feat: support mixed identifier convergence
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c
This commit is contained in:
parent
4901b6d623
commit
5789e8c520
5 changed files with 313 additions and 11 deletions
|
|
@ -571,6 +571,22 @@ 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.
|
||||
|
||||
**Mixed projection convergence implemented (2026-08-31).** Fast forge-derived
|
||||
reconciliation can legitimately reach a deterministic target before the sealed
|
||||
identifier cutover reaches its authoritative file. Projection preflight now
|
||||
classifies every replacement as `legacy_source`, `derived_target`,
|
||||
`both_present`, or `neither_present`. The first two may coexist within the same
|
||||
repository-atomic batch; the latter two remain refusals. State Hub migrates only
|
||||
legacy rows, verifies already-derived rows against repository and canonical
|
||||
record identity, and writes the same durable alias provenance for both. Repo
|
||||
Manager exposes the explicit primary-only database phase as `rmgr identifier
|
||||
migration-projection`; the existing `migration-files` command remains the
|
||||
atomic file phase, and the projection phase is reversible if file writeback
|
||||
fails. Focused State Hub and Repo Manager suites cover mixed convergence,
|
||||
idempotent retry, ambiguity refusal, HTTP apply/reverse, primary identity, and
|
||||
exact plan-seal checks. A fresh sealed State Hub pilot remains before this slice
|
||||
is operationally complete.
|
||||
|
||||
**Batch 0005 preflight blocked safely (2026-08-22):** the refreshed zero-collision
|
||||
fleet plan covers 39 repositories and 215 live records. A projection-aware
|
||||
`adaptive-pricing` batch pinned its clean synchronized source and five UUID
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue