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,6 +1,6 @@
---
id: "e274defb-28f2-571e-abcb-c17b57eab473"
name: "RAILIANCE-WP-0020 OpenBao Retention Closeout"
name: "RMASTER-WP-0020 OpenBao Retention Closeout"
type: activity-definition
version: "1.0"
enabled: true
@ -14,7 +14,7 @@ trigger:
timezone: Europe/Berlin
---
# RAILIANCE-WP-0020 OpenBao retention closeout
# RMASTER-WP-0020 OpenBao retention closeout
One-shot reactivation after the shortened 14-day reversible-retirement window.
It emits a claimable Activity Core ops run for the remaining cleanup task; it
@ -24,9 +24,9 @@ does not delete CoulombCore resources automatically.
id: reactivate-openbao-retention-closeout
condition: ""
action:
task_template: "Reactivate RAILIANCE-WP-0020 for OpenBao retention closeout"
description: "Move RAILIANCE-WP-0020 from backlog to active, run the railiance01 disaster-recovery drill, verify retained rollback requirements, and request fresh explicit approval before any destructive CoulombCore cleanup. Remaining task: RAILIANCE-WP-0020-T08."
task_template: "Reactivate RMASTER-WP-0020 for OpenBao retention closeout"
description: "Move RMASTER-WP-0020 from backlog to active, run the railiance01 disaster-recovery drill, verify retained rollback requirements, and request fresh explicit approval before any destructive CoulombCore cleanup. Remaining task: RMASTER-WP-0020-T08."
target_repo: railiance-master
priority: medium
labels: ["railiance", "openbao", "retention", "reactivation", "RAILIANCE-WP-0020-T08"]
labels: ["railiance", "openbao", "retention", "reactivation", "RMASTER-WP-0020-T08"]
```