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

The live-file pass missed these: archived ad-hocs carry a YYMMDD- filename
prefix, so the ADHOC-* glob did not match them. They still derive from the
forge, so they are live records rather than dead files.

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
This commit is contained in:
tegwick 2026-08-28 00:34:05 +02:00
parent bd9ed7392c
commit ba10e325d3

View file

@ -1,5 +1,5 @@
---
id: ADHOC-2026-06-27
id: WHYNOT-WP-ADHOC-2026-06-27
type: workplan
title: "Ad hoc fixes — 2026-06-27"
domain: infotech
@ -9,7 +9,6 @@ owner: claude
topic_slug: custodian
created: "2026-06-27"
updated: "2026-06-27"
state_hub_workstream_id: "4945ead3-d54b-438f-963a-2fd687c472d4"
---
> **Terminology note:** Historical text in this archived workplan may use the legacy term "workstream". The fleet term is **workplan** (`canon/standards/workplan-terminology-fleet_v0.1.md`).
@ -21,10 +20,9 @@ Low-risk opportunistic fixes completed directly during the WHYNOT-WP-0003 sessio
## README consumer-onboarding accuracy
```task
id: ADHOC-2026-06-27-T01
id: WHYNOT-WP-ADHOC-2026-06-27-T01
status: done
priority: medium
state_hub_task_id: "76417728-969c-4b26-9ed8-f6cedd793ff4"
```
Two staleness fixes in `README.md` found while reviewing the consumer on-ramp: