[JacobStephens2]

Summary

Versionless Release runs are Passes over green shipped changes. Automatic mode chooses minor or patch and writes the summary in one fresh-home sandboxed, traced Session. CLI, admin API and Console support explicit versions or pinned bumps.

release
  record Pass firing → Experiment / Quota / release locks
  shipped diff since last tag → newest green first-parent main commit
  pinned bump → summary
  automatic → minor or patch + summary in one Session; invalid output → patch
  bump PR → checks → tag → publication → merge

Closes #2158

Evidence

Execution evidence

• Before: cargo test --test release native::release_pass_filters_shipped_sources_assets_skills_and_pipeline_paths -- --exact --nocapture failed: src/console/start_form.html, left: false, right: true.
  After: the same command passed: 1 passed; 0 failed (45.18s).
• Before: node --test --test-name-pattern='Release start confirms automatic' console/tests/start.test.cjs failed waiting for the Bump control.
  After: the same command passed: 1 passed; 0 failed (8.19s).
• The Spec review's exact external reproduction failed because blank minor output published v0.2.0; after fixing, that reproduction and retained cargo test --test release native::review_blank_minor_summary_falls_back_to_patch -- --exact --nocapture passed.
• Retained live-progress regression passed after demonstrating that pending main CI previously emitted no progress before completing. Native release and admin API focused checks passed. UPDATE_PROMPTS=1 cargo test prompts_page and cargo test prompts_page passed (14 tests each).
• Both scripts/affected-tests refs/remotes/origin/issue-2054 attempts passed all 69 site checks and stopped on local Console fixture/timing failures: three Inbox checks in the first attempt and one Session-reader check in the second (206 passed). All four failed checks passed on focused reruns. The complete GitHub site and Console suites passed for 17671668. cargo fmt --check and cargo clippy --all-targets -- -D warnings passed. All four Rust CI partitions and their coverage gate passed for code head 17671668 (CI run). The additional cargo nextest run --test-threads 3 was stopped after 771 passes once that equivalent CI result was available; three running tests ended by SIGINT, with no earlier test failure. The final documentation-only adjustment passed all 69 site checks (135.53s). Final-head site, Console and release-build CI are also green; the new Rust partitions are still running.

Test seams:

• Installed thirdshift release CLI against a real local Git origin, fake GitHub transport, and a real fresh-home sandboxed summary Harness.
• POST /api/v1/start / /api/v1/runs and generated OpenAPI command inventory under scoped authentication; Cron jobs' recorded Pass firing.
• Console Start Release run form and confirmation in Chromium at desktop and mobile widths.

Visual evidence

Start Release run, expanded; desktop 1440×900.

Start Release run, expanded; mobile 390×844.

Review coverage

Reviewed with thirdshift-code-review against refs/remotes/origin/issue-2054 (57e6e48a). Standards: 1 finding, fixed. Spec: 1 finding, fixed. Both reviewers read all 29 changed files through 17671668, including generated output, with no exclusions. A final documentation-only commit corrects three older API paragraphs in site/index.html, site/how-it-works/index.html and site/architecture/index.html; those latest hunks were checked by the implementer and remain unread by both independent reviewers after their allowed follow-up. Final reports and counts are retained in .thirdshift-review-Ic7ZsR/ for the Session trace.

Unaddressed findings

Standards

None. The omitted automatic-selection prompt is now catalogued and regenerated; its exact focused check passes.

Spec

None. Blank summaries now force patch fallback; the reported reproduction passes and the test is retained.

Security

None. Versionless and bump-flagged Release starts stay admin-scoped, version and bump stay mutually exclusive, automatic selection can only publish a code-chosen minor or patch from a green origin/main commit, and the summary Session stays in the existing fresh-home sandbox.

Security review outcome

No unaddressed introduced findings.

Merge Danger

Door: two-way

The implementation can be reverted. Releases it publishes keep their existing immutable-tag policy.

Blast Radius: Releases

Versionless invocation can publish a new release when shipped changes have green push CI. Existing explicit-version publication checks, dedicated locks and reservation remain in place.

Built with codex codex-cli 0.167.1 · gpt-6.1-sol · xhigh