docs(CORE-WP-0007): retire inter-hub-haskell in inventory and cutover record

docs/core-hub-cutover-decision-coupling.md

@@ -15,7 +15,7 @@ sign-off retires it.
 | Question | Decision |
 | --- | --- |
 | Is legacy Inter-Hub still required for normal operation? | **No** — production ingress at `hub.coulomb.social` serves Core Hub since 2026-07-03. |
-| Is Inter-Hub fallback still required? | **Yes, rollback-only** until stabilization closes and `CORE-WP-0007-T02` is approved. |
+| Is Inter-Hub fallback still required? | **No** — `CORE-WP-0007` closed 2026-07-08; rollback deployments scaled to 0. |
 | Are the three cutover gates satisfied? | **Yes** — deployed API smoke, staging import, and activity-core sink evidence all pass. |
 | Can Phase 4 fin-hub work begin? | **Yes** — multi-hub pattern is proven at Level 2→3 boundary; fin models remain separate implementation. |
 
@@ -70,17 +70,14 @@ Consumers migrating from Inter-Hub `/api/v2` must account for:
 
 ## Rollback and Haskell Retirement Gates
 
-Rollback remains one ingress flip:
+Haskell retirement completed 2026-07-08 (`CORE-WP-0007`):
 
-1. Delete Core Hub ingress (`30-ingress.yaml`)
-2. Apply `rollback-inter-hub-ingress.yaml`
-3. Inter-Hub deployment stays running untouched through stabilization
+- Forgejo repo renamed to `coulomb/inter-hub-haskell` on railiance01 and CoulombCore
+- Rollback deployments scaled to `0` on both clusters; stale railiance01 ingress removed
+- haskelseed build lane parked; CI workflows are `workflow_dispatch` only
 
-`CORE-WP-0007` Haskell retirement requires:
-
-- stabilization window close (through 2026-07-10T17:35Z per workplan)
-- operator approval after repeated public probe pass
-- explicit decision that rollback is no longer operationally required
+Emergency rollback would require scaling Inter-Hub back up and re-applying
+`rollback-inter-hub-ingress.yaml` — not operationally maintained.
 
 ## Supersede Decisions