chore(consistency): register FLEX-WP-0022 and refresh work records

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014aQMM1dPXaPiXVn6DwwtLd

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 715613@bnt-lap001
Assistant-Session: fabd95c1-4c9e-4080-8849-8707ae025f80

workplans/FLEX-WP-0022-tenant-scope-coverage.md

@@ -16,6 +16,7 @@ related_workplans:
   - FLEX-WP-0014
 created: "2026-09-06"
 updated: "2026-09-06"
+state_hub_workstream_id: "804c588c-f47a-50c4-bdd7-51b24bbf9539"
 ---
 
 # FLEX-WP-0022 — Tenant scoping is unstated in tenant-engine and untested in two more packages
@@ -58,6 +59,7 @@ look identical in the artifact. That is the same publishing-shape argument
 id: FLEX-WP-0022-T01
 status: todo
 priority: high
+state_hub_task_id: "a84dcee5-9426-5b30-8dd3-f4c076d00174"
 ```
 
 Owner: `flex-auth` to ask; `tenant-engine` owns the answer.
@@ -76,6 +78,7 @@ Gate: the relation is named by `tenant-engine`, not inferred here. This is the
 id: FLEX-WP-0022-T02
 status: wait
 priority: high
+state_hub_task_id: "712ac826-845f-54bd-8446-f11258d21eb4"
 ```
 
 Owner: `flex-auth`.
@@ -96,6 +99,7 @@ Either way the fixtures must vary `tenant`, so the suite reports on the field.
 id: FLEX-WP-0022-T03
 status: todo
 priority: medium
+state_hub_task_id: "3058f171-99d2-526b-a1bb-bd7aed87d10a"
 ```
 
 Owner: `flex-auth`.