chore(CORE-WP-0007): retire inter-hub-haskell reference implementation

Rename awareness in README, disable push-triggered CI, and point registry
paths at coulomb/inter-hub-haskell after Core Hub cutover.

README.md

@@ -1,52 +1,35 @@
-# inter-hub
+# inter-hub-haskell (retired)
 
-Specification and reference implementation of the **Interaction Hub
-Framework (IHF)** — a governed, observable interaction substrate for
-hub-based AI-enabled software systems.
+**Status:** renamed and retired 2026-07-08 (`CORE-WP-0007`). Forgejo repo:
+`coulomb/inter-hub-haskell`. Production ingress at `hub.coulomb.social` serves
+[Core Hub](https://gitea.coulomb.social/coulomb/core-hub) since 2026-07-03.
 
-IHF treats every meaningful UI element as a **governed interaction
-artifact** rather than mere markup. It connects the full traceability
-chain from rendered widget → user interaction → structured feedback →
-requirement candidate → decision record → implementation change →
-observed outcome, so UI evolution is evidence-based rather than
-opinion-based.
+Historical specification and reference implementation of the **Interaction Hub
+Framework (IHF)** — the second-generation Haskell/IHP interaction substrate
+superseded by Core Hub.
 
-## Status
+## Preserved knowledge
 
-Phases 0–9 of the implementation are complete (see `SCOPE.md` for the full
-per-phase breakdown): specification, widget registry and event capture,
-structured feedback and triage, governance and decision linkage, outcome
-signals and regression detection, agent-assisted proposals, cross-framework
-adapter contracts, friction/health observability, federated governance and
-ownership, and a versioned external API (`/api/v2`) with OpenAPI, OAuth
-client credentials, generated SDKs, and webhooks.
+Read these before touching any remaining Haskell/IHP build path:
 
-The core artifact model and schema are stable. This is a working reference
-implementation, not just a spec — see `Web/Controller/` for the full set of
-implemented controllers (governance, requirements, hub capability
-manifests, federated policy overlays, deployment records, and more) and
-`Test/` for the test suite.
+- `specs/InteractionHubFrameworkSpecification_v0.2.md` — full IHF contract
+- `ARCHITECTURE-LAYERS.md`, `specs/OperationalArchitecture_v0.1.md`
+- `SCOPE.md` — phase breakdown and boundaries
+- `deploy/railiance/RUNBOOK.md` — last production deployment notes
 
-## Stack
+## Replacement
 
-Built on IHP (the Integrated Haskell Platform) v1.5 + PostgreSQL.
+- **Production API:** [Core Hub](https://gitea.coulomb.social/coulomb/core-hub)
+- **Ops extension pattern:** `ops-hub` (evidence now posts to Core Hub)
+- **Migration bundle source name:** `inter-hub-haskell` in Core Hub fixtures
+
+Rollback k8s deployments are scaled to `0` on CoulombCore and railiance01.
+CI workflows are `workflow_dispatch` only; do not schedule new haskelseed builds.
+
+## Stack (historical)
+
+Built on IHP v1.5 + PostgreSQL + Nix/devenv. Local dev (if ever needed):
 
 ```bash
 devenv up
-```
-
-## Getting oriented
-
-- **Full spec:** `specs/InteractionHubFrameworkSpecification_v0.1.md` (and
-  `_v0.2.md`) — 19 sections covering key concepts, core modules, and the
-  phased implementation plan
-- **Scope and boundaries:** `SCOPE.md`
-- **Architecture:** `ARCHITECTURE-LAYERS.md`, `specs/OperationalArchitecture_v0.1.md`
-- **Build history:** `workplans/`
-
-## Relevant when
-
-Building or reviewing any hub dashboard or operator surface (dev-hub,
-ops-hub, fin-hub), capturing and triaging feedback on existing hub UIs, or
-defining governed widget identity for a new capability surface. See
-`SCOPE.md` for the full relevant/not-relevant breakdown and related repos.
+```