coulomb/railiance-master
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore: use RMASTER-WP prefix for master workplans

Browse source 
Rename RAILIANCE-WP-0017..0021 to RMASTER-WP-* so railiance-master
IDs no longer collide with railiance-platform's RAILIANCE-WP series.
Hub UUIDs are unchanged.
This commit is contained in:
codex 2026-08-14 14:29:18 +02:00
parent 3cc0dc31d6
commit 4864b7852d
15 changed files with 121 additions and 119 deletions
Download patch file Download diff file Expand all files Collapse all files

4
schemas/README.md
View file

@ -10,7 +10,7 @@ authority where the two disagree.
| `rail-*` | `declarations/rail.yaml` | `rail.schema.json` |
| `reef-*` | `declarations/reef.yaml` | `reef.schema.json` |
Written under `RAILIANCE-WP-0021` from the drift survey routed by
Written under `RMASTER-WP-0021` from the drift survey routed by
`railiance-platform` under its `RAILIANCE-WP-0015` (State Hub messages
`04c776c4`, `f88f938d`).
@ -180,6 +180,6 @@ with a `deployables` list of `{name, namespace?, kind?}` (or bare name
strings). Live names that no rapp claims are reported as wave-2 worklist
items, not suppressed.
The validator is `tools/validate-family-declarations.py` (RAILIANCE-WP-0021-T05).
The validator is `tools/validate-family-declarations.py` (RMASTER-WP-0021-T05).
It is runnable standalone now. Calling it from `fix-consistency` waits on
`the-custodian` admitting the family prefixes; that sequencing is not ours.