From 66b984460ba1689b0fee8af80d4599a8b02a272a Mon Sep 17 00:00:00 2001 From: codex Date: Sun, 23 Aug 2026 14:48:18 +0200 Subject: [PATCH] docs(RMASTER-WP-0020): record callback progress and NO-GO Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02b90-83bf-75c2-81c8-aa705414e4d4 --- ...ER-WP-0020-openbao-migration-to-reef-railiance.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/workplans/RMASTER-WP-0020-openbao-migration-to-reef-railiance.md b/workplans/RMASTER-WP-0020-openbao-migration-to-reef-railiance.md index bde569b..845004d 100644 --- a/workplans/RMASTER-WP-0020-openbao-migration-to-reef-railiance.md +++ b/workplans/RMASTER-WP-0020-openbao-migration-to-reef-railiance.md @@ -340,6 +340,18 @@ one value-safe attended MFA login. The KeyCape request is State Hub message `5e56b413-d8ec-4718-b432-2debc40498ca`. None of this authorizes or advances T08 destructive cleanup. +2026-08-23 callback progress: Net Kingdom revision `61aeafe` and registered +`NK-WP-0032` add the exact loopback callback to owner source. The Railiance01 +KeyCape client was patched and restarted, and value-safe verification proved +the exact redirect plus OIDC discovery live. Railiance Platform revision +`d18649f` adds a silent, tested owner command for the governed role update. +Its first attended execution failed closed before child handoff and did not +change OpenBao; Warden could not confirm self-revocation. Platform revision +`7f71dff` records that terminal NO-GO, and ops-warden review is requested in +State Hub message `755408d8-2749-43a3-9f2b-8df83bda87af`. T09 remains +`progress`: the private path is healthy and the public Ingress remains present, +but the OpenBao role callback and attended loopback login are not yet proven. + ## Safety constraints - Never initialize or overwrite either OpenBao instance without verified