Milestones

List view

• Wave 7: Fixture completion, CI gates, and release readiness

  Purpose: complete trust, npm, publisher/composition, and manifest fixtures; enforce conformance CI; finish documentation and release readiness. Gate: V01–V06 complete and the plan completion definition satisfied.

  No due date

  •0/6 issues closed
  0% complete6 open0 closed

• Wave 6: Concurrency, liveness, and cross-surface safety

  Purpose: prove static workflow conformance, mutation fault handling, queue/GHES evidence, and controlled cross-surface contention. Gate: L04 complete; L04 is required by V01–V04.

  No due date

  •0/4 issues closed
  0% complete4 open0 closed

• Wave 5: npm-to-release-asset composition

  Purpose: implement the composition handoff, npm release-asset mode, and end-to-end composition scenarios. Gate: X03 complete; X03 is required by L01 and L02.

  No due date

  •0/3 issues closed
  0% complete3 open0 closed

• Wave 4: Release manifest and publisher

  Purpose: implement canonical release manifests and the producer-neutral release-asset publisher, including workflows and mutation convergence. Gate: M02 and R03 complete; both are required by X01.

  No due date

  •0/5 issues closed
  0% complete5 open0 closed

• Wave 3: npm provenance, signing, and real publication (M1)

  Purpose: implement npm provenance inputs, signing, OIDC/registry handling, convergence, the public workflow, and live M1 dogfood. Gate: P06 cannot be replaced by dry-run, mock registry, or local simulation.

  No due date

  •5/6 issues closed
  83% complete1 open5 closed

• Wave 0: External readiness, feasibility, and guardrails

  Purpose: establish dogfood readiness, trusted runtime feasibility, dependencies, platform evidence, module/CI guardrails, and fixture harness. Gate: F01, F02, and F03 block trusted implementation; F00 blocks only P06; F04–F06 and F05 must be green before Wave 1.

  No due date

  •7/7 issues closed
  100% complete0 open7 closed