Growth and the planner switch
Open /:owner/:name/queue, or "Queue" in the terminal's palette while a repository is open. It shows, for the
last 14 days, issues opened and closed, pulls opened, landed and closed unmerged, the open totals, who opened
the issues (owner, people, planner, builders, watchers) and a row for each day, with two plain sentences: how
fast the list grows or shrinks and how many days of work are queued at the current pace. The oldest open pull
and the oldest issue no run has started on sit above. Sealed issues are left out of every number and title for
anyone who may not see them (core/sealed.ts). No dollars are shown.
Planner: on / paused. The owner (a person who administers the repository) pauses it until they switch it on,
until the weekly reset (the account's own reset when one is read, else Monday), or until a time (UTC, within a
year). Paused, the planner opens no issues (planner_paused), adds no plan and starts no run; builders and
reviewers keep finishing what is queued. A pause lifts itself at its time. The page suggests a pause when the list
has grown three days running or queued work passes two weeks of pace; it never pauses by itself. In the terminal:
o until I switch it on, w weekly reset, t a time, n switch on. planner.paused and planner.resumed are
heard by the admins.
GET /api/v1/repos/{owner}/{name}/growth?days=14 answers the same numbers (days 1 to 90), whether the planner
is paused, and what the caller may see.
In one line (#12867). /:owner/:name/next and the terminal's Next up say the same sentence (growthWords):
issues opened and closed this week and how many issues and pulls are open now. The MCP system tool with
{ kind: "growth", repo } answers {openIssues, openPulls, openedToday, closedToday, openedWeek, closedWeek}
(today is the UTC day; the week is seven UTC days) from the same read, for a reader of the repository only; a
guest or a non-reader of a private repository gets a refusal, and sealed issues are left out for anyone who may
not see them. Today's numbers are in that answer only; the page and terminal show the week.
Closed-per-day has no index of its own: it walks the repository's rows through the existing repo_id index
(one made the retrospective's plan sort). Opened-per-day uses issue_repo_created.
The switch over MCP. system with { kind: "growth", repo, action: "pause" | "resume", until? } answers what
it would do and changes nothing; with confirm: true it calls setPlannerSwitch, as the page's switch does, and the
event is planner.paused or planner.resumed. until is a UTC time within a year; pause without it lasts until
the planner is switched on. An agent or a non-admin gets the page's sentence, "Only the owner switches the planner."
Until the chapter closes (#13108). The pause has a fourth choice: the queue page's "until the open chapter
closes", the terminal's h (c is the ceiling's) and the MCP system growth pause with chapter: true, all
through setPlannerSwitch ({ mode: "chapter" }). With no open chapter it is refused with "There is no open chapter
to wait for." and nothing changes. The pause is a row in planner_pause at CHAPTER_UNTIL plus the chapter's id in
forge_setting; pausedUntil reads it as lifted once that chapter is not open, so shipping or closing lifts it
without touching the close. Any other pause or a switch-on forgets the chapter. Pinned by
test/planner-pause-chapter.test.ts.
Not done: the panel on the repository home, and one action per aged item.