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-08-21.md

@@ -1,5 +1,5 @@
 ---
-id: ADHOC-2026-08-21
+id: KAIZEN-WP-ADHOC-2026-08-21
 type: workplan
 title: "Ad hoc Glas execution-boundary alignment"
 domain: agents
@@ -9,7 +9,6 @@ owner: codex
 topic_slug: glas-execution-boundary-alignment
 created: "2026-08-21"
 updated: "2026-08-21"
-state_hub_workstream_id: "643a3710-9778-54d2-8bd5-cdc23a4139a6"
 ---
 
 # Ad hoc Glas execution-boundary alignment
@@ -17,10 +16,9 @@ state_hub_workstream_id: "643a3710-9778-54d2-8bd5-cdc23a4139a6"
 ## Align the documented execution handoff with Glas contract 1.0
 
 ```task
-id: ADHOC-2026-08-21-T01
+id: KAIZEN-WP-ADHOC-2026-08-21-T01
 status: done
 priority: high
-state_hub_task_id: "2d309354-7a5f-59f2-9817-15545f0fda5e"
 ```