Milestones
List view
Promoted ahead of the prose batch on the maintainer 2026-08-15 filter: rank by whether an issue directly improves delivery speed or autonomy. #616 cut 1 (per-leg isolation, timeout/heartbeat, cleanup) IS the fix for #634 — concurrent legs mutating one worktree corrupt mutation evidence in both directions. #616 cut 2 (bound verdict metadata) is gate-hardening and folds into CUT C of the #558 ruling instead.
No due date•0/3 issues closedSHIPS ON PROVEN CONSUMPTION, NOT ON open_issues == 0. The terminal gate is #545 — the maintainer's own daily use of the shipped harness in other repos. It cannot be done for them. The tag is NOT a second gate. The maintainer's standing publish authorization is unqualified and is not narrowed here. An earlier version of this description held the tag back on the premise that npm forbids returning to 1.x — that premise is FALSE. npm refuses to republish an exact name/version; a later 1.99.4 after 2.0.0 is legal, and `npm dist-tag` can move `latest` anywhere. 2.0.0 is unrepeatable, not a one-way door. Sequencing: v1.99.3 (#616, #634, #537 — review-leg supervision) ships FIRST and separately. It makes every review cycle on this milestone cheaper, so folding it in inverts the order. Delivery mechanics: #673 (version bump, CHANGELOG, tag push, npm + plugin verification — merging publishes nothing, release.yml fires on the tag), #638 (npm is automated; Homebrew and the gh extension are months stale, so a 2.0 shipping to one channel is a 2.0 most consumers never see), #622 (the post-mortem runs or the maintainer waives it explicitly). Original triage, still standing: #516 first (cli/init.js removeObsoletePaths hard-deletes retired paths with no content-hash check, so a customized retired skill is lost silently on update), then #554 (CC drift review; the last gap hid a live shipped defect). #456 rides the #554 session as a retest against the current baseline. Reconciled by both review legs 2026-08-11, see #578.
No due date•2/15 issues closedShips AFTER PR-A so the gate edits are reviewed under the new contract. #533 shipped 2026-08-11 (PR #583). Dependency order now: #581 -> #547, then #540 -> #563. #582 is UNSEQUENCED pending a design ruling — the two review legs split on whether it rides with #581 or needs its own call. #540 is design-ruled on the issue; read the ruling there before writing code. This description previously restated that ruling and restated the version #540 refuted — it routes now instead (#580). No gate redesign.
No due date•6/7 issues closed