close rename plan and restate retirement gates

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c

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: active
+status: finished
 owner: codex
 topic_slug: infotech
 created: "2026-08-28"
@@ -15,6 +15,14 @@ reviewed_against_commit: "41d80429a77ffeb640f4b34091ebee5c91585373"
 quality_dor: DoR-Ok
 quality_dor_at: "2026-08-28"
 quality_dor_by: codex
+quality_dod: DoD-Ok
+quality_dod_at: "2026-08-31"
+quality_dod_by: codex
+quality_dod_note: >-
+  The generic capability, recovery contract, operator documentation, and
+  target-workplan generator are tested and deployed. FLEX-WP-0020 is committed,
+  pushed, registered, DoR-Ok, and retains the signing and human approval gates
+  for the deliberately out-of-scope live rename.
 related:
   - CUST-ADR-012
   - STATE-WP-0083
@@ -565,7 +573,7 @@ one existing async cancellation warning remain outside T08.
 
 ```task
 id: STATE-WP-0085-T09
-status: wait
+status: done
 priority: high
 state_hub_task_id: "df34f6ec-d137-52d0-93c4-3756a821097f"
 ```
@@ -605,8 +613,8 @@ committed, and registered proposed plan `FLEX-WP-0020` / State Hub UUID
 `99a661a8-b36c-5c1c-b78b-1e8930bcd0a9` (`flex-auth` commits `8d61ac9` and
 `8ea8644`). The plan is deliberately repository-only, names every reviewed
 verification owner, retains runtime/product `flex-auth` surfaces, and preserves
-the human cutover gate. T09 remains in progress because live preflight correctly
-reports `preflight_signing_unavailable`; provisioning was handed to
+the human cutover gate. At that point T09 was held because live preflight
+correctly reported `preflight_signing_unavailable`; provisioning was handed to
 `railiance-platform` in message `cd52ba10-de41-46ce-aa8b-9b44050da8f7`. No
 Forgejo rename, State Hub rebind, clone removal, consumer edit, or runtime
 deployment was performed.
@@ -615,8 +623,22 @@ deployment was performed.
 registered, `proposed`, and DoR-Ok. The deployed State Hub still has no
 repository-rename preflight signing configuration, and platform handoff
 `cd52ba10-de41-46ce-aa8b-9b44050da8f7` remains unread. This is an external
-provisioning gate, so the task is `wait`, not active implementation. No rename
-or consumer mutation was performed.
+provisioning gate for the later live cutover, so the task was held at `wait`
+while its completion boundary was checked. No rename or consumer mutation was
+performed.
+
+**Completed 2026-08-31.** T09 ends at the reviewed repository-owned adoption
+plan, not at an executable live-rename token. `FLEX-WP-0020` is clean and
+pushed at `8ea8644`, registered as State Hub workplan
+`99a661a8-b36c-5c1c-b78b-1e8930bcd0a9`, and records DoR-Ok plus the explicit
+human cutover gate. Its captured preflight proves the existing State Hub UUID,
+Forge repository ID `42`, and matching local/origin/Forge source commit. The
+missing signing configuration remains a fail-closed prerequisite of
+`FLEX-WP-0020-T05` and the platform handoff above; it is not a prerequisite for
+generating or reviewing the plan. Moving it into this workplan's completion
+gate would incorrectly make an out-of-scope live-rename prerequisite part of
+the generator delivery. No State Hub, Forgejo, checkout, deployment, or
+consumer mutation was performed during closeout.
 
 ## Workplan completion