List view

• M7: Experimental and Post-1.0 Candidates

  Goal/outcome: isolate speculative or high-ambiguity initiatives from delivery-critical tracks. Scope: experimental/post-1.0 candidates pending validation (for example custom phases, pinned context semantics, alternate thresholds, sidecar SDK experiments). Dependency notes: intentionally after core/adoption milestones. Done when: each item is promoted with validated requirements or explicitly deferred/closed.

  No due date

  •3/8 issues closed
  37% complete5 open3 closed

• M3: Gateway Security, Reliability, and Release Operations

  Goal/outcome: reach production-grade security and operational readiness for the gateway path. Scope: security policy alignment, vulnerability and code scanning workflows, provenance/attestation, reliability baselines, diagnostics, and runbook-level operations. Dependency notes: builds on M2 and unblocks broad rollout confidence. Done when: security and reliability gates are automated and operational failure modes are covered.

  No due date

  •7/8 issues closed
  87% complete1 open7 closed

• M6: Ecosystem Integrations (Gated)

  Goal/outcome: expand integrations without destabilizing maintenance burden or core quality. Scope: new adapters/backends/packaging channels only when acceptance criteria, lifecycle ownership, and compatibility policy are satisfied. Dependency notes: gated behind M1-M5 maturity. Done when: integration candidates meet policy gates with owner/tests/docs.

  No due date

  •12/45 issues closed
  26% complete33 open12 closed

• M5: Developer Experience and Adoption Path

  Goal/outcome: reduce first-run friction and make contributor/operator workflows predictable. Scope: quickstart and adoption docs, governance/roadmap hygiene, release/changelog checks, upgrade/deprecation guidance, reproducibility, and support UX. Dependency notes: depends on concrete M2-M3 behavior to document correctly. Done when: onboarding and maintenance blockers are removed.

  No due date

  •16/34 issues closed
  47% complete18 open16 closed

• M4: Routing and Context Quality at Scale

  Goal/outcome: improve routing/context quality under large noisy catalogs and longer-running sessions. Scope: routing-scale eval harnesses, ambiguity/shortlist improvements, consolidation quality, deterministic memory clustering and promotion, and optimization guardrails. Dependency notes: best executed after M2-M3 runtime baselines. Done when: quality/scale targets are met with repeatable benchmarks and no determinism regressions.

  No due date

  •20/48 issues closed
  41% complete28 open20 closed

• M2: Drop-In Gateway Core and Interop

  Goal/outcome: make contextweaver a true drop-in MCP gateway front door for existing IDE/client MCP setups. Scope: live upstream support, config import/generation, transport compatibility baseline, and core execution hardening. Dependency notes: depends on M1 and unblocks operations/adoption tracks. Done when: multi-server setups can route/execute/view stably through one gateway.

  No due date

  •60/85 issues closed
  70% complete25 open60 closed