The owner sees the work growing or shrinking at a glance, and pauses the planner with one switch #11632

The owner can now see the work growing or shrinking on a /queue page and pause the planner there. The home-page panel, per-item actions and the "chapter" pause are not done (details below). tsc, scripts/gate.ts, scripts/design-lint.ts and the touched, contract and migration-pin tests pass. A sample of the broader suite (199 tests, 10 files) passed, but I did not run scripts/fast.ts's full selection. It reported 2,163 test files for the diff, over its 5-minute budget, and the forge's check runs the whole suite on this push.

What changed

• Panel at /:owner/:name/queue:

- Issues opened and closed per day over 14 days, as two lines. - Pulls opened and landed, as two lines. Closed-unmerged pulls and open totals are shown as figures, with no line. - Issues opened, split owner, people, planner, builders and watchers. - Three computed sentences: growth per day, days of work queued, and this week's spend on owner-asked versus planner-proposed work. - The oldest open pull and the oldest issue no run has started on, as links.

• Pause suggestion: it appears as a note when the list has grown three days running or queued work passes 14 days. Nothing pauses by itself.
• API: GET /api/v1/repos/{owner}/{name}/growth?days=14 returns the same numbers (days 1–90, otherwise 422) and whether the planner is paused. It is described in OpenAPI.
• Planner switch: an owner-only same-origin POST offers pause until the weekly reset, until a time (UTC, within a year), or until the owner switches it on. A pause lifts itself at its time, and the page shows a "paused" mark.
• What a pause stops: the planner's openIssue (answers unauthorized), its openPlan (answers planner_paused) and its queued runs. Builders and reviewers still start queued runs, and the owner can still file issues.
• Storage and indexes: the migration adds table planner_pause and two indexes, issue(repo_id, created_at) and issue(repo_id, closed_at).
• Tests: test/growth.test.ts has six tests.

- Counts match the rows for a fixture with owner, person, planner, builder and watcher authors. - The pause suggestion appears and nothing pauses on its own. - A paused planner opens no issues, plans or runs while a builder's queued run still starts, and switching on restores it. - A timed pause lifts itself. - The API and page answer, and a cross-origin POST is refused. - The per-day reads use the new indexes.

Not done

• Panel on the repository home: only /queue has it.
• Per-item actions (land, close, move to Later): the aged items are links only.
• "Until the chapter closes": the forge has no chapter concept, so I did not invent one.
• Probe and doors: there is no traffic-style probe beyond the tests, no MCP tool for the switch, and no terminal screen. The commit carries a No door: line.
• Spend split: it attributes runs by the issue's author only, so runs on pulls count as "other".

Try it: open /alice/shop/queue on the preview and press "Pause the planner". /api/v1/repos/alice/shop/growth?days=14 returns the numbers.

Closes #11604

The owner can now see the work growing or shrinking on a /queue page and pause the planner there. The home-page panel, per-item actions and the "chapter" pause are not done (details below). tsc, scripts/gate.ts, scripts/design-lint.ts and the touched, contract and migration-pin tests pass. A sample of the broader suite (199 tests, 10 files) passed, but I did not run scripts/fast.ts's full selection. It reported 2,163 test files for the diff, over its 5-minute budget, and the forge's check runs the whole suite on this push.

What changed

• Panel at /:owner/:name/queue:

- Issues opened and closed per day over 14 days, as two lines. - Pulls opened and landed, as two lines. Closed-unmerged pulls and open totals are shown as figures, with no line. - Issues opened, split owner, people, planner, builders and watchers. - Three computed sentences: growth per day, days of work queued, and this week's spend on owner-asked versus planner-proposed work. - The oldest open pull and the oldest issue no run has started on, as links.

• Pause suggestion: it appears as a note when the list has grown three days running or queued work passes 14 days. Nothing pauses by itself.
• API: GET /api/v1/repos/{owner}/{name}/growth?days=14 returns the same numbers (days 1–90, otherwise 422) and whether the planner is paused. It is described in OpenAPI.
• Planner switch: an owner-only same-origin POST offers pause until the weekly reset, until a time (UTC, within a year), or until the owner switches it on. A pause lifts itself at its time, and the page shows a "paused" mark.
• What a pause stops: the planner's openIssue (answers unauthorized), its openPlan (answers planner_paused) and its queued runs. Builders and reviewers still start queued runs, and the owner can still file issues.
• Storage and indexes: the migration adds table planner_pause and two indexes, issue(repo_id, created_at) and issue(repo_id, closed_at).
• Tests: test/growth.test.ts has six tests.

- Counts match the rows for a fixture with owner, person, planner, builder and watcher authors. - The pause suggestion appears and nothing pauses on its own. - A paused planner opens no issues, plans or runs while a builder's queued run still starts, and switching on restores it. - A timed pause lifts itself. - The API and page answer, and a cross-origin POST is refused. - The per-day reads use the new indexes.

Not done

• Panel on the repository home: only /queue has it.
• Per-item actions (land, close, move to Later): the aged items are links only.
• "Until the chapter closes": the forge has no chapter concept, so I did not invent one.
• Probe and doors: there is no traffic-style probe beyond the tests, no MCP tool for the switch, and no terminal screen. The commit carries a No door: line.
• Spend split: it attributes runs by the issue's author only, so runs on pulls count as "other".

Try it: open /alice/shop/queue on the preview and press "Pause the planner". /api/v1/repos/alice/shop/growth?days=14 returns the numbers.

The pull still adds no pipeline change, so I added the Direction: line the "pipeline first" rule allows. It goes in an empty commit that gives the reason: the owner asked for this work by name in #11604, and the switch is what lets the pipeline items be worked down. bun scripts/gate.ts passes locally and the commit is pushed. I haven't seen the forge's check result for this push.

The pull itself is unchanged:

• /:owner/:name/queue: the 14-day panel, the three sentences and the planner's on/paused switch (owner-only, same-origin POST).
• GET …/growth?days=14: answers the same numbers.
• Pause: it stops the planner's issues, plans and runs while builders and reviewers keep working, and a timed pause lifts itself.
• Not done: the panel on the repository home, per-item actions (land, close, move to Later), "until the chapter closes" (the forge has no chapters), and a terminal screen or MCP tool for the switch.

To try it, open /alice/shop/queue on the preview and press "Pause the planner", or fetch /api/v1/repos/alice/shop/growth?days=14.

This fixes the two failing tests and is pushed. I re-ran the two failing tests plus the growth, schema-migration and cold-home-query suites locally. bun scripts/gate.ts and bun x tsc --noEmit also pass.

• Event audience: planner.paused and planner.resumed were not classified for any audience. They are now classified as admin-only in src/core/event_audience.ts, so the owner and other admins hear them.
• Index plan: the migration's issue_repo_closed index changed the query plan of windowShipped in the retrospective. That query reads closed issues in a time window but orders by issue number, so it now needed a sort, and week-sprint.test.ts forbids sorts in these plans. I dropped the index from 20261112090000-planner-pause.ts and regenerated its pin, which is safe because the migration is new in this pull. The growth panel's closed-per-day read still works, but it no longer has its own index.

Everything else in the pull is unchanged. I did not run the full suite.

Pushed: the sealed leak, the public dollars and the missing terminal door are fixed, and I took most of the design and correctness points too. I did not rebase, and the MCP tool is still not done. I ran the tests that cover the change, not the whole suite: 666 pass across 24 files. bun scripts/gate.ts, bun scripts/design-lint.ts and tsc --noEmit pass. scripts/fast.ts named 2,174 test files, too broad to run, so I picked the covering ones myself.

What changed

• Sealed issues (1): growth() and oldest() now take the viewer's sealedScope, applied to the per-day, open-total, author-split and oldest-item reads. The page and GET …/growth pass the viewer's scope. A test seals an issue and checks a guest and a stranger see no count or title. The filer and a writer still see it.
• Spend (2): dropped from the API and the page, along with the third sentence. A test checks that no dollar amount appears on either.
• Terminal door (3): new src/tui/screens/queuegrowth.ts, offered as "Queue" in the palette while a repository is open. It shows the same panel from the same reads, sealed issues left out for that viewer. A human admin of the repository can flip the switch with o (until I switch it on), w (weekly reset), t (a UTC time) and n (switch on). It goes through setPlannerSwitch, so the event reaches web viewers. test/tui-queue.test.ts covers an owner flipping it, a reader with no keys, and sealed titles.
• Page design: one sentence states the planner's state. The totals are rows, with one row per day instead of SVG charts. The switch is one select, a time field and a single primary button.
• datetime-local (5): switchInput and the new utcAt normalise values with or without seconds to UTC.
• planner_paused (6): openIssue now answers planner_paused, mapped to 409 in the API and shown as a sentence on the web form.
• Comments and types (7, 8): the stale "two indexes" comments are fixed, and Mutable is replaced by a plain Tally type.
• Weekly reset test: pausing "until the weekly reset" is tested against weekCapacity.
• Audience test: the planner.paused and planner.resumed audience being admin-only is tested.
• Closed-per-day read: it has no index of its own, because the earlier issue_repo_closed made windowShipped sort. It walks the repository's own rows through the existing repo_id index. The plan test asserts a SEARCH … USING INDEX and no scan, and docs/features/growth.md says so.

Not done, and why

• MCP tool for the switch: left out. The page, the terminal and the API's growth read cover the switch, and docs/features/growth.md says so. The panel on the repository home is also not done.
• Rebase (4): I did not rebase onto main. I only shrank the pull by dropping the charts and the spend split, and left the Direction question to a person.