Milestones

List view

• M5 — Adoption & durability

  Long-tail durability, health monitoring, and adoption experience. Issues: #1605, #1748, #1608, #1606. ⚠️ #1606 is product-decision-blocked: do teams re-run Squad often enough that state persistence is worth the implementation complexity? That question must be answered by observed usage before #1606 can be scoped.

  No due date

  •4/7 issues closed
  57% complete3 open4 closed

• M4 — Review gate

  ⚠️ HARD GATE: Do not start M4 before M2 produces a VALIDATED verdict. M4's entire premise is that there is an autonomous merge path worth gating. That is precisely what the 2026-08-21 E2E run tests. If autonomy is falsified, M4 is REPLACED by a scope-contraction RFC — not delayed, not deferred, replaced. Issues: #1729, #1733, #1734, #1735, #1736.

  No due date

  •3/6 issues closed
  50% complete3 open3 closed

• M3 — Harden the proven path

  Post-E2E hardening on the path M2 validates as working. Exit criteria: Forced double /squad implement produces no duplicate squad/implement-{N} branches. Machine-readable PR provenance marker is present on every agent PR. Relay REFUSES a merge into a non-default branch. A well-formatted-but-bad plan is REJECTED by validate. Issues: #1730, #1731, #1757. Unblocked only after M2 produces a VALIDATED verdict.

  No due date

  •6/6 issues closed
  100% complete0 open6 closed

• M2 — E2E verdict

  ⚠️ Evidence-blocked by design. Contents populated by the 2026-08-21 E2E run. The measurable outcome is the DECISION RULE, not a shipped feature: every lifecycle stage tagged WORKING / BROKEN / NEVER-EXERCISED; every broken stage gets a filed defect with a repro; the falsification condition is evaluated. VALIDATED → proceed to M3 and M4. FALSIFIED → open a scope-contraction RFC instead of M4. M4 is REPLACED, not delayed.

  No due date

  •11/11 issues closed
  100% complete0 open11 closed

• M1 — Pre-E2E stabilization

  Ship all six wave:1-next fixes before the 2026-08-21 E2E run. Exit criteria: All six issues merged to dev. gh aw compile exits 0 on every squad* workflow. The #1732 compile gate demonstrably FAILS a deliberately-broken workflow in CI. bradygaster/aspiregregator-squad-e2e has 'Allow GitHub Actions to create and approve pull requests' enabled. Issues: #1772, #1758, #1759, #1732, #1761, #1756

  No due date

  •6/6 issues closed
  100% complete0 open6 closed

• 0.5.3

  Patch release: version indicator fix and pre-release semver support

  No due date
  0% complete0 open0 closed

• v0.4.1

  Bug fixes and quality - patch release

  No due date

  •13/13 issues closed
  100% complete0 open13 closed

• v0.5.0

  CI/CD hardening, memory improvements, feature work

  No due date

  •21/21 issues closed
  100% complete0 open21 closed