feat(consistency): rebuild deterministic projection IDs

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

workplans/STATE-WP-0079-retirement-strangler.md

@@ -196,6 +196,25 @@ The remaining gate is an operator-approved pilot ordering the central database
 transaction and authoritative file rewrite/reconciliation as one recoverable
 cutover unit.
 
+**Repo Manager pilot executed (2026-08-22):** the workstation projection was
+the only instance holding `RMGR-WP-0005`; the production/registrar projection
+had no matching row. A verified 4.4 MiB preapply PostgreSQL dump was retained at
+`/tmp/state-hub-rmgr-wp-0005-pilot-preapply.dump`. The live schema advanced to
+`b8d4f0a2c6e1`, then six workplan/task primary keys migrated in one transaction.
+All 12 child-task links, 12 workplan progress links, one decision link, and
+three task progress links followed. Six aliases are `applied`; all old rows are
+absent and all new rows present. Repo Manager committed the matching file
+rewrite in `5de754a`; two consistency runs produced a fresh, non-stale index and
+the new workplan API lookup returns 200 while the old lookup returns 404.
+
+The absent registrar row exposed the final rebuild gap before remote ingestion:
+create schemas did not accept authoritative UUIDs and consistency classified a
+missing derived row as an unfixable stale reference. The projection rebuild path
+now accepts file UUIDs, derives IDs when a live file has none, and registers a
+missing derived workplan/task without rewriting the authoritative identifier.
+Focused rebuild/API tests and the full State Hub suite pass (`624 passed`).
+Deploy and ingest the pilot on the registrar before widening the migration.
+
 **A2a executed (2026-08-20) — first live cutover slice.** Dual-run is on for the
 pilot repo: