Close Core Hub ops evidence continuation

workplans/CORE-WP-0008-api-first-ops-evidence-continuation.md

@@ -4,7 +4,7 @@ type: workplan
 title: "API-first ops-hub evidence continuation"
 domain: infotech
 repo: core-hub
-status: active
+status: finished
 owner: codex
 topic_slug: custodian
 created: "2026-06-27"
@@ -256,7 +256,7 @@ evidence, migration/cutover, action-required gates, and access metadata.
 
 ```task
 id: CORE-WP-0008-T07
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "c8d4bb9b-d204-46ae-b727-eafe7b80236f"
 ```
@@ -273,6 +273,18 @@ Minimum scope:
   `CUST-WP-0025-T13` through `T19`;
 - keep Haskell retirement (`CORE-WP-0007`) blocked until cutover proof exists.
 
+Completed 2026-06-27: reported the replacement evidence back to Custodian in
+`the-custodian` commit `12600c5` by adding
+`docs/core-hub-replacement-evidence.md` and updating `CUST-WP-0052`,
+`CUST-WP-0047`, and `CUST-WP-0049`. The handoff records that Core Hub now has
+the repeatable API smoke harness, activity-core sink, staging profile, CLI
+wrappers, and gated UI backlog, but no live deployed Core Hub smoke ids/counts
+were available because no approved deployed endpoint/token was present.
+`CUST-WP-0047-T05` and `CUST-WP-0049-T06` therefore remain legacy/fallback
+wait tasks. The handoff gives rewrite guidance for `CUST-WP-0025-T13` through
+`T19` and keeps `CORE-WP-0007` blocked until staging import, dual-run/cutover,
+rollback evidence, and operator approval exist.
+
 ## Acceptance
 
 - Core Hub has a repeatable deployed API smoke harness for ops-hub bootstrap and