chore(consistency): record ACTIVITY-WP-0030 hub IDs

Write back the workplan and task UUIDs from fix-consistency so the
daily SBOM catch-up plan stays indexed in WORK-RECORDS.md.

workplans/ACTIVITY-WP-0030-daily-sbom-catchup.md

@@ -14,6 +14,7 @@ related:
   - CUST-WP-0062
   - ACTIVITY-WP-0022
   - ADHOC-2026-06-01
+state_hub_workstream_id: "bfe2945e-38df-40d1-94d4-6e4a003ef66d"
 ---
 
 # Daily bounded SBOM catch-up via sbom-nexus
@@ -53,6 +54,7 @@ each. The replacement must ask sbom-nexus for **only N targets** and then
 id: ACTIVITY-WP-0030-T01
 status: todo
 priority: high
+state_hub_task_id: "b216976e-5402-4e40-b282-78c5d021df72"
 ```
 
 Write `activity-definitions/daily-sbom-catchup.md` (`enabled: false` until
@@ -75,6 +77,7 @@ lands):
 id: ACTIVITY-WP-0030-T02
 status: wait
 priority: high
+state_hub_task_id: "0d09c0d3-74bd-4f4d-8b27-5006ba010fa3"
 ```
 
 Wait on CUST-WP-0062-T03. Bounded side-effect (SCOPE: declared purpose only):
@@ -90,6 +93,7 @@ oldest never-scanned repo.
 id: ACTIVITY-WP-0030-T03
 status: wait
 priority: high
+state_hub_task_id: "18bcfc21-616a-48a2-aac3-cdcef7579913"
 ```
 
 After the daily job is proven on railiance01: set
@@ -104,6 +108,7 @@ spawns and a successful daily catch-up the same week.
 id: ACTIVITY-WP-0030-T04
 status: wait
 priority: medium
+state_hub_task_id: "f09144f6-c7f9-41d4-b466-d8a6288e6a21"
 ```
 
 Project the definition into `k8s/railiance/20-runtime.yaml`, sync schedules,