diff --git a/workplans/CORE-WP-0010-runtime-absorption-and-archive.md b/workplans/CORE-WP-0010-runtime-absorption-and-archive.md index e9cc7b6..57ae681 100644 --- a/workplans/CORE-WP-0010-runtime-absorption-and-archive.md +++ b/workplans/CORE-WP-0010-runtime-absorption-and-archive.md @@ -4,7 +4,7 @@ type: workplan title: "Runtime absorption into hub-core and archive" domain: infotech repo: core-hub -status: active +status: blocked flavor: implementation owner: codex topic_slug: infotech @@ -144,7 +144,7 @@ Evidence is recorded in ```task id: CORE-WP-0010-T05 -status: progress +status: wait priority: medium state_hub_task_id: "6e67fd41-3f52-5085-85b6-1661c322e290" ``` @@ -166,6 +166,23 @@ non-destructive retention boundaries, and defines the ordered final checklist. Only elapsed stabilization, final observations, operator approval, rollback scale-down, and the read-only Forgejo action remain. +## Loose-end review — 2026-09-27 + +`make test` passes (26/26) and the State Hub API is reachable from this +workstation (`/state/health` ok). `make stabilization-check` cannot complete +from this session: it fails at the first gate reaching the public production +host `https://hub.coulomb.social` (`/healthz`) with a self-signed-certificate +error, so the daily gate cannot be evaluated here. The remaining closeout +items in `docs/deployment/archive-closeout.md` (scaling the Core Hub rollback +workload to zero via `rapp-core-hub`, routing the Forgejo admin credential +through `warden route` to set `coulomb/core-hub` read-only, and recording +operator approval) require production/Forgejo access and an explicit operator +decision that this repo session does not have and should not take +unilaterally. No unhandled Core Hub-retirement inbox message was found +blocking this task specifically. Moved this workplan and `T05` to +`blocked`/`wait` pending operator action on the closeout checklist; no other +loose ends were found in this repo's other workplans (all are `finished`). + ## Acceptance - [x] Absorption inventory complete