chore(WARDEN-WP-0018): stamp state_hub task ids from consistency sync

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

workplans/WARDEN-WP-0018-whynot-design-npm-lane-activation.md

@@ -11,6 +11,7 @@ planning_priority: high
 planning_order: 18
 created: "2026-06-29"
 updated: "2026-06-29"
+state_hub_workstream_id: "1256aca2-5979-4d21-818e-0de42c5d811b"
 ---
 
 # WARDEN-WP-0018 — whynot-design npm lane activation + `resolvable` flag
@@ -38,6 +39,7 @@ publish-vs-read scope split.
 id: WARDEN-WP-0018-T01
 status: done
 priority: high
+state_hub_task_id: "189d0883-22b9-42dc-bda0-89460509a87d"
 ```
 
 - [x] Added `whynot-design-npm-publish` to `registry/routing/catalog.yaml` (`status: active`,
@@ -56,6 +58,7 @@ priority: high
 id: WARDEN-WP-0018-T02
 status: done
 priority: high
+state_hub_task_id: "b5dc1013-5334-43ff-afd6-1f99d521358f"
 ```
 
 - [x] `RouteEntry.resolvable` — true when a lane is active, exec_capable, and its fetch
@@ -75,6 +78,7 @@ priority: high
 id: WARDEN-WP-0018-T03
 status: done
 priority: medium
+state_hub_task_id: "95b00ef8-477a-4f0d-bd71-6154fba401f5"
 ```
 
 - [x] Notified whynot-design (reply 744977ae) with the zero-placeholder command