I3213 — One case walks a fresh clone from init to published evidence on the release candidate

✕BLOCKED wave 5 · p2 · verification profile · parallel safe

Part of a-release-is-proven-end-to-end — Whether a commit may be released, and whether its release arrived, is proved by one read and one case.

Objective

Compose the paths existing cases already prove separately (install into a foreign repository, init, a session joining, an issue started and finished, its test run, its evidence recorded and published) into one case that runs on the release candidate and names the stage that fails.

Why

The 2026-10-18 analysis proposed alpha acceptance as one reproducible scenario rather than badges that measure different things (c295#3). The owner's alpha conditions (Operation Convergence, 2026-10-17) are proved by separate cases today. It also carries the after-landing observation the critique asked for: that a record commit's evidence job passes once I2717 lands. Sources: chatgpt-majordomus:c295#3, chatgpt-majordomus:c015#4.

Current state

I1407 (DONE) walks one issue through the path, I2162 (DONE) serves a foreign repository from a released archive, scripts/ci/install-check installs, case 3220 (I2812, branch) walks the IDD loop in a browser. No case joins them on one commit. The evidence job of validate run 39064457813 on the v0.29.0 record commit 707a04c7ce8 failed in step gather with exit 12, the planned-empty report I2717 owns.

Desired state

A case in the install or ui job runs the composed scenario on the candidate commit; each stage prints its name and evidence; a failure names its stage.

Scope

• scripts/ci/install-check
• docs/RELEASE.md

Out of scope

• Replacing the cases it composes
• Merging and releasing for real inside the case

Dependencies

• I2812✓DONE The IDD loop is accepted end to end in a real browser on one commit
• I2717○READY A release record pull request gets a verdict that can pass

Acceptance criteria

• The case runs on the release candidate commit in CI
• A failure at any stage names the stage
• The case reuses the existing fixtures and adds no second installer
• After I2717 lands, the first release record commit's evidence job is read by its failed steps, not its job conclusion, and recorded green in this issue's evidence, or the failing step is cited and handed back to I2717

Validation

• bash test/run.sh 1024_an_installed_release_serves_a_foreign_repository
• majordomus plan validate

Evidence required

• case_a_fresh_clone_reaches_published_evidence

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3213.yaml. Read it back with majordomus plan show I3213.