Skip to content

v0.10.0

Latest

Choose a tag to compare

@nicoleman0 nicoleman0 released this 01 Nov 16:27
· 7 commits to main since this release
39fe824

Added

  • #138: Install asks whether to include OpenSpec. Use --no-openspec for plain plans; later updates keep that mode.
  • #82: Projects without openspec/ use a plain plan with scenarios and tasks. Roles and review checks support both modes.
  • #134: merge-queue.py restacks each child after its parent merges, before the parent's teardown, and refuses a child queued ahead of its parent. It waits up to 60 seconds for a lagging PR head after a push.
  • #124: state.py timings splits each phase into busy and wait time. The coordinator marks turns with state.py turn-end and turn-start.
  • #119: Opt-in stacked issues branch from a reviewed parent, restack after it merges, and block parent teardown while children depend on it.
  • #123: wait-agents.sh --timeout <seconds> returns when watched agents run past the limit, listing each with how long it has worked.
  • #121: merge-queue.py <issue>... rebases, checks, pushes, and waits for CI on each passing PR in order, then prints the merge command, or merges with --merge. union-resolve.py merges a CHANGELOG's Unreleased subsections instead of repeating their headings.
  • #120: Best-of-N, opt-in per issue. Two implementers on different providers build the same reviewed change, the reviewer keeps one, and the other is abandoned. Hooks get a CANDIDATE variable.

Changed

  • #130: Docs match the small-issue fast path and resumed fix rounds again: README.md stops saying the planner always stops at a plan and that you are asked at exactly three points, roles/implementer.md names the fast path in line 1, and SKILL.md no longer says every phase starts fresh.
  • #113: The maintainer can pre-approve a batch's merges by naming the condition in the coordinator conversation. The approval covers that batch only and can be withdrawn. With a repo that allows auto-merge, gh pr merge --squash --auto merges each PR when its CI finishes.
  • #115: Only blockers (an unmet scenario or task, a failed check, a scope breach, a security or data-loss problem) request changes. The coordinator may fix notes and small findings itself, up to about 10 lines.
  • #116: A small issue is planned and implemented in one session. It stops for a plan review only when it has questions.
  • #117: pre-review.sh runs the checks, the scope check, and OpenSpec validation before a reviewer starts. Projects put their checks in switchyard/hooks/checks.sh.
  • #122: switchyard/lessons.md carries traps from one batch to the next. The updater adds it when missing and never changes it.
  • #114: Fix rounds resume the implementer session that built the change. On Herdr the reviewer runs in a split pane beside it. Existing projects should change Codex's Later turns in switchyard/routing.md to codex exec resume <session> <flags> "<prompt>".
  • #79: state.py timings reports time per phase, provider, and model, with review rounds and the verdict. Teardown keeps a summary in .switchyard/history.jsonl.
  • #118: Open maintainer questions wait in one queue, .switchyard/questions.md, so the coordinator goes on with other issues meanwhile. state.py status shows an issue with open questions as waiting.