Milestones
List view
A qualified, stable static capability-review release. Track proven trust and first-run blockers, the report 1.0 compatibility freeze, exact beta-wheel evidence, release rehearsal, operator readiness and an explicit product go/no-go. Conditional expansion is tracked separately; no due date bypasses qualification.
No due date•21/35 issues closedConditional expansion after observed repeat use: #474 first proves a remaining MCP configuration or reviewed-inventory gap using existing host readers and capability payloads. A lock-style artifact is optional and must earn its surface. Broad organization state and governance are deferred; completed setup/review presentation work is not carried forward as unfinished scope.
Due by December 31, 2026•1/4 issues closedActivation and reviewer trust: repair supported entry paths and published-version parity; make the human quickstart runnable; close one authenticated GitHub review loop; measure first value and the next eligible change in the existing pilot (#521). Reuse the delivered capability schema, attestations, incident fixtures and local-review path. Release-exit measurement remains #312; no safety catch bar is relaxed. Standards mapping is queued independently rather than blocking activation.
Due by November 6, 2026•32/34 issues closedRelease integrity and gate correctness. The final tag requires an approved qualification policy, tagged-source/qualified-wheel binding, deterministic rehearsal and test evidence, a recoverable publication transaction, and a wheel-scoped signed SBOM.
No due date•13/15 issues closed