Sync USER-WP-0008 and USER-WP-0009 with StateHub

workplans/USER-WP-0009-postgres-durable-store-requirements.md

@@ -13,6 +13,7 @@ created: "2026-06-05"
 updated: "2026-06-05"
 depends_on:
   - USER-WP-0007
+state_hub_workstream_id: "b5c85993-4aa2-4a8d-98b6-d174ab1b4538"
 ---
 
 # USER-WP-0009 - Postgres Durable Store Consumer Requirements
@@ -52,6 +53,7 @@ schema, migrations for its own tables, store semantics, and conformance tests.
 id: USER-WP-0009-T1
 status: todo
 priority: high
+state_hub_task_id: "64c578e1-e2a1-48d4-8da9-659d4f881ef3"
 ```
 
 Inventory the current in-memory store behavior and document the durable
@@ -64,6 +66,7 @@ schema version reporting.
 id: USER-WP-0009-T2
 status: todo
 priority: high
+state_hub_task_id: "19cfd23e-8a87-416d-b948-c727e8c5a11c"
 ```
 
 Create a consumer-facing requirements document for a Postgres durable store.
@@ -75,6 +78,7 @@ security, observability, backup/restore expectations, and acceptance tests.
 id: USER-WP-0009-T3
 status: todo
 priority: high
+state_hub_task_id: "d3b388de-bb79-41d5-805e-d2def88ac926"
 ```
 
 Define the boundary between user-engine and the future NetKingdom Postgres
@@ -86,6 +90,7 @@ secrets, authorization, or audit-platform concerns.
 id: USER-WP-0009-T4
 status: todo
 priority: medium
+state_hub_task_id: "d0e05af7-d777-4948-b072-79f1ffb9fc3a"
 ```
 
 Identify required changes, if any, to the existing store protocol or migration
@@ -96,6 +101,7 @@ the isolated MVP without leaking Postgres concepts into domain code.
 id: USER-WP-0009-T5
 status: todo
 priority: medium
+state_hub_task_id: "3c428960-be5b-411e-bd9b-7cba833abba8"
 ```
 
 Define conformance scenarios and failure-mode tests the future Postgres store
@@ -107,6 +113,7 @@ readiness, and redacted diagnostics.
 id: USER-WP-0009-T6
 status: todo
 priority: medium
+state_hub_task_id: "d606094a-254c-46d5-9bb8-a3449ce61c2c"
 ```
 
 Record open questions for the independent provider repository, including