docs: record hub-core production cutover

STATE.md

@@ -5,26 +5,28 @@
 
 ## One-line posture
 
-**Core Hub remains the verified production `/api/v2` authority on railiance01.
-Hub-core S0–S5 implementation is published at `8ab1d0c` with immutable image
-digest `sha256:2a8b396c5295476d5ce865927b8309a6e054e50eac4e92175ef32cdeaba962fb`;
-the next gate is the private production candidate and data import.**
+**Hub-core is the verified production `/api/v2` authority on railiance01.
+Core Hub remains deployed and healthy with no writer groups as the tested
+rollback until the stabilization window closes on 2026-08-28.**
 
 ## Production truth
 
 | Surface | Current state |
 | --- | --- |
 | Public endpoint | `https://hub.coulomb.social` → `92.205.62.239` |
-| Runtime | railiance01, Helm revision 4, chart `0.3.2` |
+| Runtime | railiance01, Helm revision 20, chart `0.4.0` |
 | Package | `rapp-core-hub`, verified and bound to `reef-railiance` |
-| Image | Forgejo digest `sha256:0db6f7c646c6d4c1fbc844dc266fcf883584637e1c1f47802efe1c6a98558d3c` |
-| Database | railiance01 `platform-pg`, database `core_hub`, schema `core_hub` |
+| Authoritative image | hub-core `055cf49`, digest `sha256:adf580d09a4a9139b1663c41d59d46903a007e03a3ae567e09b8a6ec23708ab8` |
+| Rollback image | Core Hub digest `sha256:388a94ec752e13a0031e329a45e970480c41691e969d4e40c31924669e8d0005` |
+| Database | railiance01 `platform-pg`, database `core_hub`, schemas `core_hub` and `hub_runtime` |
 | TLS | Let's Encrypt certificate Ready through 2026-11-18 |
 | Consumers | ops-hub gate and activity-core resolver/evidence sink verified |
-| Source fallback | CoulombCore production and staging Deployments at zero replicas; source DB read-only |
+| Live rollback | Core Hub Deployment Ready, public routes removed, writer set empty |
 
 The relocation and retirement evidence is in
 [`docs/evidence/core-hub-railiance01-stabilization-2026-08-21.md`](docs/evidence/core-hub-railiance01-stabilization-2026-08-21.md).
+The hub-core migration and cutover evidence is in
+[`docs/evidence/core-hub-hub-core-cutover-2026-08-21.md`](docs/evidence/core-hub-hub-core-cutover-2026-08-21.md).
 Deployment packaging and rollout truth lives in the `rapp-core-hub` repository.
 
 ## Workplans
@@ -33,7 +35,7 @@ Deployment packaging and rollout truth lives in the `rapp-core-hub` repository.
 | --- | --- | --- |
 | `CORE-WP-0001`–`CORE-WP-0009` | finished / archived | Gen3 runtime, contracts, persistence, consumer gates, and hardening delivered |
 | `CORE-WP-0011` | finished | Production relocated to railiance01 and active CoulombCore runtime retired |
-| `CORE-WP-0010` | active | S0–S5 code done; private candidate/data gates next |
+| `CORE-WP-0010` | active | Production cutover done; stabilization/archive gate remains |
 
 ### Open work
 
@@ -41,19 +43,21 @@ Deployment packaging and rollout truth lives in the `rapp-core-hub` repository.
 | --- | --- | --- |
 | `CORE-WP-0010-T01` inventory | done | Inventory recorded in `docs/specs/runtime-absorption-inventory.md` |
 | `CORE-WP-0010-T02` dual-run design | done | Route-group plan recorded in `docs/specs/runtime-absorption-plan.md` |
-| `CORE-WP-0010-T03` absorption slices | progress | Deploy private candidate, import/compare data, run consumers |
-| `CORE-WP-0010-T04` production cutover | wait | Absorption evidence and operator approval |
-| `CORE-WP-0010-T05` archive | wait | Cutover complete and residual ownership recorded |
+| `CORE-WP-0010-T03` absorption slices | done | Seven-table parity, conformance, restart, and consumer gates passed |
+| `CORE-WP-0010-T04` production cutover | done | Hub-core authoritative; rollback and forward recovery exercised |
+| `CORE-WP-0010-T05` archive | wait | Seven-day stabilization through 2026-08-28T20:49:50+02:00 |
 
 ## Intent position
 
-The operational reset promised by `INTENT.md` is real: the service is small,
-containerized, contract-tested, credential-safe, observable, and deployed on
-ordinary Kubernetes/PostgreSQL infrastructure. The larger Gen3 product intent
-is only partly realized. Core Hub does not yet own the fleet's messaging,
-progress/work projections, durable decision/deployment/outcome resources, or a
-single extension runtime. Those gaps are not a reason to disturb the healthy
-production runtime; they are inputs to the hub-core consolidation decision.
+The operational and consolidation goals in `INTENT.md` are now materially
+realized: hub-core is the single production runtime, remains contract-tested
+and credential-safe, and runs on ordinary Kubernetes/PostgreSQL infrastructure
+with a reversible migration. The larger Gen3 product intent is still partial.
+Fleet development coordination remains in state-hub, and durable
+decision/deployment/outcome resources plus some progress/work projections are
+not yet unified behind hub-core. Those residual capabilities need explicit
+owners after this repository is archived; they are not reasons to reverse the
+healthy production cutover.
 
 ## Verify
 
@@ -69,12 +73,11 @@ curl -fsS https://hub.coulomb.social/readyz
 - `CORE-WP-0011` is finished but has no State Hub UUID; the registrar warning is
   retained rather than inventing an identifier.
 - `.custodian-brief.md` is generated and may lag file-backed workplan truth.
-- Hub-core runtime/compatibility/migration implementation is published at
-  `8ab1d0c`; its candidate image digest is recorded above. Public authority
-  stays here until the private data, conformance, consumer, and rollback gates
-  pass.
+- Hub-core production authority is published at `055cf49`; exact migration,
+  conformance, consumer, writer-fence, and rollback gates passed.
 - `make lint` has baseline style findings in unchanged Python files; the full
   suite passes all 26 tests after adding migration export and write fencing.
 - The stopped CoulombCore workloads and read-only source database are retained
   only as controlled fallback evidence.
-- Do not archive this repository before `CORE-WP-0010` completes.
+- Do not archive this repository before the 2026-08-28 stabilization review
+  completes `CORE-WP-0010-T05`.