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

fix: preserve scoped Custodian historical work identities

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-luna
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
tegwick 2026-09-09 12:47:43 +02:00
parent 6854ea10b2
commit 89524d83e4
5 changed files with 657 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

71
workplans/RMGR-WP-0014-custodian-historical-identity-compatibility.md Normal file
View file

@ -0,0 +1,71 @@
---
id: RMGR-WP-0014
type: workplan
title: "Preserve Custodian historical identities during ordinary synchronization"
domain: infotech
repo: repo-manager
status: finished
owner: codex
topic_slug: infotech
created: "2026-09-09"
updated: "2026-09-09"
---
# Custodian historical identity compatibility
Origin: the user's HFACT-WP-0001 critical-path continuation and delegated legacy
ID side quest; historical reconciliation remains CUST-IN-0017 in the-custodian.
Review found valid historical suffix IDs and parent-local TNN aliases rejected by
the new global identity gate. Preserve the existing source labels and UUIDs.
## Audit the exact source and Hub bindings
```task
id: RMGR-WP-0014-T01
status: done
priority: medium
```
Read-only audit covers nine historical workplans and 54 existing task UUIDs.
The 38 local aliases are qualified by their original parent in the projection.
The actual State Hub derive/merge path retained all 54 task UUIDs, parents and
statuses in memory against a current HTTP snapshot; no rows were created or
cancelled. Three unrelated missing qualified ad-hoc source bindings already
match the deterministic UUIDs held by the Hub and may be restored by the normal
identifier tool. See docs/evidence/2026-09-09-custodian-legacy-identities.json.
## Add bounded compatibility without weakening new identities
```task
id: RMGR-WP-0014-T02
status: done
priority: medium
```
The kind registry enumerates the historical suffix IDs and each observed local
alias range. Parent scoping applies only to those accepted local aliases with
an existing managed UUID. Canonical qualified IDs remain globally checked.
Unknown aliases, same-parent UUID collisions and missing local UUIDs refuse
ordinary registration. The Custodian machine canon carries the same historical
interpretation; no new identifier convention is introduced.
## Verify safe registration and hand off broader reconciliation
```task
id: RMGR-WP-0014-T03
status: done
priority: medium
```
Repo Manager suite: 169 passed. Portable tests cover global canonical collisions,
parent-local collisions, unknown parent/alias, missing UUID, immutable source
bindings and all 38 aliases. Full Custodian dry run now passes the identity gate.
Ordinary sync must still prove its exact pushed commit and primary receipt.
No retirement acknowledgement is granted by this compatibility change.
Residual handoff: CUST-IN-0017 remains open for historical duplicate projection
rows (including CUST-WP-0010b source UUID def8455a-9de4-4891-a15a-5b09ca98ab1e
versus stale duplicate 416ff571-18cf-5cb2-9c8b-836f68a301b3), retired/orphan
history and the CUST/THE instruction-generation conflict. HFACT-WP-0001-T02
retains task-field projection completeness and semantic idempotency keys. This
workplan closes only the bounded identifier-compatibility defect.