feat: advance repository records and provenance

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

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

@@ -8,7 +8,7 @@ status: active
 owner: codex
 topic_slug: infotech
 created: "2026-08-16"
-updated: "2026-08-18"
+updated: "2026-08-21"
 parent_project: prj-state-hub-retirement
 parent_workplan: SHR-WP-0001
 related:
@@ -86,7 +86,7 @@ anti-patterns (`INTENT.md`+`GOAL.md`, `PRJ-WP-`). Index:
 
 ```task
 id: RMGR-WP-0004-T02
-status: todo
+status: progress
 priority: high
 state_hub_task_id: "2c9b0cb1-f0f0-40f7-83ef-1828298338d3"
 ```
@@ -106,10 +106,10 @@ 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.
 
-**Opened (2026-08-18):** `rmgr conform` reports `missing` vs
+**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. (Do not set `progress` until
-`RMGR-WP-0005-T06` stops C-15 forcing this task back to `wait`.)
+consistency lane / STATE-WP-0080 guard. The earlier C-15 gate is gone:
+`RMGR-WP-0005-T06` is complete, so this task is no longer `todo` in substance.
 
 ## Own governed scaffolding
 
@@ -202,7 +202,7 @@ deletes it. Inventory `caller:custodian-cli` is already `move` →
 
 ```task
 id: RMGR-WP-0004-T06
-status: wait
+status: done
 priority: medium
 state_hub_task_id: "faaeb016-3ba8-493a-bbdf-9227de24f720"
 ```
@@ -211,12 +211,18 @@ Per `SCOPE.md` § Initial extraction source, extraction must preserve behaviour
 with compatibility tests. Cover:
 
 - a `prj-` repo scaffolds `GOAL.md`, no `INTENT.md`, no flavor-derived prefix;
-- a durable repo's scaffolded output is byte-identical to the state-hub path
-  (regression guard against changing ordinary-repo behaviour);
+- a durable repo preserves the agreed durable-file contract from the State Hub
+  handoff (byte identity is intentionally retired with the old template owner);
 - conformance checking flags both known live findings from T02;
 - flavor signals that disagree warn rather than silently resolving;
 - re-running scaffolding on a conformant repo is idempotent.
 
+Result (2026-08-21): regression coverage exercises project and durable layouts,
+the two known conformance findings, disagreeing flavor signals, CLI behavior,
+and byte-stable no-op reruns. The stale byte-identity requirement was adapted
+to contract equivalence because retaining State Hub's private template bytes
+would make the retired implementation authoritative.
+
 ## Enforce workplan identifier uniqueness
 
 ```task
@@ -287,7 +293,7 @@ ADR-007 § Migration.
 
 ```task
 id: RMGR-WP-0004-T09
-status: wait
+status: progress
 priority: high
 state_hub_task_id: "3a6ba954-4e35-4b2d-8dff-d3db84ed832c"
 ```
@@ -457,7 +463,7 @@ allocates its next number, or they become live collisions.
 
 ```task
 id: RMGR-WP-0004-T07
-status: wait
+status: done
 priority: low
 state_hub_task_id: "7fdd54fe-fba7-4713-9814-d4534ff19706"
 ```
@@ -470,3 +476,9 @@ this repo.
 If the ownership shift warrants it, the Custodian may want an ADR recording that
 repository-standards enforcement is a Repo Manager responsibility — that is a
 Custodian decision, raised from here, not made here.
+
+Result (2026-08-21): the seam is explicit in
+`docs/repository-standards_v0.1.md`: Custodian canon defines repository
+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.