apply reef identifier batch 0006

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

docs/evidence/RMGR-WP-0005-batch-0006-reef-railiance-cutover-2026-08-31.md

@@ -0,0 +1,70 @@
+# RMGR-WP-0005 batch 0006 reef-railiance cutover
+
+Date: 2026-08-31
+
+## Authorization
+
+Bernd Worsch approved `RMGR-DEC-2026-005` as written. The approval is limited
+to batch seal
+`102061f3ed93eac091e9ceb05d9d3130241a23134b9f7d5a624d91c4ef824759`,
+source-plan seal
+`af3c8e3fe6f423845a97258a10322eeded4b7814d13bf9541b5d550c285cc0b9`,
+repository `reef-railiance`, two replacements, and zero assignments. State Hub
+decision `a0616e13-cd0c-441a-8339-f0e502bb2bbf` is resolved with
+`decision_type: made` and `decided_by: Bernd Worsch`.
+
+## Final preflight
+
+`rmgr identifier migration-batch-verify` returned `ok: true`,
+`ready_for_decision: true`, the exact batch and plan seals above, repository
+`reef-railiance`, and no errors. The file phase dry-run reported one file, two
+replacements, zero assignments, and no write.
+
+The source was clean and synchronized at sealed HEAD
+`3e98b10d81990c45465f3f620441d97347670b52`. The primary health identity was:
+
+- role: `primary`
+- label: `railiance01`
+- schema: `a4d5e6f7b8c9` current
+
+## Execution
+
+The first projection command omitted the explicit instance-label override. It
+refused before mutation because the Repo Manager default was misspelled
+`railliance01`. Repeating the command with
+`--expected-instance-label railiance01` passed every source and Git precondition.
+The default spelling is corrected in this closeout change set.
+
+The forward projection receipt reported:
+
+- `replacements: 2`
+- `migrated: 2`
+- `already_derived: 0`
+- `assignments_deferred: 0`
+
+The atomic file phase then touched only
+`workplans/REEF-RAILIANCE-WP-0003-rapp-qonto-production-gates.md`, replacing:
+
+| Record | Legacy UUID | Deterministic UUID |
+| --- | --- | --- |
+| `REEF-RAILIANCE-WP-0003` | `c3f9fbfd-3db1-4387-8b65-7d53ba57138d` | `8ac413ad-2f57-53e6-b586-c5bec9cfbd1f` |
+| `REEF-RAILIANCE-WP-0003-T04` | `9d0c1f61-0ed8-4d5c-b4c2-2578424ad3b4` | `9d792070-5f2b-5b3d-ba52-92c8b0d4a6b8` |
+
+`statehub fix-consistency` completed after the rewrite and refreshed the reef
+brief in automatic commit `cec61da`. The authoritative UUID change is pushed to
+Forgejo in reef commit `dcf51b3`.
+
+## Post-cutover verification
+
+- The deterministic workplan and task endpoints return their original record
+  identities, content, and lifecycle states.
+- The migrated task has
+  `workplan_id: 8ac413ad-2f57-53e6-b586-c5bec9cfbd1f`.
+- The two legacy UUID endpoints return 404, as expected: durable migration
+  aliases support governed reversal but are not public read redirects.
+- The reef repository is clean and synchronized with `origin/main` after push.
+- The authoritative diff contains exactly two UUID replacements and no content
+  or status changes.
+- Repo Manager verification passed: `148 passed` and Ruff reported no issues.
+
+No rollback was required.

docs/evidence/RMGR-WP-0005-cache-centralization-2026-08-31.md

@@ -3,7 +3,7 @@
 Date: 2026-08-31
 
 The workstation no longer runs a State Hub API. `127.0.0.1:8000` is the
-operator's SSH relay to the sole `railliance01` primary, whose health reports
+operator's SSH relay to the sole `railiance01` primary, whose health reports
 `instance_role: primary`, `instance_label: railiance01`, and a current schema.
 The retired production sweep remains disabled and has no checkout or SSH
 hostPath mount.