Post-W12 Next Increment Plan

Status

P0–P3 are complete on main. P3 S8 External Specialized Pack Lifecycle: COMPLETE (PRs #319, #355, #356, #357, #359, #361, #363; docs follow-ups #360, #362). P4 is not started and is not authorized by this document; it may now receive a separate maintainer brief. This document still does not authorize a publish, tag, new package, hosted-provider credentials, or a W13 workspace phase.

Verified against origin/main @ 89b6c1d (PR #318 merged, 2026-08-16).

Why this exists

ENGINEERING_WORKSPACE_IMPLEMENTATION_PLAN.md ends at W12. After W12 Client and the handoff PRs merged, there is no next W-phase. Continuing “by week number” would invent work the plan never defined.

The repository still has named, unfinished increments in other roadmaps. This file picks an order among those existing increments. It does not add a new product.

What is already done

Track	Evidence on main	Residual
Engineering Workspace W0–W12	PR #286–#313	No W13
Quality Packs Q1–Q18	PR #257–#275	Marketplace stays fail-closed
Specialized packs S1–S8	PR #277–#284, #319, #355–#357, #359, #361, #363	S8 complete; network/update/marketplace/TUI/MCP mutation deferred
Managed extensions E1–E8	PR #218–#248	No HTTP MCP install in npm 1.0.2
Assessments A1–A22	PROJECT_STATE baseline	Live assessProject still caller-owned
Harness H0–H9	PR #213–#244	Real adapters + runner deferred
Skills C1–C6	catalog + ADR-0051	C7 future
Desktop v0.6 + W clients	ADR-0042 + W1–W12 panels	Not in published 1.0.2
Memory M1–M4 / Security S1–S5	0.4.0-beta.1 line	Later expansions need threat review
Learning L1–L8	0.4.0-beta.1 line	Later candidates future
Neutron foundations	CLI neutron, workspace sync records	N1–N9 runtime not executed

Gaps that are not a new W-phase

1. Release honesty. Closed on PR #315. RELEASE_STATE.md snapshot 2026-08-16 keeps Implemented-in-main separate from npm 1.0.2. The next published version is undecided.
2. Workspace public gate leftover. Closed as deferred on P1. Real new-project and existing-project retrofit dogfood wait for an explicit maintainer brief. See docs/releases/dogfooding/2026-08-16-workspace-public-gate.md.
3. Neutron N1–N2. After Desktop v0.6, NEUTRON_RUNTIME_ROADMAP.md sequences N1 contracts then one real model adapter.
4. S8. COMPLETE. Step 8 of SPECIALIZED_ENGINEERING_PACKS_PLAN.md now has reviewed external packs through the managed extension lifecycle on CLI, daemon, Doctor, and Desktop. Update/replace, revocation, deactivation, network fetching, marketplace, MCP mutation, and TUI activation remain deferred and are not S8 blockers.
5. Quality debt. CLI_COMMAND_TS_DECOMPOSITION.md and oversized daemon / evidence-analysis / mcp-server files. Extract on the next meaningful touch.

Recommended order

P0 — Release honesty (docs + maintainer decision)

Status: complete on PR #315. RELEASE_STATE.md snapshot 2026-08-16 distinguishes Implemented in main from Released on npm (1.0.2 @ 192fd05). Next published version is undecided. Do not tag v0.6.0-beta.1. Do not publish from this document.

Exit: a reviewer can tell what is in git versus what is on npm. Met on PR #315.

P1 — Workspace public-gate evidence

Status: complete on this branch. The two real-dogfood bullets are deferred to the maintainer. Fixture and composed W1–W12 paths are recorded, not treated as a live walkthrough. No new engine.

Exit: the gate is closed with evidence, or marked deferred with an owner. Met as deferred in docs/releases/dogfooding/2026-08-16-workspace-public-gate.md.

P2 — Neutron N1, then N2

N1 status: complete on main via PR #317.

N2 status: complete on main via PR #318.

Exit: N1 contracts validate in fixtures. The “one configured provider” inspect loop is implemented for Ollama on loopback.

P3 — S8 external specialized packs

S8a status: complete on main via PR #319. previewExternalSpecializedPack pins a caller-supplied payload, exposes provenance/permissions/trust, routes the review through resolveExtensionAdoptionProposal, and keeps the pack untrusted-external until activateExternalSpecializedPack. No auto-install, no network fetch.

S8b status: complete on main via PR #355 (ef8d838). Canonical manifest digest and deterministic prepareExternalSpecializedPackLockEntry for .aif/extension-lock.json (reuse existing ExtensionLockEntry; no new schema family).

S8c status: complete on main via PR #356 (da78b73). Transactional apply via applyExternalSpecializedPackActivation reusing applyExtensionAdoptionPlan.

S8d status: complete on main via PR #357 (71d0876). CLI (intentloom specialized-packs external preview|activate) and daemon RPC (intentloom.specialized-packs.external.preview.v1, intentloom.specialized-packs.external.activate.v1) expose the S8a/S8c lifecycle without network fetch, pack byte copying, or MCP/Desktop/TUI mutation.

S8e status: complete on main via PR #359 (70e997d). Canonical Doctor inspects active external specialized-pack pins in .aif/extension-lock.json without mutation or network access. Local kind: local locators may be verified against project-scoped manifests; git/package locators remain metadata only.

S8f1 status: complete on main via PR #361 (8581df6). Desktop read-only external specialized-pack preview/review via existing daemon preview RPC.

S8f2 status: complete on main via PR #363 (d1581b8). Desktop explicit human approval and activation persist a referenced .aif/extension-lock.json pin. Maintainer Desktop tauri dev acceptance passed on a disposable project on 2026-08-22.

S8 overall status: COMPLETE. Path 3 gate (S8a–S8e + S8f1 + S8f2 + maintainer manual acceptance) is satisfied. Deferred post-S8 work is not a P3 blocker: TUI activation, MCP mutation, optional MCP/TUI read-only parity, update/replace, revocation, deactivation, remote discovery, network fetching, and marketplace.

P4 — File-budget extracts

Continue command.ts decomposition in the published order (clean, then inspect/timeline/conformance). Do not grow oversized production files.

Explicitly out of scope until a new ADR

• W13 or any new Engineering Workspace week
• live assessProject or model calls from Desktop
• autonomous commits, pushes, merges, releases
• C7 provider-plugin installation
• Harness real network / local-model / CLI-agent adapters
• Enterprise hosted coordination
• glib upgrade (wait for Tauri/gtk-rs)
• new monorepo, MFE, or second UI framework

First authorized action

P0–P3 are complete on main. P4 file-budget extracts may now receive a separate maintainer brief; do not start P4 implementation from this document. Do not start N3–N9, Desktop model UI, hosted adapters, MCP mutation, TUI activation, or specialized-pack update/revocation/network/marketplace work from this document.

Sources

• docs/roadmap/ENGINEERING_WORKSPACE_IMPLEMENTATION_PLAN.md
• docs/roadmap/ENGINEERING_WORKSPACE_CAPABILITY_MATRIX.md
• docs/roadmap/NEUTRON_RUNTIME_ROADMAP.md
• docs/roadmap/SPECIALIZED_ENGINEERING_PACKS_PLAN.md
• docs/roadmap/CLI_COMMAND_TS_DECOMPOSITION.md
• docs/releases/RELEASE_STATE.md
• PROJECT_STATE.md
• DUTY_WATCH.md current watch