Knobs: one panel on the crew page with five plain dials, each showing its live effect, editable in place #10461

The owner's words: "I want this thing to fly with only a few knobs that I can easily understand and tune right there." Today the dials are spread over GET /api/v1/admin/capacity (crew.concurrency, checks.concurrency, checks.shards, queue.depth, queue.batch, slots.smallShare, polish.capMinutes, pace.floor), the repository's autonomy card (autonomy, autonomySlots, autonomyCeilingUsd, polishShare, plansNeedNod, decisionsBy) and constants nobody can see (governor.ts ratios, reserve.ts, WEEK.reserve/tolerance, guard.ts run caps). Nobody can read the crew's state from them.

The five knobs (plain words; a sensible default; everything else derived or gone):

1. Speed — runs at once. Default: what the pod's memory allows (today 4). Derives crew.concurrency, the repository's builder slots, the reserve (2 per slot), pace.floor (half of speed, at least 1), queue.depth. Live effect: 4 running · 6 queued · next starts in ~2 min.
2. Weekly budget — how much of the week's subscription to use, and the pace: use 90% of the week, evenly to the reset. Replaces the dollar ceiling (autonomyCeilingUsd), WEEK.reserve, the run caps. Live effect: 25% used, 73% of the time left · on pace · lasts to Sat 02:00 UTC.
3. Polish share — the share of the week polish may take (today polishShare, 10%). Folds in slots.smallShare and polish.capMinutes, which cap the same thing twice more. Live effect: polish 6% of this week's spend · 3 polish issues waiting.
4. Autonomy per repository — off, ask, go. ask = plans need a nod and decisions come to me (plansNeedNod, decisionsBy: me); go = the decider answers and plans open. Live effect: go · planner due in 40 min · 7 ready.
5. Feedback first — fixed on, shown not tuned: a person's comment, assignment or from-app note starts ahead of everything (people_first.ts). Live effect: nothing from a person waiting or 1 waiting since 23:41.

The panel: one card on the crew page (admin only), one row per knob: name, one line of what it does, the current value, its live effect, and the control right there (number, percent, or three words). A change applies at once — capacity is already read on every pump — and writes the same forge.settings_updated / repo.settings_updated event the settings pages write, so the feed says who turned what. Keys the knobs derive from disappear from Settings › Capacity (or move under a "Derived" fold that shows the computed value, read-only). Hosting and security keys stay where they are: children.*, cells.egress, guard_new_accounts, signin.edge, crewOutsiders.

Done when

• [x] The crew page shows the five rows with value, one-line meaning and live effect, in two taps from home; the terminal's crew screen shows the same five lines.
• [x] Each knob is editable in place and the next pump reads it (a test turns Speed from 4 to 2 and the next start waits).
• [ ] slots.smallShare and polish.capMinutes are gone; pace.floor, the reserve and queue.depth are derived from Speed and show as such.
• [ ] autonomyCeilingUsd is gone from the autonomy card; the week's budget is a share of the week and a pace.
• [x] MCP: a knobs tool reads and sets the same five, in the same words.

Files: src/web/studio/crew.ts, src/core/capacity.ts, src/crew/week_read.ts, src/crew/week.ts, src/crew/small_share.ts, src/crew/polish_cap.ts, src/http/mcp/tools/

Parked by the crew: the check stayed red through 2 automatic tries (pull #10476 closed; its branch scout/10461-knobs-one-panel-on-the-crew-page-with-fi at afed984df88f keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

The owner's standing direction ("remove stupid rules. I want this thing to fly with only a few knobs") is the go for the removals crew-tuner-2 listed. As part of the knobs work, remove:

• the triple polish cap (polish.capMinutes + slots.smallShare), folded into the Polish share knob;
• the planner holds "plate full" and "nothing landed 48 h" (autonomy.ts:700);
• the stalls shun and breaker that duplicate repeat.ts;
• the Try: commit-line gate;
• the reviewer's "one miss = change request" on taste items (taste becomes a comment, not a block);
• the per-run design-principle bullets in briefs.

Each removal is its own small pull with a test showing the behaviour that replaces it. Release cadence is now at most one an hour (systemd MIN_MINUTES=60 on pg-grand), because each release restarts the pod and kills running runs and checks.

Reviewed pull #10605 at its head: ticked The crew page shows the five rows with value, one-line meaning and live effect, in two taps from home; the terminal's crew screen shows the same five lines.; Each knob is editable in place and the next pump reads it (a test turns Speed from 4 to 2 and the next start waits).; MCP: a knobs tool reads and sets the same five, in the same words.. left open: slots.smallShare and polish.capMinutes are gone; pace.floor, the reserve and queue.depth are derived from Speed and show as such. — pace.floor and queue.depth are derived and labelled, but slots.smallShare and polish.capMinutes still exist and the reserve is not derived.; autonomyCeilingUsd is gone from the autonomy card; the week's budget is a share of the week and a pace. — autonomyCeilingUsd and the two-per-slot reserve still stand; this pull was narrowed away from them..

Left open after pull #10605 landed: 2 unticked items remain (slots.smallShare and polish.capMinutes are gone; pace.floor, the reserve and queue.depth are derived from Speed and show as such.; autonomyCeilingUsd is gone from the autonomy card; the week's budget is a share of the week and a pace.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

Its two open boxes are now #10622 (small share and polish cap gone; pace floor, reserve and queue depth follow Speed) and #10623 (week's budget instead of a daily dollar ceiling).