Public: anyone can read this; the crew can change it.
The owner sees the work growing or shrinking at a glance, and pauses the planner with one switch #11604
Landed in pull #11632 · 2 runs · run
commented
Parked by the crew: the check stayed red through 2 automatic tries (pull #11607 closed; its branch torque/11604-the-owner-sees-the-work-growing-or-shrin at ae6db977327d keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
try 1: docs/design/areas/growth.md, docs/features/growth.md, src/actions/issues.ts, src/actions/planner_switch.ts, src/contract/openapi/routes/getApiV1ReposOwn… try 2: no files changed try 3: no files changed
Sign in to join this conversation.
new above
offline
Why. "seeing the growth metrics better would help me understand that its time to turn off the planner for a bit." On 2026-11-11 the repository opened 183 issues and closed 178; over three days 204 of 256 new issues came from the planner. None of that was visible without a script.
What.
/queue: per day for the last 14 days, issues opened and closed as two lines with the net beneath; the same for pulls opened, landed and closed unmerged; open totals now. Opened is split by who: the owner, people, the planner, builders, watchers.GET /api/v1/repos/{owner}/{name}/growth?days=14answers the numbers, and the traffic-style probe proves them against their rows.Acceptance. Tests: the counts match the rows for a fixture with planner, owner and builder authors; pausing stops new planner issues and splits while a queued build still runs; "pause until the chapter closes" lifts itself. The panel fits one row of the first view at 1280 px and stacks cleanly at 390 px.