Milestones
List view
Desktop graph and deployment tail: Aspire packaging, installers, update transactions, provisioning, health/control surfaces, containment, Windows service tier, and graph-deploy conformance.
No due date•0/22 issues closedProcess manager and bare-metal supervision after runtime automation: process graph, lifecycle engine, control plane, CLI, deploy adapters, telemetry, and the DevTools process-control consumer.
No due date•0/40 issues closedTyped extension and generation foundation. Ship order: RFC 0001 SDK/client slices S1–S8; plugin CLI contribution RFC #1502; route/client/UI scaffold corrections (#1354, #1355, #1357, #1358, #1360); then actionable follow-ups (#1429, #1448, #1451–#1453, #1455, #1458, #1461–#1462, #1481, #1533, #1544, #1551), SQLite scaffold cleanup #1588, Fresh navigation coordinator #1590, typed OpenAI Responses mapping #1591, durable typed worker progress #1592, and existing MySQL/docs/public-surface fixes. Invalid cache-suppression proposal #1550 is closed and intentionally excluded; its remaining direct policy/browser regression coverage is #1557. Consumer fixes may land in parallel but must not bypass the accepted SDK/CLI seams. Dependent auth, deploy, and DevTools consumers remain later.
No due date•48/99 issues closedProduction runtime and command foundations. Ship order: security and correctness blockers (#1365–#1388); RFC 0002 automation A0–A3 (#1503–#1512); RFC 0003 command core C1–C4/C7 (#1482–#1488); then service layering, plugin health/ports/durability/telemetry, and E2E truth (#979, #1362–#1372). Post-release adoption measurement lives in 0.0.9, not here.
No due date•1/32 issues closedFrontend Contribution Layer — plugins that ship userland UI. RFC #890, epic #922: proofs, contracts/spine, registry emission, host runtime, secure gateway, scaffold wiring, DX, lifecycle, and test kit. This milestone also owns Wave-7 adoption measurement #1381 against published 0.0.8 artifacts; auth/AI/runtime/DevTools consumers follow only after their backend prerequisites.
No due date•6/27 issues closedDevTools and late integration train after runtime and frontend foundations: RFC 0005 host/contribution spine, inspectors and runtime consoles, migration documentation, and remaining cross-epic consumers. DevTools deep-links to Aspire/Scalar and never duplicates their owned surfaces.
No due date•4/45 issues closedAdvanced auth and deploy adapters: Better Auth, organization policy, conformance, machine/agent authentication, and Cloudflare/Vercel/AWS targets with live probes. No DevTools work belongs to this milestone.
No due date•0/11 issues closedExpansion consumers: deploy container/platform clients, WorkOS SSO/SCIM/audit/secret lifecycle, and frontend-contribution auth/AI surfaces. Every consumer depends on the accepted CLI, SDK, and frontend contribution contracts.
No due date•0/10 issues closedEnterprise auth foundation after RFC 0001: Entra/OIDC and tenant-aware multi-backend routing, plus any prerequisite typed SDK/auth contribution work not already shipped. No auth frontend or enterprise adapter may bypass the accepted SDK seam.
No due date•0/3 issues closedDeploy-plugin foundation and container/runtime integration after the shared CLI and frontend seams: host contribution contracts, adapter extraction, plugin wiring, scaffold/E2E, events/telemetry, and the first frontend runtime panels.
No due date•0/15 issues closedRuntime and command completion after 0.0.8: RFC 0002 automation A4–A6/A8, RFC 0003 relay/provider/CLI/docs slices, and early deploy contribution plumbing. Work here must consume the SDK and CLI contribution foundations rather than invent parallel seams.
No due date•7/28 issues closedUpstream-blocked or genuinely undecided work, independent future programs such as RFC 0004 hybrid MCP retrieval, and multi-release umbrella issues. Scheduled implementation children belong on concrete 0.0.x milestones; this is not a dumping ground for ready urgent fixes.
No due date•23/107 issues closed