chore(consistency): renormalize lifecycle state [auto]

Updated by fix-consistency on 2026-08-28:
  - workplan status: ready → active

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a049a4-ee9f-78e1-9d66-2cb0f9bea3e3

workplans/STATE-WP-0085-repository-lineage-preserving-rename.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Lineage-preserving repository rename workflow and adoption-plan generator"
 domain: infotech
 repo: state-hub
-status: ready
+status: active
 owner: codex
 topic_slug: infotech
 created: "2026-08-28"
@@ -146,7 +146,7 @@ that leaves the operator guessing which action already happened.
 
 ```task
 id: STATE-WP-0085-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "dbac0fdf-042e-51bf-937e-59d15e34cb14"
 ```
@@ -175,6 +175,15 @@ Acceptance:
 - owner transfer and product/runtime rename are explicitly outside this
   contract rather than silently half-supported.
 
+Result (2026-08-28): accepted `STATE-ADR-001` in
+`docs/adr/ADR-001-repository-rename-identity-contract.md`. It defines immutable
+State Hub and Forge identities, protected slug aliases, compare-and-set phase
+semantics, retry and rollback limits, twelve named failure states, recovery from
+every phase, and the treatment/owner inventory for persistence, REST, CLI, MCP,
+consistency projections, dashboard queries, events, edge relay state, Forgejo,
+local clones, and external consumers. Owner transfer and product/runtime rename
+are explicit target-workplan boundaries.
+
 ## Add durable forge identity, aliases, and rename operations
 
 ```task