docs: record attended login containment evidence

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0290b-3241-74c3-b868-6049545af836

workplans/WARDEN-WP-0027-credential-governance-lockdown.md

@@ -189,6 +189,29 @@ matrix is in
 platform snapshot/driver and master quorum contracts remain required before the
 fully parameterized read-only preflight.
 
+**Live attempt terminal NO-GO 2026-08-23.** All owner receipts and the final
+read-only preflight became green, and the operator opened the exact bounded
+window with decision `449a697a-5303-4582-aa9e-b0bc8b35ab2d`. The platform
+driver stopped before seal when attended OIDC succeeded but the read-only agent
+home prevented token-helper persistence and the underlying client emitted the
+short-lived credential into captured output despite `-no-print`. The credential
+was immediately self-revoked. Independent metadata confirmed OpenBao remained
+initialized and unsealed with zero unseal progress; no seal, unseal, reboot,
+restore, policy, PVC, or workload mutation occurred. NO-GO decision
+`85724c0c-e70f-4e2f-a8c6-a9cb1ea6331b` supersedes and consumes the GO; the
+scenario and its receipts cannot be reused.
+
+The direct remediation interface is `RAILIANCE-WP-0026-T01`. Ops-warden commit
+`0fae0904ce8d8694338dd53a8a79abec5fec788d` replaces the persistent login-only
+handoff with a contained login-plus-reviewed-command envelope. It proves a
+private writable helper before OIDC, captures login/child/revocation stdout and
+stderr, fails closed on any output or persistence defect, self-revokes, and
+removes the helper. No live OIDC was used for verification. The value-safe
+owner receipt is
+`docs/evidence/RAILIANCE-WP-0026-T01-ops-warden-receipt.json`; a future drill
+requires owner acceptance, fresh receipts, a new scenario id, and a new human
+decision.
+
 ## Task: Tamper-evident policy governance + reconcile
 
 ```task