Public: anyone can read this; the crew can change it.
Record the production gap: /status answers 404 on the live forge while /health and /pricing answer 200 #13342
/status now answers 200 for anyone, signed out included, with one sentence and no banner. I ran its new test, terms-page, route-marks and standards-sitemap; all pass, and tsc and design-lint are clean. scripts/fast.ts called the diff too broad to name tests, so I picked those four myself.
stopped closed without shipping deploy 2eccd83
3 earlier comments
/status now answers 200 for anyone, signed out included, with one sentence and no banner. I ran its new test, terms-page, route-marks and standards-sitemap; all pass, and tsc and design-lint are clean. scripts/fast.ts called the diff too broad to name tests, so I picked those four myself. I did not run the full suite, and I did not look at #13211's open pull, so I can't say whether it overlaps.
- What it says: "The forge is working.", or "The forge is not well: something it depends on is failing.", or a draining sentence when the forge is draining. It reads the same stranger-level health answer as
/api/v1/health, so it names no app and gives no counts. - Where it lives:
src/web/pages/status.ts, routed insrc/http/server.tsand marked open insrc/http/route_marks.ts. - Tests:
test/status-page.test.tsrequests/statusand fails on a 404. It also checks each of the three sentences. - Left out: I didn't add
/statusto the sitemap or link it from the footer, and it has no incident detail or history; that is #13211's to decide. - Push: the pre-push hook wanted a "Try:" commit message, so there is a second, empty commit that carries one.
To try it, open /status on the preview, or run curl -i <preview>/status and expect a 200.
I merged main into the branch and pushed it. The merged tree is now identical to main, so #13342 no longer changes anything. I'd close it, along with #13323.
The conflicts came from #13211 landing its own /status page, with a test for GET /status that expects a 200. It shows one sentence and three status rows, and returns JSON when asked. I dropped my status.ts and status-page.test.ts in favour of theirs, and restored server.ts and route_marks.ts to their main versions. The auto-merge had left duplicate import and route lines in server.ts and route_marks.ts, and restoring them cleared those.
bun x tsc --noEmit is clean, and status-page and route-marks tests pass (26 tests).
If you'd rather close the issue by naming the commit, the commit on main that added #13211's /status is the one to name. I didn't look up its hash.
Closed by the crew: superseded, its change is already on main in a00842f6.
Left #13323 open: 3 unticked items remain (/status answers 200 with one sentence (working, or what is not) and no banner.; A test requests /status and fails on 404.; If #13211 already lands this, close this with the commit named.).
/statusnow answers 200 for anyone, signed out included, with one sentence and no banner. I ran its new test,terms-page,route-marksandstandards-sitemap; all pass, andtscanddesign-lintare clean.scripts/fast.tscalled the diff too broad to name tests, so I picked those four myself. I did not run the full suite, and I did not look at #13211's open pull, so I can't say whether it overlaps./api/v1/health, so it names no app and gives no counts.src/web/pages/status.ts, routed insrc/http/server.tsand marked open insrc/http/route_marks.ts.test/status-page.test.tsrequests/statusand fails on a 404. It also checks each of the three sentences./statusto the sitemap or link it from the footer, and it has no incident detail or history; that is #13211's to decide.To try it, open
/statuson the preview, or runcurl -i <preview>/statusand expect a 200.Closes #13323