feat: advance conformance and deterministic ID migration

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

workplans/RMGR-WP-0004-repository-standards-conformance.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Repository standards conformance and governed scaffolding"
 domain: infotech
 repo: repo-manager
-status: active
+status: finished
 owner: codex
 topic_slug: infotech
 created: "2026-08-16"
@@ -86,7 +86,7 @@ anti-patterns (`INTENT.md`+`GOAL.md`, `PRJ-WP-`). Index:
 
 ```task
 id: RMGR-WP-0004-T02
-status: progress
+status: done
 priority: high
 state_hub_task_id: "2c9b0cb1-f0f0-40f7-83ef-1828298338d3"
 ```
@@ -106,11 +106,14 @@ Known first findings, both live today:
 - every `prj-` repo would collide on workplan prefix `PRJ-WP-`, because the
   prefix is derived from the flavor marker rather than from the project.
 
-**Progress (2026-08-21):** `rmgr conform` reports `missing` vs
-`contradictory` and flags both known findings. Remaining: call from the
-consistency lane / STATE-WP-0080 guard. The earlier C-15 gate is gone:
+**Result (2026-08-21):** `rmgr conform` reports `missing` vs
+`contradictory` and flags both known findings. The earlier C-15 gate is gone:
 `RMGR-WP-0005-T06` is complete, so this task is no longer `todo` in substance.
 
+The compatibility call is now live as State Hub consistency check C-35
+(`state-hub` commit `b9d9ffe`). It executes the Repo Manager command and
+projects its findings without copying flavor rules into the retiring hub.
+
 ## Own governed scaffolding
 
 ```task
@@ -151,7 +154,7 @@ Durable flavors get `INTENT.md` and an optional foundation workplan.
 
 ```task
 id: RMGR-WP-0004-T04
-status: wait
+status: done
 priority: medium
 state_hub_task_id: "8cd3ba11-b16b-4910-8bf6-651a24d47b8c"
 ```
@@ -166,6 +169,13 @@ running it on a `prj-` repo produces the standard's session order —
 This matters beyond first registration: regeneration runs fleet-wide, so a
 flavor-blind template silently re-breaks conformant repos.
 
+Result (2026-08-21): current generator and fleet output were re-audited rather
+than changed from the stale task premise. Templates are brief-first and contain
+no `INTENT.md` assumption; the four `prj-` repositories have zero incorrect
+purpose-document references. The two literal `INTENT.md` mentions explicitly
+say project repositories use `GOAL.md`, which is the desired safeguard.
+Repo Manager conformance is now the regeneration guard via C-35.
+
 ## Accept the handoff from state-hub
 
 ```task
@@ -293,7 +303,7 @@ ADR-007 § Migration.
 
 ```task
 id: RMGR-WP-0004-T09
-status: progress
+status: done
 priority: high
 state_hub_task_id: "3a6ba954-4e35-4b2d-8dff-d3db84ed832c"
 ```
@@ -459,6 +469,14 @@ to the next free `KONT-WP-` number.
 every clash is against an archived file. Assign them before either repo
 allocates its next number, or they become live collisions.
 
+Result (2026-08-21): all 11 records named by the live-collision section are now
+terminal (`finished` or legacy `completed`). `rmgr identifier preflight --root
+/home/worsch` sees 263 live identifiers across 113 repositories with zero
+collisions, so T03's gate is cleared without rewriting frozen history. Dormant
+future ownership for `WHYNOT-WP`, `OPS-WP`, and `REPO-WP` is handed off as live
+residual `RMGR-IN-0002`; it must be resolved before the next allocation under
+any of those prefixes.
+
 ## Confirm the canon boundary
 
 ```task
@@ -482,3 +500,10 @@ Result (2026-08-21): the seam is explicit in
 standards and Repo Manager implements conformance and governed mutation. The
 canon ADR for this workplan links the enforcement placement; no competing
 semantic standard was introduced here.
+
+## Closure
+
+Finished 2026-08-21. Standards modeling, conformance, governed scaffolding,
+compatibility coverage, identifier uniqueness, prefix ownership, and the canon
+boundary are live. Dormant prefix ownership is preserved as registered residual
+`RMGR-IN-0002` rather than keeping this implementation workplan open.