CORE-WP-0005-T02 done: Inter-Hub exporter + staging import (28 records, idempotent)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

workplans/CORE-WP-0005-data-migration-and-cutover.md

@@ -31,7 +31,7 @@ Result 2026-06-27: Defined and implemented the `core-hub.migration.v1` bundle pa
 
 ```task
 id: CORE-WP-0005-T02
-status: wait
+status: done
 priority: high
 state_hub_task_id: "e0ea0928-a3ea-4ece-bbb7-ee08f8a3279b"
 ```
@@ -66,3 +66,21 @@ state_hub_task_id: "fa68858a-b18e-4f09-a477-6b11e54099d4"
 ```
 
 With operator approval, switch production traffic such as `hub.coulomb.social` to Core Hub. Keep rollback available until stabilization passes.
+
+
+## Progress 2026-07-02 — staging import completed
+
+Built the Inter-Hub exporter (`scripts/migration/inter_hub_export.sql`, read-only
+against the `interhub` DB on net-kingdom-pg) emitting a validated
+`core-hub.migration.v1` bundle (sha256 `e1b53b7f2d67ef7a…`): 1 hub (`ops-hub`),
+1 manifest, 2 api consumers, 8 api keys (prefix+hash only), 15 widgets, 1
+interaction event. `migration validate` passed with zero errors/warnings and no
+secret material.
+
+Imported into Core Hub staging via an in-cluster Job (staging DB URL from
+`core-hub-staging-env` secretKeyRef, bundle via ConfigMap): dry-run `ok=true`
+(28 would-create), real import created all 28 records with zero errors, and a
+second run proved idempotency (created=0, updated=28, no duplicates).
+Server-side confirmed: the imported `ops-hub` hub and its 15 widgets are visible
+via `/api/v2/*`. T02 done; the staging DB now holds real Inter-Hub data for the
+T03 dual-run smokes.