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

chore(consistency): sync task status from DB [auto]

Browse source 
Updated by fix-consistency on 2026-08-03:
  - RAILIANCE-WP-0020-T04: progress → wait
This commit is contained in:
custodian-sync 2026-08-03 20:35:53 +02:00
parent ceed081c8d
commit 9a1fcd9699
1 changed files with 8 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

9
workplans/RAILIANCE-WP-0020-openbao-migration-to-reef-railiance.md
View file

@ -90,7 +90,7 @@ was aligned to OpenBao 2.5.4, matching the source.
```task
id: RAILIANCE-WP-0020-T03
status: wait
status: done
priority: high
state_hub_task_id: "88671108-cf8c-4de6-b1ce-06e99b1c3d70"
```
@ -112,6 +112,13 @@ Shamir barrier. The remaining semantic and repeated restart/unseal proof needs
two of the three existing source shares through the attended custody ceremony;
no supported automated custody route exposes those shares.
Completed 2026-08-03. The operator supplied two rotated shares through hidden
prompts. Two restart/unseal cycles passed. The restored cluster became active
with the source cluster ID; inventory counts matched; the existing scoped Qonto
AppRole proved exact-path `read` and sibling `deny`; and declarative file audit
output was non-empty. Machine-readable evidence is in
`docs/evidence/openbao-isolated-restore-2026-08-03.json`.
## T04 - Restore authoritative state on railiance01
```task