fix(workplans): qualify ad-hoc identifiers with the repository prefix

`ADHOC-YYYY-MM-DD` is unique per date but not per repository, so any two repos
opening an ad-hoc on the same day collide. The 2026-08-26 fleet projection
reset refused 9 records for exactly this reason.

Canon (work-record-types_v0.1, CUST-WP-0066) settled the form as
`{PREFIX}-WP-ADHOC-YYYY-MM-DD`, filename unchanged, and grandfathered existing
ids on the condition they are never *silently* re-derived. This is the explicit
migration that clause allows for.

The hub id is derived from the record id, so a changed id is a different
record: stale state_hub_*_id fields are dropped and fix-consistency re-derives.

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

workplans/ADHOC-2026-07-02.md

@@ -1,5 +1,5 @@
 ---
-id: ADHOC-2026-07-02
+id: CUST-WP-ADHOC-2026-07-02
 type: workplan
 title: "Ad Hoc Tasks — 2026-07-02"
 domain: infotech
@@ -9,10 +9,9 @@ owner: codex
 topic_slug: custodian
 created: "2026-07-02"
 updated: "2026-07-02"
-state_hub_workstream_id: "5c53733b-c077-4a93-be66-9c3af8f9b6fd"
 ---
 
-# ADHOC-2026-07-02 — Ad Hoc Tasks
+# CUST-WP-ADHOC-2026-07-02 — Ad Hoc Tasks
 
 Small same-day improvements that are useful to track, but do not justify a
 dedicated requirement/workplan cycle.
@@ -20,10 +19,9 @@ dedicated requirement/workplan cycle.
 ## Extend Canonical Capability Tags
 
 ```task
-id: ADHOC-2026-07-02-T01
+id: CUST-WP-ADHOC-2026-07-02-T01
 status: done
 priority: medium
-state_hub_task_id: "1fad5239-3130-4453-ba71-b89323567006"
 ```
 
 Extend the repo-classification canon so `monetization`, `lifecycle`,