diff --git a/workplans/CUST-WP-0025-fos-hub-bootstrap.md b/workplans/CUST-WP-0025-fos-hub-bootstrap.md
index 71aadcb..d731de4 100644
--- a/workplans/CUST-WP-0025-fos-hub-bootstrap.md
+++ b/workplans/CUST-WP-0025-fos-hub-bootstrap.md
@@ -475,7 +475,7 @@ rather than becoming the first implementation path.
 
 ```task
 id: CUST-WP-0025-T16
-status: wait
+status: progress
 priority: high
 state_hub_task_id: "702849c5-b253-4ede-afa7-0ab4f81e49a5"
 ```
@@ -498,6 +498,18 @@ path, and activity-core widget mapping are available. This task can close or
 supersede `CUST-WP-0047-T05` and `CUST-WP-0049-T06` only after deployed Core
 Hub evidence exists or an explicit supersede decision is recorded.
 
+Progress 2026-07-02: the first evidence bullet is met. Core Hub staging is
+deployed on CoulombCore (operator-approved: namespace `core-hub-staging`,
+image `gitea.coulomb.social/coulomb/core-hub:3ed8531`, dedicated apps-pg
+database, migrate job complete). The deployed smoke ran in-cluster with the
+operator token confined to the namespace: run `20260702143544-6c8f18`,
+`ok=true`, 10/10 API checks plus the full ops-hub bootstrap sequence (hub
+`6798723a`, activated manifest, API consumer prefix `ch_N0ZhsXIbD`, widget,
+interaction event `21d09f99`, hub registry containment true). Remaining T16
+evidence: the deployed activity-core Core Hub sink smoke (runtime token +
+widget mapping), then the supersede decision for `CUST-WP-0047-T05` /
+`CUST-WP-0049-T06` becomes decidable on evidence.
+
 ### T17 — Core Hub, dev-hub, and cutover decision coupling
 
 ```task
diff --git a/workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md b/workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md
index f45b424..09e9bf9 100644
--- a/workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md
+++ b/workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md
@@ -677,6 +677,17 @@ Progress 2026-06-27 Core Hub operator UI first screens:
   `T17` cutover decision coupling; both still require staging/runtime custody or
   migration evidence.
 
+Progress 2026-07-02 Core Hub staging deployed:
+
+- The T07 Core Hub replacement lane got its first deployed proof: staging on
+  CoulombCore with the full smoke evidence chain (see `CUST-WP-0025-T16`
+  progress and `CORE-WP-0004-T03`, now done). Two defects fixed en route:
+  missing `psycopg2-binary` in the runtime image and the apps-pg
+  NetworkPolicy label requirement (`railiance.io/postgres-client=apps-pg`).
+- Remaining Core Hub gates: activity-core sink smoke against staging
+  (runtime token + widget mapping), staging import (`CORE-WP-0005-T02`),
+  dual-run/cutover readiness, and Haskell retirement approval.
+
 ## Task: Create The Stable Pickup Checkpoint
 
 ```task