Epic: v1.0.8 release qualification reliability and pre-announcement gate

[jeffhuber]

Goal

Make multi-provider release qualification deterministic, discoverable, evidence-complete, and usable before broad release announcement. Ship v1.0.8 through the Code Mower gate, qualify it across local and hosted provider paths, upload metadata-only evidence, and leave the builder-calibration ledger current.

Ordered work

1. Fix audit verdict transport for metadata findings without source lines (Preserve audit verdicts when metadata findings omit source lines #681).
2. Complete the bounded reliability children of Make local release campaign qualification deterministic and preserve failure evidence #708:
   • deterministic Python 3.12+ runtime plus truthful authentication/result readiness;
   • retry chronology plus terminal fail/incomplete evidence upload.
3. Make release-campaign state discoverable across worktrees without breaking existing generated workflows or local campaign files.
4. Add a bounded candidate-package source suitable for pre-announcement qualification, initially TestPyPI with explicit index controls and exact identity checks.
5. Verify Cursor/Grok Bot and Devin hosted campaign transport using trusted comments and bounded response deadlines.
6. Publish v1.0.8 only after local checks, both peer audits, release readiness, package workflow rehearsal, and candidate qualification are green.
7. Run the v1.0.8 campaign, inspect and upload metadata-only adoption results, update Builder calibration: five bounded deliveries each for Cursor, Muse, Antigravity, and Devin #659, and record the final release posture.

Constraints

• One issue per PR; keep PRs under 300 lines where practical.
• Code Mower gate plus Codex and Claude peer audits; author lanes never gate themselves.
• Dry-run before dispatch, upload, or publish.
• No source, diffs, transcripts, issue bodies, raw stdout/stderr, auth output, local paths, or secrets in cloud events.
• Existing campaign files remain readable; generated workflows are added or updated compatibly, never casually renamed.
• Hosted paid work never retries automatically.

Dependency map

The audit transport, deterministic runtime/readiness, attempt-evidence, and campaign-discovery issues are parallel-safe. Candidate-source qualification depends on the campaign identity contract remaining stable. Hosted verification depends on the candidate source and transport readiness. Release and final qualification are serial.

[jeffhuber]

Work Order: execute v1.0.8 through Code Mower

Implementation queue:

• Preserve audit verdicts when metadata findings omit source lines #681: audit metadata-line transport, Cursor builder.
• Release campaign: deterministic supported runtime and truthful adapter readiness #710: deterministic runtime/readiness, Antigravity builder.
• Release campaign: preserve retry chronology and upload terminal failure evidence #711: chronology and terminal evidence upload, Muse builder.
• Release campaign: discover state consistently across worktrees #712: cross-worktree campaign discovery, Devin builder attempt.
• Release campaign: qualify an exact TestPyPI candidate before broad announcement #713: closed TestPyPI candidate source, Claude builder after campaign identity review.
• Release Code Mower v1.0.8 after multi-provider candidate qualification #714: serial release after every preceding gate and qualification requirement is satisfied.

Each PR needs tests, a concise documentation update, final-head peer audits excluding the author lane, and metadata-only evidence upload after dry-run inspection. Shared campaign identity changes merge before #713 rebases and finalizes.

[jeffhuber]

Hosted-provider dogfood added two contract-first children:

• Provider registry: separate Cursor Cloud Agent and Grok Bot identities #717 separates Cursor Cloud Agent builder identity from Grok/Cursor BugBot reviewer identity and preserves legacy campaign evidence explicitly.
• Hosted campaigns: verify Cursor and Devin result transport before paid dispatch #718 verifies Cursor and Devin result-return transport before any paid dispatch and fails unavailable integrations before mutation.

Updated dependency order: merge shared runtime/chronology/discovery work first; then #717; then #718 and #713 may proceed against stable provider and campaign identity; #714 remains the serial release gate. The unacknowledged Devin #712 dispatch is retained as infrastructure evidence and will not be retried automatically.