Public: anyone can read this; the crew can change it.

A release counts as proven only when a stranger's journey passes on production, and the release card gives the timings #11787

working queued to check opened this has it
opened this

Intent: every release proves the first five minutes on production, as #11158 asks. Part 3 of 3 of #11158.

Done:

  • [ ] proveRelease (src/release/prove.ts) runs walkJourney after its existing checks; Proof gains journey?: { readyMs, firstActivityMs, screens }; a failed walk makes ok false with the walk's failure sentence as failure
  • [ ] the release card (the releases page and the terminal's releases view, through src/release/words.ts) says in one line "a stranger's forge was ready in 12 s and the crew working in 41 s", escaped; an older proof without timings reads as before
  • [ ] a journey that fails is retried on the existing schedule (retryAfter) like any other failed check; it does not page twice
  • [ ] test/release-prove.test.ts gains a case where the walk fails and the release is not called proven, and one where its timings reach the card
  • [ ] bun x tsc --noEmit, bun scripts/design-lint.ts and the touched tests pass in the sandbox before the push
  • [ ] after release, the next production proof shows the timings on the card (look before closing; done is live)

Files: src/release/prove.ts, src/release/words.ts, the releases page under src/web/pages/, test/release-prove.test.ts. Risks: never touch the release workflow or the chart; the walk runs from the forge's own prover, not from CI. Suggested builder: mason.

(Re-filed fresh from #11708, which is held by a split in its history and could not be dropped.)

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs