chore: use RMASTER-WP prefix for master workplans

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

View file

@ -1,7 +1,7 @@
#!/usr/bin/env python3
"""Validate rail.yaml, rapp.yaml, and reef.yaml family declarations.
RAILIANCE-WP-0021-T05.
RMASTER-WP-0021-T05.
Discovers rail-*, rapp-*, and reef-* repos under a root (default: the
parent of this repository), loads each declarations/<family>.yaml, and
@ -15,7 +15,7 @@ checks, in this order:
6. if --inventory is given, every live deployable belongs to exactly one rapp
This repo does not query a cluster. Live coverage consumes an inventory
file produced by an implementation repo (RAILIANCE-WP-0021-T06).
file produced by an implementation repo (RMASTER-WP-0021-T06).
Usage:
tools/validate-family-declarations.py