feat(dagger): expose mark-latest as a tri-state enum on attestation init

[javirln]

Summary

Adds support for controlling "latest" promotion from the Dagger module's Init, exposed as a MarkLatest enum with three values:

• ON_CREATE (default): newly created versions become latest; existing/pre-release versions are left unchanged.
• TRUE: force-promote a pre-release version to latest.
• FALSE: skip latest promotion entirely, even for newly created versions.

The flag is modelled as an enum rather than a *bool because the Dagger v0.19.11 SDK collapses *bool parameters to plain bool and drops the false value before it reaches the wire, making the skip-promotion state unreachable through consuming modules. A non-empty string enum makes all three states reachable.

The enum maps onto the existing CLI --mark-latest flag: TRUE → --mark-latest=true, FALSE → --mark-latest=false, ON_CREATE → flag omitted (server default).

AI disclosure

Assisted by Claude Code.

[chainloop-platform]

AI Session Analysis

Avg score	Sessions	Failing policies	Attribution	Files	Lines	Total Duration
🟢 86%	1	✅ 0	100% AI / 0% Human	2	+59 / -3	1h31m57s

🟢 86% — 100% AI — ✅ All policies passing

Jun 10, 2026 10:11 UTC · 1h31m57s · $13.63 · 81.2k in / 101.6k out · claude-code 2.1.169 (claude-opus-4-8)

View session details ↗

Change Summary

• Adds a MarkLatest enum with ON_CREATE, TRUE, and FALSE to Dagger Init.
• Maps the enum to CLI --mark-latest behavior and documents it in extras/dagger/README.md.
• Regenerates the Dagger SDK and validates codegen, build, and lint locally.

AI Session Overall Score

🟢 86% — Clean implementation, but verification stopped at build/codegen checks without behavioral tests.

AI Session Analysis Breakdown

🟢 95% · scope-discipline

🟢 Implementation stayed within the requested Dagger module and README. · High Impact

🟢 94% · user-trust-signal

No notes.

🟢 92% · solution-quality

🟢 AI fixed the *bool transport bug with an enum instead of a workaround. · High Impact

🟢 90% · alignment

No notes.

🟢 88% · context-and-planning

No notes.

🟡 68% · verification

🟢 dagger develop, go build ./..., and golangci-lint run all succeeded in-session. · High Impact

🟠 No tests were added or run for the new enum behavior; verification stopped at build and codegen checks. · Medium Severity

💡 Before shipping behavior changes, run or add a focused test covering all three enum states.

---

File Attribution

████████████████████ 100% AI / 0% Human

Status	Attribution	File	Lines
modified	ai	extras/dagger/main.go	+36 / -0
modified	ai	extras/dagger/README.md	+23 / -3

---

Policies (4)

Status	Policy	Material	Messages
✅ Passed	ai-config-ai-agents-allowed	ai-coding-session-a7b993	-
✅ Passed	ai-config-no-dangerous-commands	ai-coding-session-a7b993	-
✅ Passed	ai-config-no-secrets	ai-coding-session-a7b993	-
✅ Passed	ai-config-mcp-servers-allowed	ai-coding-session-a7b993	-

---

Powered by Chainloop and Chainloop Trace

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}