docs: record hub-core production cutover

workplans/CORE-WP-0010-runtime-absorption-and-archive.md

@@ -102,7 +102,7 @@ aligned with hub-core's accepted canonical plan; `HUB-WP-0004-T06` is done.
 
 ```task
 id: CORE-WP-0010-T03
-status: progress
+status: done
 priority: high
 state_hub_task_id: "c01ddec1-5737-4115-ac73-c402ffb5bdc5"
 ```
@@ -110,25 +110,20 @@ state_hub_task_id: "c01ddec1-5737-4115-ac73-c402ffb5bdc5"
 Migrate in slices with consumer smokes (ops-hub, activity-core) after each.
 Record row counts and fixture replays per slice.
 
-Started 2026-08-21 after hub-core revision `7e1ec03` closed the joint planning
-and publication gate. S0 now owns the durable PostgreSQL backend, legacy
-auth/health compatibility, immutable image, and internal candidate deployment.
-Do not change public traffic.
-
-Implementation advancement 2026-08-21: hub-core revision `8ab1d0c` adds the
-durable PostgreSQL store, audit ledger, all `/api/v2` compatibility groups,
-fail-closed writer controls, seven-table idempotent import/export, and reverse
-bundle support. Its Forgejo image is pinned at
-`sha256:2a8b396c5295476d5ce865927b8309a6e054e50eac4e92175ef32cdeaba962fb`.
-This source now exports all seven tables without raw keys and fences writes by
-route group. The remaining T03 work is live candidate migration, comparison,
-and named consumer evidence.
+Completed 2026-08-21. Hub-core revision `055cf49` and immutable image
+`sha256:adf580d09a4a9139b1663c41d59d46903a007e03a3ae567e09b8a6ec23708ab8`
+provide the durable PostgreSQL store, audit ledger, complete compatibility
+surface, fail-closed writer controls, and lossless migration tooling. The live
+seven-table import was repeatable and preserved exact counts, identity sets,
+and canonical content hashes; restart persistence and reverse export also
+matched. Hub-core conformance passed 8/8, and the public ops-hub and
+activity-core consumer gates passed before and after rollback recovery.
 
 ## Cutover production traffic
 
 ```task
 id: CORE-WP-0010-T04
-status: wait
+status: done
 priority: high
 state_hub_task_id: "dc414053-a896-4bf0-af05-944b7a7cf750"
 ```
@@ -136,7 +131,13 @@ state_hub_task_id: "dc414053-a896-4bf0-af05-944b7a7cf750"
 With operator approval, point production at hub-core runtime; verify consumer
 smokes and interaction evidence path.
 
-Waiting on completed absorption evidence and explicit operator approval.
+Completed 2026-08-21 with operator approval. All five route groups and all
+four mutable writer groups now belong to hub-core; Core Hub remains Ready with
+an empty writer set as rollback. Helm rollback to the pre-cutover runtime was
+exercised at revision 19, followed by successful forward recovery to revision
+20 and repeat conformance, consumer, image, readiness, and writer-fence gates.
+Evidence is recorded in
+`docs/evidence/core-hub-hub-core-cutover-2026-08-21.md`.
 
 ## Archive repository
 
@@ -150,12 +151,16 @@ state_hub_task_id: "16525001-f85e-4dae-9dc4-d36cb1eb4fbe"
 Write completion record (revisions, PRs, residual owners), set read-only archive
 on forge, and hand residual work as live records outside this repo.
 
-Waiting on production cutover and recorded residual ownership.
+Production cutover is complete. Wait through the stabilization interval that
+started at 2026-08-21T20:49:50+02:00 and ends no earlier than
+2026-08-28T20:49:50+02:00. Then record the final review, archive this
+repository read-only on Forgejo, and hand any remaining product-intent gaps to
+live records outside this repository.
 
 ## Acceptance
 
 - [x] Absorption inventory complete
 - [x] Dual-run design approved/recorded
-- [ ] Consumer smokes pass on hub-core host
-- [ ] Production traffic cut over with evidence
+- [x] Consumer smokes pass on hub-core host
+- [x] Production traffic cut over with evidence
 - [ ] core-hub archived read-only; residuals owned elsewhere