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

docs(registrar): record closed-workplan recovery

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 13:03:33 +02:00
parent c90f70122c
commit fa1f272ea4
3 changed files with 95 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -273,6 +273,21 @@ Prefer waiting for T03 where possible: once identifiers are derived, these
converge without manual intervention. Re-register by hand only what blocks work
before then.
**Scoped recovery (2026-08-22):** a request from `rail-kubernetes` exposed two
registrar wrapper defects. The missing scan incorrectly excluded a newly
finished workplan, producing a false `noop`; after that was fixed, unrelated
C-03 assessment failures produced a false `failed` even though the requested
projection was complete. Commits `69adfff` and `c90f701` now distinguish a new
closed parent from frozen child-only gaps and verify the exact requested UUIDs
before accepting assessment exit 1.
The production central hub now contains deterministic `RAIL-K8S-WP-0003` and
both done tasks, and the file writeback is pushed in `rail-kubernetes` commit
`29305d4`. A read-only repeat has no C-06/C-11 finding for that workplan. Its
two older workplans still carry production-absent random UUIDs and remain T04
work; T02 therefore stays `wait`. Evidence:
`docs/evidence/RMGR-WP-0005-rail-kubernetes-registrar-2026-08-22.md`.
## Derive identifiers deterministically
```task