Repository navigation
v1.10.0
md-agent v1.10.0 — seats that reach each other, heal, and stay cheap
From a field audit of two live review runs (docs/analysis-2026-09-05-v1.9.0-field.md), then measured again.
Seats reach each other's work. A verified reply is committed on the seat's branch by the harness and the orchestrator's event names the sha; the completion gate commits every changed workspace before judging; claude seats can read sibling worktrees. The orchestrator is told to sequence a consumer after its producer replies.
Auto-heal. roles[].fallback (or a run-level fallback) is a ladder of {provider, model}. A provider that is dry at preflight moves its seats to their rung before launch; a seat that runs dry mid-run reseeds itself on the rung from its transcript and replies with [SEAT HEALED].
Honest accounting. A turn stopped by its cap reports [TURN CAPPED] with its partial work on disk, and its spend is booked. The gate waits for busy seats. Idle turns re-invoke in seconds, not ten minutes. The soft budget carries a wind-down rule.
Explicit readiness. VERIFY-READY on its own line is the completion claim; slice reports are attached, never bounced.
Lean seats. No skills by default; projectInstructions: false drops a large CLAUDE.md from a read-only seat's every call; readOnly: true gives a judging seat Read/Grep/Glob only; per-tier turn budgets; recycle at 120k resident tokens; a READ DISCIPLINE block in every mandate. Measured on the same review: $11.67 → $9.78, re-read tokens −39%.
Tiering, measured. Opus on every judging seat; sonnet/haiku only behind a mechanical check. The planner, init, the skill and the README encode it.
Guards. The verify command is dry-run at launch and a malformed one refuses the run. Older items closed: huddle timeout, quota probe false positives, expired self-stops revived on resume, verify output attached only to the failing seat, process-group kill on verify timeout, a second completion request answered rather than dropped.