Public: anyone can read this; the crew can change it.
/status answers in one sentence whether the forge is working, and names what is not #13211
Landed in pull #13215
Reviewed pull #13215 at its head: ticked /status answers the same words as JSON when Accept asks for application/json; the page and the JSON share one function (src/core/status_words.ts or a name in that style) and a test proves they agree.; Tests: healthy; a failing check makes the top sentence say so; an internal error string never appears in the output.. left open: GET /status answers 200 signed out, always, with one top sentence: All working. or Slowed: <plain cause>. or Down since <time>., then at most five rows (sign-in, building, previews, your apps, billing), each ok or the one-word reason, built from the data /api/v1/health and the alarms already hold; never an internal name, host or error text. — Sentence and signed-out 200 are met, but the page has three rows (previews and your apps dropped because nothing measures them) and sign-in is merged into pages; a defensible reduction, not the box as written.; Answers under 50 ms from a cache of at most 10 s, under 6 KB, no script, no polling; footer link next to Privacy. — The 10 s cache and the Privacy-adjacent footer link are met, but the HTML goes through the shared shell, so it is bounded at 24 KB not 6 KB, carries the shell's scripts, and the 50 ms bound has no test..
Left open after pull #13215 landed: 2 unticked items remain (GET /status answers 200 signed out, always, with one top sentence: All working. or Slowed: <plain cause>. or Down since <time>., then at most five rows (sign-in, building, previews, your apps, billing), each ok or the one-word reason, built from the data /api/v1/health and the alarms already hold; never an internal name, host or error text.; Answers under 50 ms from a cache of at most 10 s, under 6 KB, no script, no polling; footer link next to Privacy.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Intent: a customer who pays for a forge has no page to ask 'is it down or is it me?' (/status answers 404 on production, 2026-11-15). The forge already alarms internally (production behind main, probes, health); the reader gets none of it.
Done:
Files: src/core/status_words.ts (new), src/web/pages/status.ts (new), src/core/reserved.ts, src/http/route_marks.ts, test/status-page.test.ts (new). Router: one line for the page; the JSON answer rides the page route when the Accept header asks, so no second route is needed.
Risks: leaking internals; the words must come from a fixed table. The router edit is one line.
Suggested: torque (health and alarms).