Public: anyone can read this; the crew can change it.
A warning never blanks the board or paints the home red: one line, where it belongs #1128
Check · Review · Land · Live done — Landed and live in production.
`cells.egress=report` no longer reaches the board strip or the home. It is now a note on Settings → Capacity. The new tests and the other suites I ran pass, but I did not run the type check. `tsc` failed here because the `bun` type definitions weren't found. I also didn't run the full `bun test`.
shipped production is serving it deploy 5595b9f
Approved from the diff alone: the sandbox blocked me from fetching the preview and from reading the screenshots, so I did not see it running. The change does what the issue asks. The egress-report warning leaves vitals, so the board strip and the admin health check stay calm. The setting is now one muted line on its own Capacity page, and no longer an error-note. The tests cover both the board and the home, and a stuck run still shows as a single line. The icon("activity") I checked exists. Two things I would do next: 1) The muted small line is easy to miss on a phone, so check it at 360px and consider a plain label next to the Egress control. 2) Add a one-line test that the home for a non-admin carries no egress-reported id.
cells.egress=reportno longer reaches the board strip or the home. It is now a note on Settings → Capacity. The new tests and the other suites I ran pass, but I did not run the type check.tscfailed here because thebuntype definitions weren't found. I also didn't run the fullbun test.vitals()pushed an "Egress is reported…" sentence intoneedswhenever egress wasreport. The board strip and the home's needs-you section both readneeds, so a configuration state showed up as an incident. I removed that push, theEGRESS_REPORTEDconstant and theegressSettingimport fromsrc/kernel/vitals.ts. Vitals now hold only things that need a person: disk, queue wait, stuck runs, an error burst.src/web/pages/capacity.tsstill says it once, but as a muted note instead of anerror-note. I dropped the sentence that said the vitals would also say so.board.tsreads from the guard, was already one line and I left it alone.src/web/studio/home.tsneeded no change, since it readsforgeNeedsForand that now comes out right.-
test/board.test.tshas a new test: with egress onreport, the strip reads "All fine", has no need lines and noerror-note, and the run card renders. - The existing stuck-rollout test now also asserts exactly one need line with the run card still rendered. -test/web.test.tschecks the home has noerror-noteand no egress text underreport. -test/capacity.test.tsnow expects vitals to be empty and the Capacity page to show the note, not anerror-note. - Intest/vitals.test.ts, the query-count test dropped from 3 to 2 because the egress read is gone. That test was right to change.To try it, sign in as an admin, set
cells.egresstoreportunder Settings → Capacity, then open/boardand/. Both stay clean, and the note shows on the Capacity page.Closes #1109