# RMGR-WP-0005 batch 0007 fleet-completion cutover

Date: 2026-08-31  
Decision: `RMGR-DEC-2026-006`  
Source plan SHA-256: `ab8ae2e55470553f105c6209d6aa4c7b828085bd6c71cec7b16173b8a19bef7b`  
Approved batch SHA-256: `c0cc496a06d9535a40840a0c7488cf365d8e47c5c58cc29aca72fb6d98273700`

## Outcome

Bernd Worsch approved the decision as written. Batch 0007 completed all 85
identifier replacements across its ten named repositories, with zero
assignments and no rollback. Each repository passed source, Git, primary
identity, and projection preconditions immediately before execution. The
railiance01 projection transaction completed before the atomic file rewrite;
each repository was then committed, pushed, reconciled from the exact Forgejo
commit, and checked for legacy=404, deterministic=200, and matching canonical
record identity.

| Repository | Replaced | Commit | Reconcile |
| --- | ---: | --- | --- |
| `fin-hub` | 13 | `bbfa2d6` | applied, zero refused |
| `net-kingdom` | 16 | `ce198fc` | applied, zero refused |
| `prj-canon-federation` | 13 | `921f007` | applied, zero refused |
| `prj-forgejo-org-refactor` | 6 | `b9e9b73` | applied, zero refused |
| `prj-state-hub-retirement` | 8 | `354e13d` | applied, zero refused |
| `prj-unattended-progress-company` | 13 | `2901cc9` | applied, zero refused |
| `railiance-master` | 3 | `51747ca` | applied, zero refused |
| `railiance-telemetry` | 4 | `aa59e80` | applied, zero refused |
| `rapp-qonto` | 4 | `1a6fa41` | applied, zero refused |
| `soul-frame` | 5 | `7e4ed86` | applied, zero refused |

`rapp-qonto` exercised the guarded duplicate-convergence path deployed in State
Hub commit `a7c91a6`: one legacy workplan migrated normally and three exact,
unreferenced task duplicates were coalesced transactionally. All four legacy
endpoints now return 404 and all four deterministic endpoints retain the
canonical record identity.

## Bounded sync-wrapper finding

After `net-kingdom` was pushed, the high-level `rmgr sync` wrapper refused its
pre-projection identity scan because archived historical id
`NK-WP-0003-T08a` is noncanonical. This was not source drift, a migrated record,
or a projection failure. The underlying guarded forge-derived reconcile accepted
the exact pushed commit, updated the projection with zero refusals, and direct
verification passed all 16 mapped records. The checkout is clean and
synchronized. Residual `RMGR-IN-0003` tracks scoping normal sync validation so
unrelated historical conformance findings do not block canonical work.

## Fleet closure proof

The fresh post-cutover plan is
`docs/evidence/RMGR-WP-0005-fleet-postcutover-2026-08-31.json`, sealed as
`9dbe8b9dd43997fc80617d18070e7359394b6473c06b54b03ace5288a321b263`.
It reports:

- 42 repositories eligible, zero skipped;
- 306 live work records;
- 306 unchanged deterministic identifiers;
- zero replacements and zero assignments.

## Interim-rule retirement

State Hub commit `5dd04dc` removes the C-06/C-11/C-32 single-writer registrar
guard. Its convergence test runs two independent hub stores against identical
repository sources with `STATEHUB_REGISTRAR=0`, proves byte-identical UUID
writeback, verifies each store contains exactly one workplan and one task, and
proves a second pass creates no duplicate or byte change. The complete State Hub
suite passes (828 tests) and the dashboard production build succeeds.

The exact image `main-5dd04dc` is live on railiance01 as Helm revision 55. The
deployment rollout succeeded; live health reports `primary/railiance01` with
schema `a4d5e6f7b8c9` current. State Hub commit `d8e1810` pins the chart and
values declaration to the deployed image.

No migration rollback was required.