docs(wp-0031): close routing metadata cleanup

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06bfe-2a55-7ed3-bacd-879977b099bf

workplans/ACTIVITY-WP-0031-production-execution-reliability-cleanup.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Production automation execution reliability cleanup"
 domain: infotech
 repo: activity-core
-status: active
+status: finished
 owner: codex
 topic_slug: activity-core
 created: "2026-08-20"
@@ -185,7 +185,7 @@ passed `10 passed` without warnings.
 
 ```task
 id: ACTIVITY-WP-0031-T05
-status: wait
+status: done
 priority: medium
 state_hub_task_id: "a7eb3615-dd11-54c9-80ec-a147d100f8b7"
 ```
@@ -211,13 +211,28 @@ both locations. `rein-aharness` commit `aedfadd` now supplies the non-secret
 OpenBao/AppRole defaults and includes `~/.local/bin` in `PATH`. The corrected
 unit is live and healthy. A value-free smoke proved `read` on the exact Binky
 IMAP path, `deny` on a sibling path, and presence of both required IMAP fields;
-the rein suite passed 224 tests with one skip. T05 remains `wait` only for its
-other named external metadata/retention handoffs.
+the rein suite passed 224 tests with one skip. At that point, T05 remained
+`wait` only for its other named external metadata/retention handoffs.
+
+Closed 2026-09-04 after verifying those handoffs against their authoritative
+sources. Repo Manager's completed fleet cutover reports all 42 eligible
+repositories and 306 live records unchanged at deterministic UUIDs, with zero
+remaining replacements or assignments. State Hub contains the canonical
+`RMASTER-WP-0020` workplan and task identities only.
+
+The retained production ops row
+`cf26417c-ed14-4b66-b1f0-4deaafac1201` remains deliberately `open`, targets
+`railiance-master`, has no claim owner or lease, and is not labelled
+`automated`. Its legacy `RAILIANCE-WP-0020` title/label are immutable emission
+evidence, not a second workplan identity. The owner source explicitly keeps
+`RMASTER-WP-0020-T08` at `wait` pending disaster-recovery proof and fresh
+destructive-cleanup approval; the activity grants neither. Routing and metadata
+ownership are therefore complete without changing or claiming the safety row.
 
 ## Acceptance
 
 - [x] Weekly SBOM fan-out is disabled in source and production
 - [x] Production status distinguishes schedule fires from execution failures
 - [x] Full test suite is green
-- [ ] Provider and consumer prerequisites have named owners and evidence
+- [x] Provider and consumer prerequisites have named owners and evidence
 - [x] Workplan and State Hub task state are consistent