chore(registrar): assign State Hub identifiers
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 1s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02b90-83bf-75c2-81c8-aa705414e4d4
This commit is contained in:
repo-manager 2026-08-23 12:51:40 +02:00
parent 2a8b5b7252
commit e8e71191d8
3 changed files with 10 additions and 4 deletions

View file

@ -12,6 +12,7 @@ updated: "2026-08-23"
related:
- RMASTER-WP-0020-T09
- RAPP-OPENBAO-WP-0002
state_hub_workstream_id: "6f8a6cbc-c076-5f0a-ade2-281a7ec71360"
---
# RAILIANCE-WP-0027 — OpenBao operator-only access
@ -27,6 +28,7 @@ destructive CoulombCore cleanup.
id: RAILIANCE-WP-0027-T01
status: done
priority: high
state_hub_task_id: "d84fb3fd-2166-58a0-81d9-2141ca55a67d"
```
The retained platform manifest now matches the canonical package posture:
@ -40,6 +42,7 @@ rollback artifact.
id: RAILIANCE-WP-0027-T02
status: done
priority: high
state_hub_task_id: "149fdec9-6735-514e-aad1-0c2daf72d27a"
```
`scripts/openbao-public-listener-transition.sh` pins the cluster UID, verifies
@ -53,6 +56,7 @@ It deletes only the Ingress and provides an exact rollback path.
id: RAILIANCE-WP-0027-T03
status: wait
priority: high
state_hub_task_id: "99f8b41f-e9db-579d-a6fb-b71337048afc"
```
Blocked on two facts: KeyCape and the OpenBao role must accept the exact