/flow says how many crew runs declined in the last day, and why #10880

/flow (the panel on /boards) now shows a "Declined in 24 h" line, and the flow MCP tool returns the same counts. src/flow/declines.ts is reached and has left scripts/unreached-allow.json.

The new test/flow-declines-reach.test.ts and the neighbouring declines, MCP size/table and panel tests pass, as do bun scripts/gate.ts, tsc --noEmit and design-lint. I did not run the full suite, and I did not look at the panel in a browser.

• Reader: new readDeclines(db, now, publicOnly) reads declined agent build runs finished in the last 24 h, newest first, and counts them by reason with the existing declines(). It follows the same public-only rule as the other flow reads.
• /flow: each reason (already on main, not on main yet, off direction, other) shows its count. Each count is followed by up to three issue numbers, and each number links to its run at /owner/repo/runs/<id>. Nothing renders when there were no declines.
• MCP: the flow tool's default answer gains a declines field with says, groups and runs. An agent reader gets public repositories only. Its description grew by one clause, no new tool or argument was added, and test/mcp-size.test.ts passes.
• Linking: I read "each reason linking to the runs behind it" as one link per issue to its newest declined run, capped at three with a "…" when there are more. There is no combined list page for all runs behind a reason.
• Not done: the terminal's Flow screen does not show the line.
• Push: the first push was refused by the pre-push hook because no commit said how to try the change. I added an empty Try: commit, which is why the branch has two commits.

To try it: seed a run whose summary starts "Declined: …" and open /boards, or call the flow tool with no arguments.

Closes #10862

/flow (the panel on /boards) now shows a "Declined in 24 h" line, and the flow MCP tool returns the same counts. src/flow/declines.ts is reached and has left scripts/unreached-allow.json.

The new test/flow-declines-reach.test.ts and the neighbouring declines, MCP size/table and panel tests pass, as do bun scripts/gate.ts, tsc --noEmit and design-lint. I did not run the full suite, and I did not look at the panel in a browser.

• Reader: new readDeclines(db, now, publicOnly) reads declined agent build runs finished in the last 24 h, newest first, and counts them by reason with the existing declines(). It follows the same public-only rule as the other flow reads.
• /flow: each reason (already on main, not on main yet, off direction, other) shows its count. Each count is followed by up to three issue numbers, and each number links to its run at /owner/repo/runs/<id>. Nothing renders when there were no declines.
• MCP: the flow tool's default answer gains a declines field with says, groups and runs. An agent reader gets public repositories only. Its description grew by one clause, no new tool or argument was added, and test/mcp-size.test.ts passes.
• Linking: I read "each reason linking to the runs behind it" as one link per issue to its newest declined run, capped at three with a "…" when there are more. There is no combined list page for all runs behind a reason.
• Not done: the terminal's Flow screen does not show the line.
• Push: the first push was refused by the pre-push hook because no commit said how to try the change. I added an empty Try: commit, which is why the branch has two commits.

To try it: seed a run whose summary starts "Declined: …" and open /boards, or call the flow tool with no arguments.

All three of the review's points are done: the terminal Flow screen now shows the declines line, there is a how-to doc, and the label exports are fixed.

• Terminal door: the Flow screen in src/tui/screens/flow.ts now shows Declined in 24 h: … under the review latency, the same sentence the page and the flow tool use. It is left out when nothing was declined. An admin sees every repository; an agent or guest sees public repositories only.
• Test: test/flow-declines-reach.test.ts gains a test for the screen. It covers the line being absent with no declines, the admin seeing both a public and a private decline, and an agent seeing only the public one.
• How-to: docs/features/flow-declines.md says what the line shows and how to read it on /boards, in the terminal Flow command and through the flow tool. README.md is untouched.
• Exports: DECLINE_LABELS and DECLINE_REASONS are now exported where they are defined in src/flow/declines.ts, and the bottom re-export is gone.

The gate and tsc print nothing, and the two TUI flow test files I ran pass: 7 tests (the new one, the rest of the reach test and test/tui-flow-lead.test.ts). I did not run the full suite; the forge runs it on the push.

To try it: open the Flow command in the terminal after a declined run, or open /boards and read the "Declined in 24 h" line.

I merged main into the branch and pushed it. The only conflict was the doc string in src/http/mcp/tools/flow.ts.

I kept main's wording, including its new ui://forge/flow card mention. I added my declines phrase (crew runs declined in 24 h, by reason) after the reviewing part.

bun scripts/gate.ts and bun x tsc --noEmit print nothing. I ran 39 tests across 6 files — the declines reach test, the TUI flow lead test and the MCP flow tests — and all pass. scripts/fast.ts exited 2: the diff is too broad to name tests, because scripts/unreached-allow.json changed on main. So I picked those test files by hand and did not run the full suite; the forge runs it on the push.