close rename plan and restate retirement gates

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c

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: active
+status: blocked
 owner: codex
 topic_slug: infotech
 created: "2026-08-09"
@@ -116,7 +116,7 @@ registration suite passes (`20 passed`).
 
 ```task
 id: STATE-WP-0079-T04
-status: progress
+status: wait
 priority: high
 state_hub_task_id: "3a454438-1955-547f-a491-8eab7cd25710"
 ```
@@ -365,11 +365,31 @@ the daily filename unchanged. A regression test covers the filename/id pairing.
 This prevents new collisions without making State Hub the long-term convention
 owner.
 
+**Owner-gate reconciliation 2026-08-31.** The previously open receiving-side
+gates have advanced materially: RMGR-WP-0005 finished the deterministic
+identifier migration, HUB-WP-0005 put all hub-core route and writer groups into
+production ownership with exercised rollback, and ACTIVITY-WP-0029 finished
+the schedule, consistency-sweep, interaction-event, and execution-boundary
+handoffs. Those are durable owner records and no longer block this task.
+
+They establish receiving-side readiness only. They do not, by themselves,
+prove that State Hub callers and route families have switched or that the
+required parity, rollback, and production receipts exist.
+
+The remaining move/replace slices are not executable in State Hub. OPS-WP-0003
+is still `proposed` with all three tasks `todo`, and FIN-WP-0003 is still
+`proposed` with all three tasks `todo`; they own the service-catalog and fabric
+authority cutovers. State Hub's freeze policy forbids implementing those owner
+surfaces here. T04 is therefore `wait` on those two live owner workplans, the
+remaining hub-core/activity-core State Hub route-switch receipts, and explicit
+authorization for any production writer cutover. It must resume from a fresh
+owner-readiness and caller scan, not from the obsolete 2026-08-20 snapshot.
+
 ## Retire legacy surfaces
 
 ```task
 id: STATE-WP-0079-T05
-status: progress
+status: wait
 priority: medium
 state_hub_task_id: "f6cf8c01-eb59-5ca8-a541-23928d4a000c"
 ```
@@ -459,13 +479,21 @@ live SBOM callers, live `GET /tasks/?workstream_id`, the three high-volume
 workstream reads still inside their 60-day quiet window, and two workstream
 mutations still inside 30 days. Evidence:
 `docs/evidence/legacy-meter-weekly-review-20260831.json`. T05 remains
-`progress`; T06 must not start.
+`wait`; T06 must not start.
+
+The nine held interfaces are explicitly owned by this task until the meter
+allows retirement; they are not untracked prose residuals. Three SBOM reads and
+`GET /tasks/?workstream_id` still had calls in the seven-day review window.
+Three high-volume workstream reads have only 9 of 60 required quiet days, while
+the two workstream mutations have 14/30 and 15/30 quiet days. A future review
+must recapture central-primary evidence and apply the existing volume ladder;
+calendar passage alone is not retirement evidence.
 
 ## Stabilization window and archive prep
 
 ```task
 id: STATE-WP-0079-T06
-status: todo
+status: wait
 priority: high
 state_hub_task_id: "9230c99b-af58-5794-9291-452e619a30fa"
 ```
@@ -473,6 +501,13 @@ state_hub_task_id: "9230c99b-af58-5794-9291-452e619a30fa"
 With T06 gates: zero normal read/write window, final dump, backup/restore
 evidence, stop service, archive repo read-only. Residuals → live owners.
 
+**Blocked 2026-08-31.** The sole `railiance01` primary is healthy and remains
+the active coordination service, the legacy meter has live callers, and T04
+still has owner-side cutovers. A freeze, final dump/restore rehearsal, service
+stop, or repository archive would therefore interrupt normal work and destroy
+the evidence needed by T05. T06 remains `wait` until T04 and T05 are done and a
+fresh central meter demonstrates the required zero normal read/write window.
+
 ## Acceptance
 
 - [x] Freeze policy documented