diff --git a/docs/infrastructure-stabilization-pickup-checkpoint.md b/docs/infrastructure-stabilization-pickup-checkpoint.md
index b9e67a1..9830ad4 100644
--- a/docs/infrastructure-stabilization-pickup-checkpoint.md
+++ b/docs/infrastructure-stabilization-pickup-checkpoint.md
@@ -3,17 +3,52 @@
 Updated: 2026-07-02
 Coordinator workplan: `CUST-WP-0051`
 
-## Operator Pickups Ready Now (updated 2026-07-02 afternoon)
+## End-of-Day Checkpoint (2026-07-02 evening)
 
-All five morning gates are closed (deploy, CCRs, audit evidence, applier
-proof, unseal-wiring review). The issue-core REST emission lane is live
-end-to-end (Gitea issue `176`), the llm-connect OpenRouter lane is active,
-and the credential lifecycle runbook exists. The single open operator item is
-the **Core Hub staging deployment decision set** (CUST-WP-0025-T16 /
-CORE-WP-0004): target cluster (recommended CoulombCore), staging secret
-posture (recommended generated K8s Secrets), and image path (recommended
-Gitea registry — needs explicit approval because `coulomb` org packages are
-public). Image `core-hub:ba32597` is pre-built locally; registry auth exists.
+Nine workplans finished today and the Core Hub replacement lane was driven
+from no deployed evidence to real data migrated with cutover blockers named.
+
+**Finished this session:** ARTIFACT-STORE-WP-0007, RAIL-BS-WP-0008,
+RAIL-BS-WP-0009, ACTIVITY-WP-0016, RAILIANCE-WP-0008, ISSUE-WP-0003,
+CORE-WP-0004 (+ CUST-WP-0053 earlier). RAILIANCE-WP-0009/0010 are done bar
+ops-warden catalog confirmation; NET-WP-0020-T02 is wired (needs a greenfield
+slate for live proof).
+
+**Live infrastructure now running (was blocked at session start):**
+
+- Daily-triage robustness deployed on railiance01; bounded top-7 proven
+  (State Hub event `24d2d321`). Three scheduled runs (Jul 3–5) close
+  ACTIVITY-WP-0006 calibration by themselves.
+- Credential lanes active: issue-core (`CCR-2026-0002`) and llm-connect
+  OpenRouter (`CCR-2026-0003`), applied via the constrained prod-applier,
+  both ExternalSecrets syncing. Lifecycle runbook at
+  `railiance-platform/docs/credential-lane-lifecycle-runbook.md`.
+- issue-core REST emission live end-to-end (Gitea issue `176`) over a new
+  cross-machine ops-bridge lane (`remote_host` feature added to ops-bridge).
+- Core Hub staging deployed on CoulombCore (`core-hub-staging`, image
+  `gitea.coulomb.social/coulomb/core-hub:3ed8531`): deployed API smoke +
+  activity-core sink smoke both green; full Inter-Hub data (28 records)
+  migrated idempotently.
+
+**Open items requiring a decision (not agent-executable):**
+
+1. **Core Hub cutover prerequisites (core-hub owner).** T03 dual-run found (a)
+   a blocking catalog gap — migrated widgets reference 7 `ops-*` widget types
+   absent from Core Hub's seeded registries because the migration bundle
+   omits the type registries; design choice: extend the bundle schema vs.
+   seed the vocabularies; (b) `/api/v2/hubs` auth-posture break (public →
+   protected). Both on `CORE-WP-0005-T04`; flagged via hub message `4b859f9b`.
+2. **Core Hub production cutover** (`CORE-WP-0005-T04`): operator approval +
+   rollback plan, after prerequisite 1. Then `CORE-WP-0007` Haskell
+   retirement unblocks.
+3. **State Hub pragmatic cutover** (`CUST-WP-0011-T07`): still the standing
+   operator freeze/restore/redirect approval (unchanged from prior board).
+4. **ops-warden confirmations** close `RAILIANCE-WP-0009-T06` /
+   `RAILIANCE-WP-0010-T06` (no custodian action).
+5. **NET-WP-0020-T02** greenfield live proof needs a rebuild slate.
+
+Prior morning decision set (Core Hub staging cluster/secrets/image) is
+resolved: CoulombCore + generated Secrets + Gitea registry, all executed.
 
 ## Original morning list (2026-07-02, all closed)
 
diff --git a/workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md b/workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md
index 09e9bf9..ff5016b 100644
--- a/workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md
+++ b/workplans/CUST-WP-0051-infrastructure-stabilization-metaplan.md
@@ -256,7 +256,7 @@ Progress 2026-06-27 Core Hub pivot:
 
 ```task
 id: CUST-WP-0051-T04
-status: progress
+status: done
 priority: high
 state_hub_task_id: "42810d3b-5557-4efd-871b-65bef7c19e0e"
 ```
@@ -352,7 +352,7 @@ Progress 2026-07-02 live deploy (operator-authorized):
 
 ```task
 id: CUST-WP-0051-T05
-status: progress
+status: done
 priority: medium
 state_hub_task_id: "2083f0e4-e037-48bf-8069-f31e8db2fd95"
 ```
@@ -688,6 +688,19 @@ Progress 2026-07-02 Core Hub staging deployed:
   (runtime token + widget mapping), staging import (`CORE-WP-0005-T02`),
   dual-run/cutover readiness, and Haskell retirement approval.
 
+Closeout 2026-07-02 (T04): the daily-triage runner is deployed on railiance01
+and proven — one trusted runner emitting bounded top-7 schema-valid reports
+(event `24d2d321`), coupled schema/executor shipped together, admin-sync
+no-restart proven. The three-clean-run calibration streak continues in
+ACTIVITY-WP-0006 (scheduled Jul 3–5, calendar-only). T04 done.
+
+Closeout 2026-07-02 (T05): each near-term service lane is now finished or
+cleanly parked — issue-core REST emission finished (ISSUE-WP-0003, Gitea issue
+176), artifact-store MinIO/STS finished (ARTIFACT-STORE-WP-0007), staged
+promotion finished (RAIL-BS-WP-0006). Forgejo (RAIL-HO-WP-0005) and
+SECRETS-WP-0003 remain parked behind explicit design/publish decisions with no
+ambiguous human-needed state. T05 done.
+
 ## Task: Create The Stable Pickup Checkpoint
 
 ```task