Rewrite FOS ops hub phase for Core Hub

workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md

@@ -456,21 +456,22 @@ Progress 2026-06-27:
   `NK-WP-0001` Keycloak task is cancelled as superseded, `NK-WP-0002` local
   identity is done, and the remaining identity gate is the IAM Profile v0.2
   FastAPI integration test.
-- Current ops-hub reality is extension-first: `ops-hub` exists,
-  `OPS-WP-0001` is finished, and `OPS-WP-0002` waits on authenticated
-  Inter-Hub bootstrap/runtime-key evidence. Reconcile `CUST-WP-0025-T13`-`T19`
-  after the first governed ops event lands.
+- Current ops-hub reality is Core Hub replacement-first: `CORE-WP-0008`
+  finished the API smoke harness, activity-core sink, staging profile, CLI
+  wrappers, UI rebuild backlog, and Custodian handoff. `CUST-WP-0025-T13`-`T19`
+  have been rewritten away from the obsolete standalone scaffold.
 - Fin-hub/business tasks remain deliberately deferred until identity integration
   and ops-hub extension evidence are proven.
 
 Progress 2026-06-27 Core Hub reset:
 
-- `CUST-WP-0052` now owns the reset criteria. `CUST-WP-0025-T13` through
-  `T19` should not be executed literally as the old standalone ops-hub scaffold
-  until Core Hub replacement evidence is good enough and the tasks are rewritten.
-- Core Hub is promising enough to stop expanding the Inter-Hub-first path:
-  local ops-hub bootstrap compatibility and `/console` visual checks exist, but
-  staging import, deployed dual-run smokes, and cutover evidence are still open.
+- `CUST-WP-0052` completed the Phase 3 reset. `CUST-WP-0025-T13` through
+  `T19` now point at Core Hub-owned API evidence, CLI parity, deployed
+  smoke/cutover gates, whynot-aligned UI, and cancellation of immediate
+  standalone ops-hub MCP registration.
+- Core Hub is now the preferred replacement lane, but staging import, deployed
+  dual-run smokes, cutover evidence, and Haskell retirement approval remain
+  open.
 
 ## Task: Create The Stable Pickup Checkpoint