docs: define hub-core absorption plan

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

@@ -40,13 +40,24 @@ CoulombCore.
 
 ## Readiness and blocker review — 2026-08-21
 
-`CORE-WP-0011` is finished: production now runs on railiance01 and the active
-CoulombCore runtimes are stopped. The runtime surface inventory is complete in
-`docs/specs/runtime-absorption-inventory.md`. The remaining work is blocked,
-not merely unstarted: `HUB-WP-0004` is still proposed and its runtime packaging
-(`T03`), minimal ports (`T04`), and joint absorption plan (`T06`) determine the
-shape of every subsequent task here. This workplan can return to `active` when
-those decisions are owned and ready for joint execution.
+At the start of the review, `CORE-WP-0011` was finished and the runtime surface
+inventory was complete, but `HUB-WP-0004` was still proposed. Its runtime
+packaging (`T03`), minimal ports (`T04`), and joint absorption plan (`T06`) were
+therefore recorded as the blockers. The advancement below supersedes that
+dependency snapshot.
+
+## Dependency advancement — 2026-08-21
+
+Hub-core has completed `HUB-WP-0004-T01`–`T05` in its file-backed workplan and
+State Hub: the primary-image decision, Tier 1 contracts, minimal port runtime,
+and initial conformance harness now exist. The paired design is recorded in
+`docs/specs/runtime-absorption-plan.md`, completing this workplan's T02 input
+and the Core Hub half of `HUB-WP-0004-T06`.
+
+Execution remains blocked on publishing the completed hub-core work at an
+immutable source/image revision and replacing its deliberately ephemeral
+in-memory backend with a production PostgreSQL boundary. Those are explicit
+Slice 0 entry gates, not reasons to reopen the architecture decision.
 
 ## Inventory runtime surfaces to absorb
 
@@ -69,7 +80,7 @@ and move constraints.
 
 ```task
 id: CORE-WP-0010-T02
-status: wait
+status: done
 priority: high
 state_hub_task_id: "d2679b41-01e9-477c-9d8a-0b1ddc8847cf"
 ```
@@ -78,7 +89,10 @@ Define how hub-core serves equivalent `/api/v2` (or compatible gateway) while
 core-hub remains rollback. Include feature flags, traffic shift, and smoke
 ownership.
 
-Waiting on `HUB-WP-0004-T03` and `HUB-WP-0004-T06`.
+Completed 2026-08-21. `docs/specs/runtime-absorption-plan.md` defines the
+route-group order, one-writer rule, data/delta checks, compatibility adapters,
+consumer gates, traffic controls, rollback, evidence, and ownership. Hub-core
+must link the joint plan to close `HUB-WP-0004-T06`.
 
 ## Execute absorption slices
 
@@ -92,7 +106,9 @@ 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.
 
-Waiting on the approved dual-run design and `HUB-WP-0004-T04`.
+Waiting on a committed/published hub-core runtime revision, immutable image,
+durable PostgreSQL backend, and candidate deployment. Start with Slice 0; do
+not change public traffic.
 
 ## Cutover production traffic
 
@@ -125,7 +141,7 @@ Waiting on production cutover and recorded residual ownership.
 ## Acceptance
 
 - [x] Absorption inventory complete
-- [ ] Dual-run design approved/recorded
+- [x] Dual-run design approved/recorded
 - [ ] Consumer smokes pass on hub-core host
 - [ ] Production traffic cut over with evidence
 - [ ] core-hub archived read-only; residuals owned elsewhere