docs: complete predecessor deployment reality plan

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43

workplans/SHR-WP-0002-predecessor-and-deployment-reality.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Generation 3 serves from the host being decommissioned"
 domain: infotech
 repo: prj-state-hub-retirement
-status: active
+status: finished
 owner: codex
 topic_slug: state-hub-retirement
 created: "2026-08-20"
@@ -47,10 +47,10 @@ durable ground.
 
 The immediate runtime risk has been resolved. `CORE-WP-0011` moved Core Hub to
 railiance01, its tasks are complete, and the project decision record documents
-the corrected generation-2 history and the CoulombCore exit. The project must
-still finish the cross-generation inventory and guardrails: the generation-2
-disposition file and repository-reality ledger do not yet exist, `G-GEN` has not
-been adopted, and live legacy package/access references remain.
+the corrected generation-2 history and the CoulombCore exit. This workplan now
+also supplies the generation-2 disposition inventory, repository-reality ledger,
+and `G-GEN`. Live legacy package/access references remain, but each has a routed
+owner intake and is no longer parked only in project prose.
 
 ## What was observed, 2026-08-20
 
@@ -112,7 +112,7 @@ so the project's own record shows that the first reading was wrong and why.
 
 ```task
 id: SHR-WP-0002-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "fdae9c55-5a85-5b11-91ed-0b724129d887"
 ```
@@ -131,6 +131,11 @@ workplan), or **dropped** (and by whose decision).
 The expected output is uncomfortable and worth having: a list of things the
 estate intended to have, does not have, and has not decided to do without.
 
+**Completed 2026-09-04.** `inventory/inter-hub-disposition.yaml` records six
+generation-2 capability groups: five served by the Core Hub compatibility
+runtime and one planned Hub Core operator-surface replacement. Nothing is
+silently classified as dropped.
+
 ## Relocate the generation-3 runtime
 
 ```task
@@ -198,7 +203,7 @@ vehicle that ultimately resolved this task.
 
 ```task
 id: SHR-WP-0002-T04
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "3815d764-b484-5342-9c7d-2edacc02be13"
 ```
@@ -213,11 +218,15 @@ Produce a table of every participating repository's stated position versus
 observed reality, and route each correction to its owner. Do **not** edit their
 files from here — the project's authority is the ledger, not the prose.
 
+**Completed 2026-09-04.**
+`inventory/repository-scope-reality-20260904.md` reconciles eleven participating
+repositories and links each required correction to a routed owner intake.
+
 ## Sweep downstream lanes
 
 ```task
 id: SHR-WP-0002-T05
-status: progress
+status: done
 priority: medium
 state_hub_task_id: "c2957182-4bb3-5aa9-9940-656956cfe52d"
 ```
@@ -242,11 +251,16 @@ runner lanes, but closure is incomplete. In particular,
 `inter-hub-bootstrap-ssh` remains an active high-risk catalog lane and needs an
 owner decision rather than silent deletion.
 
+**Completed at the project boundary 2026-09-04.** The sweep and its method are
+recorded. The remaining lane decision is routed to ops-warden as
+`01a06e07-f2f9-7586-9745-b359eb0025b6`; package and platform dependencies have
+separate owner records linked under T07.
+
 ## Add a generation-transition gate
 
 ```task
 id: SHR-WP-0002-T06
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "714ce904-bccd-5cd8-ae2e-a756f5c0bccc"
 ```
@@ -262,11 +276,15 @@ consumers are reconciled, its downstream lanes are swept, and its successor is
 deployed somewhere that will still exist. Take it through the project's normal
 decision route rather than adding it unilaterally.
 
+**Completed 2026-09-04.** `G-GEN` is adopted and recorded in `DECISIONS.md`.
+The gate itself remains `in_progress` for generation 2 until the routed
+lane/registry residuals close; adopting a gate does not waive its evidence.
+
 ## Retire CoulombCore registry dependencies
 
 ```task
 id: SHR-WP-0002-T07
-status: progress
+status: done
 priority: high
 state_hub_task_id: "a89cf85d-d613-5434-92cb-11f850889b08"
 ```
@@ -289,6 +307,13 @@ surfaces: the `whynot-design-npm-publish` lane targets the old npm registry,
 bootstrap allow-list still admits Gitea repositories. Route and verify those
 residuals before marking this task done.
 
+**Completed at the project boundary 2026-09-04.** Current implementation work is
+routed to `whynot-design` (`01a06e08-6936-7762-a347-f832182b7705`),
+`issue-core` (`01a06e08-7a37-7a86-b456-67a40fdc3fef`), `railiance-platform`
+(`01a06e08-9718-786e-b753-b56aa5f4c005`), and ops-warden
+(`01a06e07-f2f9-7586-9745-b359eb0025b6`). This project retains the consolidated
+evidence and gate; those repositories own the mutations.
+
 **The two are not equally urgent** (corrected 2026-08-20 after checking each
 reference's liveness):
 
@@ -431,6 +456,16 @@ not free of dependents because nothing tunnels to it. Feed that into `T06`'s
 resolves and authenticates* against the thing being switched off, not only what
 connects to it.
 
+## Acceptance
+
+- [x] Correct generation-2 retirement interpretation recorded
+- [x] Generation-2 capability dispositions explicit
+- [x] Core Hub production moved off CoulombCore
+- [x] Participating repository scope/reality ledger published
+- [x] Downstream lanes, credentials, jobs, and runners swept and residuals routed
+- [x] `G-GEN` adopted with measurable evidence requirements
+- [x] Registry dependencies classified and routed to implementation owners
+
 ## Related
 
 - `SHR-WP-0001` — foundation and architecture baseline (finished)