feat(ecosystem): adopt hub-core dependency and CI pin gate (CORE-WP-0009)

Import slugify_or_default from hub-core, add contract tests, vendor hub-core in
Docker/Forgejo CI, document metadata isolation and pagination deferral, and
align INTENT/SCOPE with three-repo stack.

INTENT.md

@@ -36,6 +36,20 @@ The framework must be usable by humans and agents. Human operators need a stable
 - UI: whynot-design aligned tokens and Lit/custom-element adapters where UI components are needed; avoid locking the framework to React.
 - Deployment: Docker/Kubernetes/ArgoCD/Gitea or Forgejo workflows on the normal platform path; no GHC/IHP/Nix build dependency for the new framework.
 
+## Ecosystem position
+
+`core-hub` is the **production framework layer** in the three-repo hub stack:
+
+| Repo | Role |
+| --- | --- |
+| `hub-core` | Shared library — models, router factories, utils (`hub_core.utils`) |
+| `state-hub` | Dev coordination — file-first workplans, dev MCP |
+| `core-hub` | Production service — `/api/v2`, hubs, manifests, operator console |
+
+Canon: `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`
+
+**Naming:** `core-hub` = core *framework runtime*. `hub-core` = core *primitives library*.
+
 ## Current State
 
-This repo has been re-bound from the `repo-seed` template into the Core Hub planning and specification home. The first implementation work is organized around contract extraction, FastAPI/Postgres foundation, Inter-Hub compatibility, data migration, operator UI, and retirement of the Haskell build lane after cutover.
+Production serves Core Hub at `hub.coulomb.social` since 2026-07-03. Haskell Inter-Hub is retired (`CORE-WP-0007`). Ecosystem consolidation with hub-core and state-hub is tracked under `CUST-WP-0057` / `CORE-WP-0009`.