docs(plan): extension restructure — 6-phase implementation plan
24 tasks across 6 phases derived from the 2026-05-04 extension restructure spec. Per-task bite-sized steps (TDD where new behavior, verify-existing- tests where pure relocation) with explicit file/line citations and full code snippets. Phase 1 (StateHost typing, S-M, blocks 3+4): 5 tasks Phase 2 (storage.ts + itemToManifestEntry, S): 3 tasks Phase 3 (setup wizard SW migration + step registry, L): 7 tasks Phase 4 (vault.ts split into 5 modules + vault_locked lift, M): 7 tasks Phase 5 (P2 cluster: timer/gitHost/teardown/allSettled/debounce, M): 5 tasks Phase 6 (get_vault_status + sidebar status indicator, S-M): 3 tasks Task 7.1 (final verification sweep against spec Done criteria). Recommended sequence: 1 → 2 → 5 → 4 → 6 → 3 (independents first, then the typed-StateHost-dependent phases, then Phase 3 last because it's the biggest single phase and benefits from all the supporting infra in place). Max subagent parallelism: 3 streams. Cross-plan: explicit out-of-scope notes for Plan A (security/docs polish, already shipped) and Plan B (CLI restructure, already shipped). The wasm.d.ts file is not touched by this plan (verify empty diff at done). STATUS + ROADMAP updated to point at the plan. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
@@ -18,7 +18,7 @@ Per the 2026-05-30 post-v0.6.0 audit: of the three 2026-05-04 architecture-revie
|
||||
|
||||
- **Extension restructure** — `vault.ts` split (5 modules), setup.ts SW-abstraction routing, type-checked `shared/state.ts`, SW router-helper dedup, `relicario status` parity, plus P2 cleanups (inactivity timer / gitHost-on-expiry / debounced detector). Effort: **L (multi-day to multi-week)**.
|
||||
Spec: `docs/superpowers/specs/2026-05-04-extension-restructure-design.md`
|
||||
Plan: not yet written — that's the next concrete move.
|
||||
Plan: `docs/superpowers/plans/2026-05-30-extension-restructure.md` (6 phases, 24 tasks)
|
||||
|
||||
## Medium-term
|
||||
|
||||
|
||||
Reference in New Issue
Block a user