feat(identifier): declare helixforge fleet namespace

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d

docs/evidence/RMGR-WP-0005-helixforge-migration-readiness-2026-08-21.md

@@ -0,0 +1,54 @@
+---
+id: RMGR-EVIDENCE-0005-HELIXFORGE-MIGRATION-20260821
+type: evidence
+workplan_task: RMGR-WP-0005-T04
+created: "2026-08-21"
+---
+
+# HelixForge deterministic-identifier migration readiness
+
+Fleet owner Bernd Worsch declared `helixforge` as the authoritative current
+namespace. Repo Manager records it in `config/fleet-namespace.yaml`; omitting
+`--namespace` now resolves to that checked-in declaration.
+
+## Source preflight
+
+- 114 repository workplan roots scanned under `/home/worsch`;
+- 242 live workplan/task identifiers;
+- zero live identifier collisions;
+- one initial ineligible repository (`net-kingdom`) due to 14 legacy task ids
+  written as `-T1`…`-T8`;
+- those ids and their four documentation references were normalized to
+  `-T01`…`-T08` in NetKingdom commit `25ed928`;
+- regenerated plan: 42/42 repositories eligible, 242 records, 209 replacements,
+  33 assignments, zero skipped;
+- plan SHA-256:
+  `98a7d876d49fbec9c062f970c18e25750da4cd4b5c89ab0d4ed24d50183abbda`.
+
+The full old-to-derived mapping is
+`docs/evidence/RMGR-WP-0005-helixforge-uuid-migration-plan-2026-08-21.json`.
+It carries canonical UTC generation time plus per-repository Git HEAD and
+authoritative-source fingerprints. `rmgr identifier migration-verify` validates
+the seal and all 42 source preconditions.
+
+## Central-projection gate
+
+No UUID was rewritten. State Hub uses these UUIDs as primary keys, with
+references from tasks, progress and token events, decisions, dependencies,
+launch requests, intakes, capability requests, contributions, technical debt,
+extension points, and legacy suggestions. The checked-in foreign keys specify
+delete behavior but no `ON UPDATE CASCADE` behavior.
+
+Consequently, changing the repository fields first would detach the central
+projection, while directly updating database primary keys would fail or leave
+references split. Apply remains unauthorized until State Hub has:
+
+1. a transactional old→derived projection migration covering every referencing
+   table;
+2. durable alias/provenance for old ids used by saved links and events;
+3. per-repository prepare/apply/rollback behavior coordinated with the Git
+   commit and push seal; and
+4. an isolated PostgreSQL rehearsal proving forward and reverse mappings.
+
+This is a discovered compatibility requirement, not a source-data blocker. The
+sealed plan remains evidence; any source or HEAD drift requires regeneration.