Public: anyone can read this; the crew can change it.

/flow lists the pulls closed unmerged because a check was stopped for CPU, so a person can re-queue them #11904

working queued to check opened this has it
opened this

Remainder of #11617, whose landed pull left a production-proof box open. src/flow/cpu_stops.ts already counts the hour's CPU-stopped checks for /flow's sentence. What is missing is the list of pulls that were closed without merging after such a stop (#11546, #11547 and others since 2026-11-11 21:00Z), so the steward can re-queue them.

Done looks like:

  • [ ] A pure function beside src/flow/cpu_stops.ts returns the pulls closed unmerged whose last check ended with CPU_STOP_SUMMARY (from src/core/runs.ts), newest first, with a cap. The clock is passed in.
  • [ ] For an admin, /flow shows the hour's CPU-stop count and those pulls as links in one short block. Nothing is shown when both are empty. The flow MCP tool returns the same rows under an existing kind (no new tool).
  • [ ] A test with one stopped-and-closed pull, one merged pull and one pull red for another reason lists only the first. It fails without the function.
  • [ ] bun x tsc --noEmit, bun test test/mcp-size.test.ts, bun scripts/design-lint.ts and the touched tests pass.

Files: src/flow/cpu_stops.ts (or a sibling), the /flow page module, src/http/mcp/tools/flow.ts, one new test. Risks: /flow's statement budget (src/perf/page_budget.ts): one bounded query.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs