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

feat(identifier): declare helixforge fleet namespace

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-21 23:57:03 +02:00
parent 3c6887a3e0
commit 956efbb7ae
9 changed files with 2915 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -277,7 +277,7 @@ before then.
```task
id: RMGR-WP-0005-T03
status: progress
status: done
priority: high
state_hub_task_id: "28067729-498d-4f47-89bd-5b9718e999c7"
```
@ -330,6 +330,14 @@ current fleet namespace boundary/name: ADR-011 intentionally leaves that an
open governance question, so Repo Manager does not infer it from a hostname.
No existing minted identifier was rewritten implicitly.
**Result (2026-08-21):** fleet owner Bernd Worsch declared `helixforge` as the
authoritative namespace. `config/fleet-namespace.yaml` records the decision,
root lineage, and accurate `N2 U1 R1 S1` posture with `N3 U2 R2 S1` target.
Identifier commands now use that declaration by default while retaining an
explicit override for foreign namespaces. The derivation contract, fixed UUID,
collision/unarchive guard, and independent reproduction test are all active;
bulk replacement remains the separately governed T04 operation.
## Migrate the fleet
```task
@ -358,6 +366,20 @@ malformed live identifier. Applying those plans remains gated on the namespace
declaration and a compatibility write path that updates file and central
projection together.
**Progress (2026-08-21, namespace declared):** the `helixforge` fleet preflight
scanned 114 repository roots and found 242 live identifiers with zero
collisions. Fourteen non-canonical NetKingdom task ids were the sole initial
repository blocker and were normalized in commit `25ed928`. The regenerated,
SHA-256-sealed mapping is source-ready across 42/42 affected repositories: 209
UUID replacements and 33 assignments, with per-repository HEAD/source
fingerprints verified by `rmgr identifier migration-verify`.
Apply is still deliberately unauthorized. State Hub's workplan/task primary
keys are referenced by numerous foreign keys without `ON UPDATE CASCADE`; a
file-first or direct-PK rewrite would split the projection. Evidence and the
required transactional/alias/rollback contract are recorded in
`docs/evidence/RMGR-WP-0005-helixforge-migration-readiness-2026-08-21.md`.
## Retire the interim rule
```task