coulomb/repo-manager
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(identifier): record repo-manager cutover pilot

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
This commit is contained in:
tegwick 2026-08-22 10:01:30 +02:00
parent 4b5e48fd69
commit f8b914a52a
2 changed files with 118 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

21
workplans/RMGR-WP-0005-registrar-consolidation-deterministic-ids.md
View file

@ -403,6 +403,19 @@ plan after this implementation commit. The remaining gate is a single-repository
pilot that couples database apply, authoritative file rewrite, consistency
verification, and database rollback if the file phase fails.
**Pilot completed (2026-08-22):** the refreshed sealed plan covered 43/43
eligible repositories, 245 mappings (212 replacements, 33 assignments), and no
collisions. The authorized `repo-manager` slice migrated six existing
workplan/task rows and file identifiers atomically. All referenced rows followed,
six aliases are durable, the local cache is fresh, and both old/new API lookups
have the expected 404/200 result. The production registrar was upgraded with
sweeping still disabled and rebuilt the formerly absent projection from the
same deterministic workplan UUID and all 12 authoritative task UUIDs. Exact
evidence, restore points, hashes, and residuals are in
`docs/evidence/RMGR-WP-0005-repo-manager-pilot-2026-08-22.md`. T04 remains in
progress: widening beyond this single repository requires a new explicit fleet
cutover decision and refreshed source fingerprints.
## Retire the interim rule
```task
@ -459,6 +472,14 @@ State Hub database and verify hub-native centralization. The documented remote
tunnel at `127.0.0.1:18000` was not running during this pass, so no central
comparison was inferred.
**Production comparison (2026-08-22):** the registrar began with no Repo
Manager workplan projection. After the contained rebuild, `RMGR-WP-0005` and
all 12 task UUIDs exactly match the authoritative file, and a second read-only
pass reports no issue for that workplan. This proves discard-and-reconstruct for
the pilot record without identifier writeback. T07 remains in progress because
the full isolated projection rebuild and hub-native centralization proof still
cover more than this one workplan.
## Separate file-derived from hub-native data
```task