feat(identifiers): prepare verified cutover batches

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
This commit is contained in:
tegwick 2026-08-22 14:57:56 +02:00
parent bdf3af19e2
commit 5e14d09bdf
10 changed files with 3097 additions and 0 deletions

View file

@ -431,6 +431,23 @@ evidence, restore points, hashes, and residuals are in
progress: widening beyond this single repository requires a new explicit fleet
cutover decision and refreshed source fingerprints.
**Batch 0002 prepared (2026-08-22):** the original fleet seal now rejects 15
repositories with legitimate source drift. A refreshed zero-collision plan
covers 41 repositories and 230 records. New `rmgr identifier
migration-batch-plan` pins an exact subset only after source verification plus
clean, Forgejo-synchronized Git preflight, and always emits
`apply_authorized: false` until a decision cites its batch hash.
`RMGR-DEC-2026-001` now offers the directly executable second pilot:
`whynot-design` only, one workplan UUID replacement, no task replacements or
assignments. Workstation and production both resolve the old UUID, reject the
derived UUID, and agree on 9 tasks, 11 progress events, and 1 decision. The
sealed batch hash is
`4039224352c6590fdc6b41e739539f1f9c92d098b43ed6e30b3cd9a87b53da65`.
No mutation has run; approval, revision, or rejection of that exact package is
the remaining gate. Evidence:
`docs/evidence/RMGR-WP-0005-batch-0002-readiness-2026-08-22.md`.
## Retire the interim rule
```task