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>

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

workplans/ADHOC-2026-07-03.md

@@ -1,5 +1,5 @@
 ---
-id: ADHOC-2026-07-03
+id: ADAPTIVE-WP-ADHOC-2026-07-03
 type: workplan
 title: "Ad hoc repo maintenance - 2026-07-03"
 domain: financials
@@ -9,7 +9,6 @@ owner: codex
 topic_slug: helix-forge
 created: "2026-07-03"
 updated: "2026-07-03"
-state_hub_workstream_id: "f5c22683-5dd8-46e9-9ff3-2215af2eb66e"
 ---
 
 # Ad hoc repo maintenance - 2026-07-03
@@ -17,10 +16,9 @@ state_hub_workstream_id: "f5c22683-5dd8-46e9-9ff3-2215af2eb66e"
 ## Refresh Scope Document To Match Implemented Capabilities
 
 ```task
-id: ADHOC-2026-07-03-T01
+id: ADAPTIVE-WP-ADHOC-2026-07-03-T01
 status: done
 priority: medium
-state_hub_task_id: "1443b72e-2ee2-4c49-98a4-b309bf99e917"
 ```
 
 Update `SCOPE.md` so the repo boundary, current state, and execution limits