docs(identifiers): record railiance-cluster cutover
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
This commit is contained in:
parent
c3e22baf5a
commit
63c00f9c9d
2 changed files with 126 additions and 0 deletions
|
|
@ -504,6 +504,24 @@ uses `ON UPDATE CASCADE`. The fail-closed batch hash is
|
|||
identifier mutation has run. Evidence:
|
||||
`docs/evidence/RMGR-WP-0005-batch-0004-railiance-cluster-readiness-2026-08-22.md`.
|
||||
|
||||
**Batch 0004 completed (2026-08-22):** `RMGR-DEC-2026-003` approved the exact
|
||||
sealed `railiance-cluster` package. Fresh workstation and production restore
|
||||
points were created and verified before both projection transactions replaced
|
||||
the workplan and five live task UUIDs. The authoritative six-line file
|
||||
transaction was pushed in commit `2bcc3f0`; the two cancelled task UUIDs stayed
|
||||
unchanged beneath the derived parent.
|
||||
|
||||
Both projections now return old/new API lookups 404/200 for all six mapped
|
||||
records, retain seven child tasks, two cancelled tasks, one decision, five
|
||||
mapped-task progress references, and their original 14/12 workplan progress
|
||||
histories, and carry six applied aliases. Repeated consistency found no
|
||||
remaining issue in the migrated slice. Production retains six pre-existing
|
||||
C-03 failures for unrelated repository records that are absent from that
|
||||
projection. Full restore hashes, commits, checks, and the bounded transport
|
||||
note are in
|
||||
`docs/evidence/RMGR-WP-0005-batch-0004-railiance-cluster-cutover-2026-08-22.md`.
|
||||
T04 remains in progress for separately sealed and approved fleet batches.
|
||||
|
||||
## Retire the interim rule
|
||||
|
||||
```task
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue