fix(workplans): qualify ad-hoc identifiers with the repository prefix
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

`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>
This commit is contained in:
codex 2026-08-28 00:28:24 +02:00
parent e44a271910
commit fab1cb19a1
3 changed files with 8 additions and 14 deletions

View file

@ -1,5 +1,5 @@
---
id: ADHOC-2026-08-25
id: CUST-WP-ADHOC-2026-08-25
type: workplan
title: "Ad hoc tasks 2026-08-25"
domain: infotech
@ -8,7 +8,6 @@ status: active
owner: codex
created: "2026-08-25"
updated: "2026-08-25"
state_hub_workstream_id: "1c53d3db-6633-5e2d-987f-10706d73be9e"
---
# Ad hoc tasks 2026-08-25
@ -16,10 +15,9 @@ state_hub_workstream_id: "1c53d3db-6633-5e2d-987f-10706d73be9e"
## Verify one-pass workplan binding
```task
id: ADHOC-2026-08-25-T01
id: CUST-WP-ADHOC-2026-08-25-T01
status: done
priority: low
state_hub_task_id: "d8af3e6b-26ae-580c-bbeb-caa8ad419bec"
```
Confirm that a newly registered workplan records its backing file without a