docs: close core-hub absorption execution

workplans/HUB-WP-0005-core-hub-absorption-execution.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Core Hub absorption execution"
 domain: infotech
 repo: hub-core
-status: active
+status: finished
 owner: codex
 topic_slug: custodian
 created: "2026-08-21"
@@ -89,7 +89,7 @@ surface without reads from the legacy schema.
 
 ```task
 id: HUB-WP-0005-T06
-status: wait
+status: done
 priority: high
 ```
 
@@ -98,11 +98,20 @@ the operator-approved production writer cutover, exercise rollback, and hand
 the seven-day stabilization/archive residual to CORE-WP-0010. Wait until
 RAPPCOREHUB-WP-0002 provides the private candidate and route controls.
 
+Completed 2026-08-21. Production runs immutable image
+`sha256:adf580d09a4a9139b1663c41d59d46903a007e03a3ae567e09b8a6ec23708ab8`.
+All five route groups and all four writer groups are hub-core-owned; Core Hub
+is live with no writer groups as rollback. The seven-table import and reverse
+export have exact counts, identity sets, and content hashes. Conformance is
+8/8, ops-hub and activity-core gates pass, and Helm rollback to the pre-cutover
+revision plus forward recovery was exercised. The seven-day window ends no
+earlier than 2026-08-28T20:49:50+02:00 under CORE-WP-0010.
+
 ## Acceptance
 
 - [x] Production readiness requires durable PostgreSQL and auth dependencies
 - [x] Import is idempotent; counts, identities, hashes, and provenance compare
 - [x] All 22 checked-in Core Hub OpenAPI paths have governed dispositions
-- [ ] ops-hub and activity-core gates pass on hub-core
-- [ ] Production runs the immutable hub-core image with one writer per group
-- [ ] Rollback is exercised and stabilization residual is recorded
+- [x] ops-hub and activity-core gates pass on hub-core
+- [x] Production runs the immutable hub-core image with one writer per group
+- [x] Rollback is exercised and stabilization residual is recorded