Roadmap

What’s moving in zurdo, relative to the released v1.13.1 these docs describe. Items here are subject to change until they ship.

Just shipped: v1.13.0 / v1.13.1 (2026-07-31 / 2026-08-01)

The honest-pass milestone — three checks that stop a run from reporting work it didn’t do, plus the baseline fix that came out of the same review.

• A [shell:] hint that runs no tests now fails. cargo test <filter matching nothing> exits 0 having verified nothing. A libtest or go test report showing zero tests run now fails the hint with a test runner ran zero tests, whatever the exit code — at pre-flight, every iteration, verify, and heal. Details.
• A run-end warning names tasks that passed without any agent work. Terminal passed with zero attempts gets called out by name in the summary; a run where every task did that escalates to “nothing ran”. Diagnostic only — the exit code is untouched — and silent on resumes. Details.
• doc-echo, a sixth warn-lint family. Flags a criterion whose only proof greps a prose doc for a phrase the criterion itself names. Advisory, not --strict-promotable, pending field data on its false-positive rate. Details.
• Frozen-path comparison is tree-to-tree (v1.13.1). A frozen glob naming a path that was untracked at capture time no longer failed every attempt with nothing to revert, and a file the run created and never staged no longer escaped the check. run-diff.patch gained the same symmetry. Details.

These three checks exist because zurdo shipped a release claiming flags its binary did not have: four PRD tasks recorded themselves passed against [shell: cargo test <name>] criteria naming tests nobody had written. The v1.12.0 changelog carries the correction.

Recently shipped

v1.12.0 (2026-07-28) — the CI-ready surface. --format json on validate, verify, and state list, all emitting one shared versioned envelope, plus zurdo validate --strict to promote four of the six warn-lint families to errors. Details.

v1.11.0 (2026-07-28) — executor observability. Terminal post-mortem blocks that explain a dead task to a human rather than guiding an agent; out-of-tree path references recorded per attempt and surfaced on four read paths; and a reasoner evidence bundle that reads a structured tool-call projection instead of a raw stream tail — on one 348 KB transcript the old window showed 1.18%, 40% of it cost telemetry.

v1.10.0 (2026-07-28) — zurdo doctor and the provider vocabulary. A PRD-free, lock-free, write-free environment diagnostic that subsumes check-models, plus a shared provider event vocabulary verified against real captured streams — which is what surfaced three live adapter defects, including a codex adapter that could not extract assistant text at all. Details, providers.

v1.9.0 (2026-07-27) — structural hints are generally available. All seven graduation gates green, so [symbol:]/[references:]/[callers:] left [experimental]; [lumen] enabled is the only remaining switch. Details.

v1.8.0 (2026-07-25) — per-task frozen baselines. Frozen-path enforcement diffs against a baseline captured at each task’s first attempt rather than run start, and blocked-by-dependency is re-derived on resume, so fixing a failed dependency unblocks its dependents without --reset.

In development

The next milestone is being scoped — nothing is committed. Watch this page after the next release, or open an issue to influence what comes next.

Release history

Found a bug, or want to influence what ships next? Open an issue.