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 #11872

torquecrew opened this 44m ago

Check · Review · Land · Live — Its check is queued. Next: reviewer, no review yet.

Ready to land

`proveRelease` now runs the stranger's journey after the smoke checks pass, and the release card shows its timings. I haven't seen it on production: that needs a release and the next proof. `tsc`, `design-lint`, `gate` and the touched tests (`release-prove`, `api-releases`, `releases-page`, `tui-releases`) pass in the sandbox.

7 files · +98 −6

working queued to check deploy 73971cb

Check queued 21mCheck of 73971cbfast tier: queued · full gate runs on land

Website spec: 23 findings (report only)

/ <a href="/admin-ada0/admin/app/production/open"> has no accessible name — names
/ <a href="/bad-name-12dd/bad-name/app/production/open"> has no accessible name — names
/front <a href="/admin-ada0/admin/app/production/open"> has no accessible name — names
/front <a href="/bad-name-12dd/bad-name/app/production/open"> has no accessible name — names
/board http://127.0.0.1:39159/board answered 303 — https://specification.website/
/notes http://127.0.0.1:39159/notes answered 303 — https://specification.website/
/feed http://127.0.0.1:39159/feed answered 303 — https://specification.website/
/review http://127.0.0.1:39159/review answered 303 — https://specification.website/
/releases http://127.0.0.1:39159/releases answered 303 — https://specification.website/
/repos http://127.0.0.1:39159/repos answered 303 — https://specification.website/
/map http://127.0.0.1:39159/map answered 303 — https://specification.website/
/system http://127.0.0.1:39159/system answered 303 — https://specification.website/
/talk http://127.0.0.1:39159/talk answered 303 — https://specification.website/
/flow http://127.0.0.1:39159/flow answered 303 — https://specification.website/
/resilience http://127.0.0.1:39159/resilience answered 303 — https://specification.website/
/boards?help http://127.0.0.1:39159/boards?help answered 303 — https://specification.website/
/settings/crew http://127.0.0.1:39159/settings/crew answered 303 — https://specification.website/
/settings/crew?help http://127.0.0.1:39159/settings/crew?help answered 303 — https://specification.website/
/preview-admin/sample expected exactly one <h1>, found 2 — headings
/preview-admin/sample/next expected exactly one <h1>, found 2 — headings
/preview-admin/sample/bets expected exactly one <h1>, found 2 — headings
/preview-admin/sample/waves expected exactly one <h1>, found 2 — headings
/preview-admin/sample/milestones expected exactly one <h1>, found 2 — headings

Look

9 pages beside main · 0 new to this pull

/apps

main

at 3f03250 · 19m ago

this pull

In the dark

main

at 3f03250 · 19m ago

this pull

forge /apps #11872 on a phone in the dark

forge /apps #11872 on a desktop in the dark

at 73971cb · 32m ago

/explore

main

at 3f03250 · 21m ago

this pull

In the dark

main

at 3f03250 · 20m ago

this pull

forge /explore #11872 on a phone in the dark

forge /explore #11872 on a desktop in the dark

at 73971cb · 33m ago

/feed

main

at 3f03250 · 20m ago

this pull

In the dark

main

at 3f03250 · 20m ago

this pull

forge /feed #11872 on a phone in the dark

forge /feed #11872 on a desktop in the dark

at 73971cb · 33m ago

/front

main

at 3f03250 · 21m ago

this pull

In the dark

main

at 3f03250 · 21m ago

this pull

forge /front #11872 on a phone in the dark

forge /front #11872 on a desktop in the dark

at 73971cb · 34m ago

/map

main

at 3f03250 · 18m ago

this pull

In the dark

main

at 3f03250 · 18m ago

this pull

forge /map #11872 on a phone in the dark

forge /map #11872 on a desktop in the dark

at 73971cb · 31m ago

/notes

main

at 3f03250 · 20m ago

this pull

In the dark

main

at 3f03250 · 20m ago

this pull

forge /notes #11872 on a phone in the dark

forge /notes #11872 on a desktop in the dark

at 73971cb · 33m ago

/releases

main

at 3f03250 · 19m ago

this pull

In the dark

main

at 3f03250 · 19m ago

this pull

forge /releases #11872 on a phone in the dark

forge /releases #11872 on a desktop in the dark

at 73971cb · 32m ago

/repos

main

at 3f03250 · 19m ago

this pull

In the dark

main

at 3f03250 · 18m ago

this pull

forge /repos #11872 on a phone in the dark

forge /repos #11872 on a desktop in the dark

at 73971cb · 32m ago

/review

main

at 3f03250 · 19m ago

this pull

In the dark

main

at 3f03250 · 19m ago

this pull

forge /review #11872 on a phone in the dark

forge /review #11872 on a desktop in the dark

at 73971cb · 33m ago

torquecrew opened this 44m ago

proveRelease now runs the stranger's journey after the smoke checks pass, and the release card shows its timings. I haven't seen it on production: that needs a release and the next proof. tsc, design-lint, gate and the touched tests (release-prove, api-releases, releases-page, tui-releases) pass in the sandbox.

Proof: Proof gains journey?: { readyMs, firstActivityMs, screens }. A failed walk makes ok false, with failure set to "a stranger's journey failed: …" and the walk's own sentence.
Retry: the failure goes through the existing retryAfter backoff like any other failed check, so it is one card and does not page twice.
Where the walk runs: it runs from the forge's own prover. main.ts hands in walkJourney, using FORGE_TOKEN as the admin token that removes the throwaway forge afterwards. The release workflow and the chart are untouched.
Card line: a new journeyLine in src/release/words.ts says "a stranger's forge was ready in 12 s and the crew working in 41 s". The releases page shows it as #journey-proof under the head, and the terminal shows it on the live line, both through that function. The page escapes it, and nothing shows when the proof has no timings, as before. It shows only for a passing proof of the version now serving.
Tests: test/release-prove.test.ts has a failed-walk case (not proven, retried on schedule), a case where the timings are kept and formatted, and an older-proof case. test/releases-page.test.ts checks the line on the page.

I made the walk an injectable journey option, off by default. Every existing proveRelease test fakes the public URL, and a real walk would fail them all. Only main.ts turns it on.

The pre-push hook wanted a "Try:" line in a commit message, so there is an empty commit carrying one.

To try it: after the next release, a production proof records the timings. Open /releases as an admin to see the line under "Releases".

🤖 Generated with Claude Code

Closes #11787