[feat] Max Sprint Mode — go-as-hard-as-possible multi-agent campaign

[NoobyGains]

Context

While using Quorum to build Quorum-for-Apps (session 2026-04-17), user requested a first-class mode for "go all-out": dispatch max parallel agents on both vendors, show a live sprint dashboard, hard-budget-capped so it can't run away, auto-commit green work, surface blockers for human attention.

What it would look like

$ quorum sprint "build the week-1 slice from pln_e542ebfb" --budget $50 --max-agents 10
[sprint] dispatching 4 Claude build agents + 3 Codex review agents + 1 Codex template agent
[sprint] live: 8 in flight, 0 complete, spent $2.14 / $50
[sprint] claude-a1 ✅ scaffold.ts written (17s)
[sprint] codex-t1 ✅ template emitted as text (42s)
[sprint] claude-a2 ❌ scaffold.test.ts — failed, respawning
...
[sprint] complete. 8/8 agents green. $12.40 spent. 2 commits staged. 1 disagreement pending human.

Must-haves for MVP

• quorum sprint <goal> command
• Parallel dispatch of N Claude agents + M Codex agents with non-overlapping file ownership
• Hard budget ceiling that stops spawning new agents at 80% of cap
• Live status (TTY-friendly) + JSON status file for UI consumption
• Auto-commit green work; queue disagreements for human review
• Sprint artifact published at start (Plan subtype), Sprint-Result at end

Why it matters

This is the killer demo for "Quorum for Apps." Single-vendor chat boxes can't parallelize because there's no review mechanism to catch collisions. Quorum can because every write is a typed artifact with provenance.

Source: session building Quorum-for-Apps scaffolder — user (@NoobyGains) requested after watching a 2-Claude-1-Codex parallel dispatch and asking "why aren't you using max agents on both sides?"

Dependencies

• [feat] Worker spawn via git worktree + claude -p / codex exec #33 (worker spawn via git worktree)
• [feat] Campaign-scoped kill-switch + cost ceiling #40 (kill-switch + cost ceiling)
• [feat] Rate-limit-aware spawning (Merge Conductor backpressure) #30 (rate-limit-aware spawning)

This issue composes those primitives into one user-facing verb.