Rewrite FOS ops hub phase for Core Hub

workplans/CUST-WP-0052-core-hub-fos-reset.md

@@ -158,7 +158,7 @@ and gated UI rebuild criteria.
 
 ```task
 id: CUST-WP-0052-T04
-status: todo
+status: done
 priority: high
 state_hub_task_id: "04c9c807-68d0-4750-bd72-a484730cd55d"
 ```
@@ -181,9 +181,14 @@ points future agents at the obsolete mega-hub/Inter-Hub scaffold sequence.
 summarizes the Core Hub replacement proof from `CORE-WP-0008-T02` through
 `T06`, records why `CUST-WP-0047-T05` and `CUST-WP-0049-T06` should remain
 legacy/fallback wait tasks for now, and gives rewrite guidance for
-`CUST-WP-0025-T13` through `T19`. The actual `CUST-WP-0025` rewrite is still
-open because no live deployed Core Hub smoke ids/counts or cutover proof exist
-yet.
+`CUST-WP-0025-T13` through `T19`.
+
+Completed 2026-06-27: rewrote `CUST-WP-0025-T13` through `T19` around Core
+Hub-owned API evidence, operator CLI parity, deployed smoke/cutover gates, and
+the whynot-aligned Core Hub UI backlog. The rewrite marks the old immediate
+standalone ops-hub MCP registration as cancelled, keeps deployed evidence and
+cutover tasks waiting on real staging/runtime proof, and does not claim Haskell
+retirement is unblocked.
 
 ## Task: Align Helixforge Build And Environment Practices
 
@@ -265,8 +270,8 @@ workplan notes, not buried in chat.
 
 - CUST-WP-0051, CUST-WP-0047, and CUST-WP-0049 point toward Core Hub replacement
   instead of further Inter-Hub expansion.
-- CUST-WP-0025 has a clear reset gate and no one resumes the old standalone
-  ops-hub scaffold until it is rewritten.
+- CUST-WP-0025 Phase 3 has been rewritten so no one resumes the old
+  standalone ops-hub scaffold sequence.
 - The next implementation lane is API first, CLI second, web UI third.
 - UI rebuild expectations name whynot-design and operator-priority views.
 - External ops-warden needs are routed through State Hub requirements, not