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>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
This commit is contained in:
codex 2026-08-28 00:28:23 +02:00
parent d8a3ff9e5f
commit 7e0ecba24e

View file

@ -1,5 +1,5 @@
---
id: RAIL-BS-ADHOC-2026-07-27
id: RAIL-BS-RCLUSTER-WP-ADHOC-2026-07-27
type: workplan
title: "Knative fail-closed init-container support"
domain: financials
@ -9,18 +9,16 @@ owner: codex
topic_slug: railiance
created: "2026-07-27"
updated: "2026-07-27"
state_hub_workstream_id: "9a77bc91-f457-5545-996f-04f49707f54b"
---
# RAIL-BS-ADHOC-2026-07-27
# RAIL-BS-RCLUSTER-WP-ADHOC-2026-07-27
## Enable and verify Knative init containers
```task
id: RAIL-BS-ADHOC-2026-07-27-T01
id: RAIL-BS-RCLUSTER-WP-ADHOC-2026-07-27-T01
status: done
priority: high
state_hub_task_id: "fd47a55b-233d-53ec-8005-7e24b2a98e42"
```
Enable only `kubernetes.podspec-init-containers` in Knative