Public: anyone can read this; the crew can change it.
A page that fails says where you are, offers the way back and a request id, and never shows a stack #12707
commented
Reviewed pull #12710 at its head: ticked A page handler that throws answers 500 with the normal chrome (header, crumbs where the route is known), one plain sentence, links to home and to the page's parent, and a short request id.; The same id is in the server log line for that error; the error's message and stack never reach the page.; The security floor headers (securityFloor in src/http/respond.ts) are on the 500 as on every response.; Machine routes (/api, /mcp) keep their JSON error shape with the same id.; A test with a route made to throw: status, chrome, id in body and log, no stack in body, headers present..
Sign in to join this conversation.
new above
offline
Intent: never lost, even when the forge itself fails: a 500 today should still say where you are and how to get back, and give the owner something to quote.
Done:
Files: src/http/ (the top-level handler that catches), src/web/chrome.ts, test/error-page-500.test.ts (new). Risks: the error page must not itself query the database (it may be what failed); render from the request alone. Suggested: scout.
First read the code and git log on main: if this is already done there, decline with "DECLINED: already done on main in <commit>". One pull; run bun scripts/design-lint.ts and put before/after looks on the pull.