docs(workplans): prepare identifier batch and SBOM client follow-up

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
This commit is contained in:
tegwick 2026-08-22 22:25:11 +02:00
parent bc0ee85ffa
commit 062a45fc58
6 changed files with 2579 additions and 0 deletions

View file

@ -487,6 +487,23 @@ and pre-existing conformance warnings are in
`docs/evidence/RMGR-WP-0005-batch-0003-markitect-cutover-2026-08-22.md`. T04
remains in progress for separately sealed and approved fleet batches.
**Batch 0004 prepared (2026-08-22):** `railiance-cluster` is the smallest next
replacement batch represented in both current projections. Its clean source is
published and synchronized at `41fdfd9`; the refreshed fleet plan and source
fingerprint verify without drift. The batch replaces `RCLUSTER-WP-0007` and
five live task UUIDs. Its two cancelled task UUIDs remain outside the live
migration plan and follow the replaced parent through the database cascade.
Both projections contain the old six mapped rows and none of the targets. Each
retains seven child tasks, one decision, and five progress references to mapped
tasks; workstation and production retain their existing 14 and 12 workplan
progress events respectively. Every current foreign key into workplans/tasks
uses `ON UPDATE CASCADE`. The fail-closed batch hash is
`554c6cbe119e13738efc6e2836254ddae00ea870f1cb99f2b5603336160e308d`.
`RMGR-DEC-2026-003` is the directly actionable approval interface; no
identifier mutation has run. Evidence:
`docs/evidence/RMGR-WP-0005-batch-0004-railiance-cluster-readiness-2026-08-22.md`.
## Retire the interim rule
```task