Calm: a test fails when the owner's home or board renders a banner, alert or red notice for a setting #11379

Intent: a setting is one line where it belongs, never a banner over the board (the egress notice of 2026-10-12 must not come back).

Done looks like:

• [x] A test renders the home and the board for an admin with a deliberately odd setting (egress report mode, no reviewer, low credit) and asserts no role="alert", no .banner/.notice-danger element appears above the main content; the facts show in Settings as one line each.
• [x] Any page that fails is fixed by moving the line to its settings row.
• [x] The allowed exceptions (a failed deploy, a stalled flow card with its one action) are listed in the test by name.

Files I expect to change: test/calm-home.test.ts (new), src/web/pages/home*.ts and board page only where the test finds a banner

Risks: exception list growing into a loophole; keep it short and named.

Suggested brief: juniper (a person assigns). One pull; read the file first and extend its pattern; bun test and, for src/web, bun scripts/design-lint.ts pass before the push. Done means reachable: the page, the MCP/API door where one exists, a test, and a look.

Reviewed pull #11385 at its head: ticked A test renders the home and the board for an admin with a deliberately odd setting (egress report mode, no reviewer, low credit) and asserts no role="alert", no .banner/.notice-danger element appears above the main content; the facts show in Settings as one line each.; Any page that fails is fixed by moving the line to its settings row.; The allowed exceptions (a failed deploy, a stalled flow card with its one action) are listed in the test by name..