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

I added test/calm-home.test.ts, which renders the admin's / and /board with egress in report mode and the week's spend share at its 10% minimum. Neither page carries a role="alert", .banner or .notice-danger element above <main>. test/calm-home.test.ts passes and tsc --noEmit is clean.

I did not run scripts/design-lint.ts, test/mcp-size.test.ts or the gate. No src/web or MCP code changed, and the forge's check runs the full suite on the push.

• No page failed. The earlier calm work (#10699, #10777) had already moved these lines, so no page needed fixing.
• Settings lines: /settings/capacity shows the egress fact once, as #egress-reported, and the week-spend setting as its own row.
• Named exceptions: the test lists two by name in EXCEPTIONS: a failed deploy (#deploy-failed) and a stalled flow card (.flow-stalled). These are guessed selectors; the test does not render either state, so nothing yet checks them against real markup.
• Detector self-test: the detector's own test fires on a banner, spares only the named exceptions, and fails if the list grows past two.

Left out:

• No reviewer: a fresh forge has none, so that state is the default rather than something the test sets. No setting controls it.
• Low credit: the "low credit" case is the week-spend share, because the repo has no balance setting. If a credit balance is added later, the test needs a case for it.
• Settings pages: I did not check any Settings page other than the capacity one for the odd facts.

To try it: bun test test/calm-home.test.ts.

Closes #11379

I added test/calm-home.test.ts, which renders the admin's / and /board with egress in report mode and the week's spend share at its 10% minimum. Neither page carries a role="alert", .banner or .notice-danger element above <main>. test/calm-home.test.ts passes and tsc --noEmit is clean.

I did not run scripts/design-lint.ts, test/mcp-size.test.ts or the gate. No src/web or MCP code changed, and the forge's check runs the full suite on the push.

• No page failed. The earlier calm work (#10699, #10777) had already moved these lines, so no page needed fixing.
• Settings lines: /settings/capacity shows the egress fact once, as #egress-reported, and the week-spend setting as its own row.
• Named exceptions: the test lists two by name in EXCEPTIONS: a failed deploy (#deploy-failed) and a stalled flow card (.flow-stalled). These are guessed selectors; the test does not render either state, so nothing yet checks them against real markup.
• Detector self-test: the detector's own test fires on a banner, spares only the named exceptions, and fails if the list grows past two.

Left out:

• No reviewer: a fresh forge has none, so that state is the default rather than something the test sets. No setting controls it.
• Low credit: the "low credit" case is the week-spend share, because the repo has no balance setting. If a credit balance is added later, the test needs a case for it.
• Settings pages: I did not check any Settings page other than the capacity one for the odd facts.

To try it: bun test test/calm-home.test.ts.

The pull is still one new file, test/calm-home.test.ts, with no source changes. It now seeds the odd states for real, and bun test test/calm-home.test.ts passes (6 tests). tsc --noEmit, bun scripts/gate.ts and bun scripts/design-lint.ts are clean. I did not run test/mcp-size.test.ts, since nothing here touches the MCP.

What changed since the first round

• Exceptions (items 1 and 5): You were right, the old selectors were invented. The list now holds only the real markup, and found is no longer exported.

- Stalled flow card: its markup is data-flow-card= from src/web/studio/flow_card.ts. The test seeds a pull with a red check, renders it through /feed in studio mode with the "Re-run" button, and shows the card is spared. - Failed deploy: its markup is the shelf row's <span class="badge" data-tone="attn"> from src/web/studio/shelf.ts. I could not render this state end to end, because a failed deploy needs a live app runtime. The test pins the tag by reading shelf.ts and showing the detector spares it. - No exemption needed: neither exception trips the alert/banner detector today. They stay on the list by name so a future change that makes one loud has to say so.

• No reviewer (item 2): The test creates an app on autonomy whose crew has only a builder agent. The board shows one data-need line, "No reviewer: agent pulls wait for you", and the page stays free of alerts and banners. That line is a calm link, not a banner.
• Low credit (items 2 and 3): The forge has no credit-balance state, so the week-spend share at its minimum (week.use = 10) stands in for it, and the test comment says so.
• Settings (item 3): I did not add a Settings line for no reviewer. Its one line is on the board, and the asks page loads it live, so it never reaches a plain fetch of the page. The egress line and the week-share row are still checked on /settings/capacity. If you want it in Settings too, that is a source change.
• Detector (item 4): It now scans everything above the first <main> plus any <header> or <nav> block wherever it sits. The board's own header is inside <main>, which is why that matters. New cases catch a banner in a header and in a nav after <main> opens. The real page's role="banner" on its top bar is a different attribute and is not flagged.