docs(STATE-WP-0079): cutover slice plan, close T02

Assign all 425 SHR-INV-0001 items to 19 slices across five waves plus Keep,
each with adapter flag, owner API, and rollback. Coverage computed against
the inventory rather than hand-counted.

Only Wave A (repo-manager, 165 items) is executable; B/D1/D2 are gated on
owner-side contracts still at proposed. Flags two findings for T04/T05: the
9 ops_dependency items cannot be strangled behind a flag, and the
legacy-meter weekly review window is 8h, not a week.

Also corrects the workplan status from proposed to active.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

workplans/STATE-WP-0079-retirement-strangler.md

@@ -4,7 +4,7 @@ type: workplan
 title: "State Hub retirement strangler and disposition execution"
 domain: infotech
 repo: state-hub
-status: proposed
+status: active
 owner: codex
 topic_slug: infotech
 created: "2026-08-09"
@@ -55,7 +55,7 @@ permanent ownership (INTENT retirement status).
 
 ```task
 id: STATE-WP-0079-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "595c3936-20b6-453f-92b5-84f86798054a"
 ```
@@ -64,6 +64,22 @@ Group SHR-INV-0001 items into cutover slices (repo/work → repo-manager;
 messages/progress/projections → hub-core; catalogs → owners; retire aliases).
 Per slice: adapter flag, owner API, rollback.
 
+**Result (2026-08-19):** `docs/retirement-cutover-slice-plan.md`. All 425
+inventory items assigned to 19 slices in five waves plus Keep, computed against
+`state-hub-disposition.yaml` rather than hand-counted. Each slice carries an
+`RM_SLICE_*` flag (off/dual/owner), owner API, and rollback; Wave A reuses the
+RMGR-WP-0002/0003 dual-run adapter rather than adding a mechanism.
+
+Owner readiness verified: only **Wave A (repo-manager, 165 items)** is
+executable — RMGR-WP-0001/0002/0003 are `finished`. Wave B is gated on
+HUB-WP-0004 (`proposed`), D1 on OPS-WP-0003 (`proposed`), D2 on FIN-WP-0003
+(`proposed`). Recommended first cut is A3 (registers), lowest blast radius.
+
+Two findings for T04/T05: the 9 `ops_dependency` items carry no capability and
+cannot be strangled behind a flag — they resolve at the T06 freeze window; and
+the legacy-meter review window is 8 hours despite `cadence: weekly`, which is
+not sufficient evidence to retire high-volume `/workstreams/` interfaces (E2).
+
 ## Register CLI and GOAL.md support
 
 ```task
@@ -130,7 +146,7 @@ evidence, stop service, archive repo read-only. Residuals → live owners.
 ## Acceptance
 
 - [ ] Freeze policy documented
-- [ ] Strangler plan covers all inventory capabilities
+- [x] Strangler plan covers all inventory capabilities
 - [x] prj-/GOAL.md register path works
 - [ ] Move/replace slices evidenced with tests/counts
 - [ ] Retire list closed or residual-owned