fix(workplans): adopt ADR-007 derived identifiers for unregistered records

These workplans exist only in the retired local hub. Their random pre-ADR-007
identifiers are refused by C-06 as stale references, so they cannot be
registered. Deriving from the canonical record id takes no identity from
anything: central does not hold them and the old ids die with the cache.

Records central already holds were deliberately left untouched.

Refs CUST-WP-0068-T06

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006

workplans/ISSUE-WP-0005-connector-alignment-implementation.md

@@ -9,7 +9,7 @@ owner: codex
 topic_slug: infotech
 created: "2026-07-22"
 updated: "2026-07-22"
-state_hub_workstream_id: "22167b3c-0707-4c24-8407-58c4bd8b8f75"
+state_hub_workstream_id: "08af499c-328f-53f8-8899-ae818fce048d"
 ---
 
 # Implement connector alignment: mapping, docs hygiene, scope gaps vs refined INTENT
@@ -68,7 +68,7 @@ without turning issue-core back into a work origin or fleet task board.
 id: ISSUE-WP-0005-T01
 status: done
 priority: high
-state_hub_task_id: "f538d48e-11b1-4859-9f39-a1103b90c05b"
+state_hub_task_id: "024ae2f2-32c5-513f-a7b1-2cde1a1a141b"
 ```
 
 Ensure INTENT, SCOPE, README “See also”, and the alignment review all point at
@@ -85,7 +85,7 @@ done; no reintroduction of landing-zone language in those files.
 id: ISSUE-WP-0005-T02
 status: done
 priority: medium
-state_hub_task_id: "53889021-53ed-4f98-a144-f7c211a58def"
+state_hub_task_id: "e86786d7-0bd4-591c-87db-8780cc53d238"
 ```
 
 Align packaging/metadata with connector intent (not “authoritative task
@@ -107,7 +107,7 @@ capability summary matches SCOPE §1 honesty.
 id: ISSUE-WP-0005-T03
 status: done
 priority: high
-state_hub_task_id: "d2fa5a3c-12ef-4a75-a8c9-b7843d507396"
+state_hub_task_id: "cd4e298c-9a42-5d35-a8e3-40626f5a0fd8"
 ```
 
 Turn INTENT’s boundary-sync discipline into an implementable policy doc under
@@ -131,7 +131,7 @@ policy.
 id: ISSUE-WP-0005-T04
 status: done
 priority: high
-state_hub_task_id: "a8f0d528-1b1f-4dfb-8df0-9c9ffd56e47c"
+state_hub_task_id: "027871b0-696d-5ab7-b18c-b26167e97813"
 ```
 
 Per `docs/uuid-external-id-mapping.md`:
@@ -154,7 +154,7 @@ note until CLI/API land.
 id: ISSUE-WP-0005-T05
 status: done
 priority: high
-state_hub_task_id: "1866bec4-e4df-444c-b633-aa97c83c0940"
+state_hub_task_id: "b9a18d1d-9b0b-5a5b-9b1f-c6cf89f6767a"
 ```
 
 Ship operator surface:
@@ -177,7 +177,7 @@ backend; idempotent re-project returns existing mapping.
 id: ISSUE-WP-0005-T06
 status: done
 priority: medium
-state_hub_task_id: "8e02509b-d304-45d9-b99b-1016dc325cfd"
+state_hub_task_id: "2a1f83ae-236a-588d-8127-deaff04b84a8"
 ```
 
 - Add optional `work_record_uuid` (and optional `work_record_id` /
@@ -197,7 +197,7 @@ uses it.
 id: ISSUE-WP-0005-T07
 status: done
 priority: medium
-state_hub_task_id: "5bea7ad1-3df5-4cf3-b79a-e89ac7ad5af1"
+state_hub_task_id: "e37e7f4a-ab35-52e3-929f-960dfde14348"
 ```
 
 Implement **outward-only** application of T03 rules for mapped records
@@ -217,7 +217,7 @@ SCOPE distinguishes backend sync vs work-record boundary sync clearly.
 id: ISSUE-WP-0005-T08
 status: done
 priority: medium
-state_hub_task_id: "ca55014a-694d-4a46-beea-cb1f2f438ada"
+state_hub_task_id: "45fac55a-5000-51c5-96a8-920b3d1179d7"
 ```
 
 After T04–T07, rewrite SCOPE §1 / §1.8 / §2 so shipped vs target matches
@@ -233,7 +233,7 @@ leakage into “shipped today.”
 id: ISSUE-WP-0005-T09
 status: done
 priority: low
-state_hub_task_id: "fe209013-d9de-4709-bc58-41abe186959d"
+state_hub_task_id: "4b0dd409-e23e-5e2f-9d6e-a3ae1664fb88"
 ```
 
 - Confirm ACTIVITY-WP-0022 still covers default sink policy