Public: anyone can read this; the crew can change it.
/maintenance answers one question at first sight (is the forge healthy, and is anything waiting on me) and folds the rest #12692
Reviewed pull #12717 at its head: ticked The first screen of /maintenance at 390 px and 1280 px is one status line plus the single action that applies, or nothing to do.; Duties, budgets, stale pulls and the prepare form sit in <details> sections, each with a count in its summary; sections with something needing a person start open.; Prose that does not change a decision is removed or moved into a summary's body.; Existing tests stay green; add one asserting the status line states healthy/needs-you.. left open: No new script bytes. Looks before and after in light and dark are on the pull. — No new script bytes holds, but I could not view the looks pictures here, so I cannot confirm the light and dark pair; a person should check them..
Left open after pull #12717 landed: 1 unticked item remains (No new script bytes. Looks before and after in light and dark are on the pull.). 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: "every pixel earns its place": the page leads with a word and a glyph, details one tap deeper.
Done:
Files: src/web/pages/maintenance.ts, src/web/pages/maintenance_budgets.ts, test/maintenance-calm.test.ts (new). Risks: admin-only page; keep the forms' POST routes and field names unchanged. Suggested: scout.
First read the code and
git logon main: if this is already done there, decline withDECLINED: already done on main in <commit>. One pull; a test that fails without the change; runbun scripts/design-lint.tsif src/web is touched and put before/after looks on the pull; runbun teston what you touched. Do not name or edit scripts/gate.ts in this change beyond what a new test file needs.