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/RPF-WP-0018-policy-surface-alignment.md

@@ -15,7 +15,7 @@ related:
   - RAPP-POSTGRES-WP-0002
 origin: routed
 origin_ref: "net-kingdom/canon/standards/tenancy-posture_v0.1.md §19.2, §20"
-state_hub_workstream_id: "d40827cb-bb48-4cdd-9b41-8dfae116d705"
+state_hub_workstream_id: "4fcb6026-2630-59a3-b5de-15f54efcf59d"
 ---
 
 # RPF-WP-0018 — policy surface alignment
@@ -181,7 +181,7 @@ repo's `docs/adr/README.md` is one repo's answer to it.
 id: RPF-WP-0018-T01
 status: done
 priority: high
-state_hub_task_id: "ff392a23-e72a-4442-843f-929f218404ae"
+state_hub_task_id: "88d1342b-5093-5fbc-aa84-1608d163b979"
 ```
 **Publish the S3 posture vector set.** Write `docs/tenancy-posture.md`:
 one vector per service under S3 custody (`openbao`, `apps-pg`, and the
@@ -194,7 +194,7 @@ Route F4 to `net-kingdom` with the vector set as the evidence.
 id: RPF-WP-0018-T02
 status: done
 priority: high
-state_hub_task_id: "962fc494-bb9b-4f67-8e5b-2ed88a670945"
+state_hub_task_id: "03f0a5bd-7876-5784-bf02-11cbcdf005bb"
 ```
 **Accept placement ownership, scoped.** Write `docs/placement-policy.md`:
 adopt the P0–P4 ladder by reference (do not restate it — the canon copy is
@@ -208,7 +208,7 @@ either way.
 id: RPF-WP-0018-T03
 status: done
 priority: medium
-state_hub_task_id: "f6f30233-3f6e-44a0-a644-7268f9d88f3c"
+state_hub_task_id: "b602226f-8eb5-5609-995f-94f9074b0895"
 ```
 **Make triggers monitorable or honestly unmonitored.** For each of the five
 §8 triggers, record in `docs/placement-policy.md` what signal would fire it,
@@ -222,7 +222,7 @@ report which service classes are co-resident. Today that is
 id: RPF-WP-0018-T04
 status: done
 priority: medium
-state_hub_task_id: "8a3ce90b-8af2-4dcd-9a35-77025d2123f2"
+state_hub_task_id: "92ce14f6-afee-50f6-abd4-197c4724a589"
 ```
 **Disclose quotas to consumers (§10.2).** Extend
 `docs/s3-consumer-interfaces.md` to `1.1.0` — additive under its own
@@ -235,7 +235,7 @@ these is announced to bound consumers, not discovered by them.
 id: RPF-WP-0018-T05
 status: done
 priority: medium
-state_hub_task_id: "a6da631d-fa4e-4c2b-acc3-d3cf53cfb57f"
+state_hub_task_id: "58ef22f8-7f1b-5647-babd-eeb817b3ae31"
 ```
 **Create the ADR surface (F2).** Create `docs/adr/` with an ADR template
 carrying the frontmatter `policy-nexus` T02/T05 consume: title, status,
@@ -250,7 +250,7 @@ only home for a decision.
 id: RPF-WP-0018-T06
 status: done
 priority: low
-state_hub_task_id: "99f2a4d8-b20c-4c43-8c94-0bc469bfcc46"
+state_hub_task_id: "49c682a0-a9b7-59f0-ad65-79b4fb9bb79c"
 ```
 **Answer §19.9 — retention floor and ceiling.** Decide whether
 `backupRetentionDays` gets a platform minimum (so a consumer asking for one
@@ -264,7 +264,7 @@ maximum declared across co-residents, so a shorter horizon is a P2 trigger.
 id: RPF-WP-0018-T07
 status: done
 priority: high
-state_hub_task_id: "b021fda3-23bd-4843-8d1b-983b6ec582b5"
+state_hub_task_id: "ad7a159b-a395-50e0-a517-d605a1d70108"
 ```
 **Route the findings.** Reply to `rapp-postgres` and `tenant-engine` with
 T01/T02 outcomes and F3/F4. Reply to `policy-nexus` with F1 (substrate