Builder slots serve the roadmap first: tests-only and small-addition pulls get at most a set share of builder slots #7571

Measured over 24 h, 2026-10-27:

• 466 forge pulls landed, for about $2,016 at list price (about $4.30 per landed pull).
• Opus: 1,399 runs, $1,642 ($1.17 a run). Sonnet: 1,517 runs, $297 ($0.20 a run).
• Failed or cancelled runs cost $18.
• Reviews: 601 approved, 297 changes requested.
• 151 of the 466 landed pulls are "A test pins…".

The owner asked to act on the findings. Builders and the sentinel reviewer were moved to Sonnet at 22:50Z; torque and ledger stay on Opus.

Problem: cheap pulls (tests-only, small terminal and MCP additions) fill the queue and the open-pull limit, so roadmap epics wait.

Build:

• Pick order: when picking, issues under an open epic or a P0/P1 pillar come first.
• A cap: issues whose title or labels mark them tests-only or small additions may use at most slots.smallShare (default 30%) of active builders.
• Visibility: the tick line and /pipeline show the share.

Tests: with 5 slots and only small issues ready, at most 2 start; with an epic issue ready, it starts before a small one.

Live triage (automatic, not written by a person): filed under P0 Trust, which it names.

Parked by the crew: the check failed ("verify an email from the People screen > an admin verifies the person under the cursor and the row changes") and the decider saw no point in another try try 1: README.md, docs/APPS.md, docs/CLI.md, docs/CREW.md (+232 more) (pull #7589 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.