RPF-WP-0015-T03: record E2 attempts blocked by aal1 login (no run, nothing changed)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 680842@bnt-lap001
Assistant-Session: 54eb9e8e-7d6b-4f0c-b7a6-a6db62075883

workplans/RPF-WP-0015-audit-core-custody-and-recovery-coordination.md

@@ -523,3 +523,15 @@ Post-reboot verify-chain/attest-chain (founder-run 21:30:55Z): intact, 508 event
 pre-reboot head c99426d8… unchanged (post-reboot-chain-head.json). Mutation freeze lifted.
 Still open before T03 can be marked done: the deferred synthetic E2 via the reviewed sender lane in E2 mode
 (railiance-platform dd003c9, owner round 8 pending).
+
+Deferred synthetic E2 (2026-10-14/15): the E2 mode was approved by all five owners
+in round 9 (contract 014627d6; railiance-platform 748fe6c: first send must be a fresh
+`accepted`, replay `duplicate`; the event stays in the append-only chain). Two E2
+receipts were issued (windows 22:31Z and 22:40Z) but no run started: the contained
+`openbao-platform-admin-login` returned `login_failed` (exit 10) at 22:35Z, 02:07Z and
+02:10Z (warden access-audit). The founder's KeyCape session showed `assurance aal1`
+(password without OTP), so the OpenBao admin OIDC login, which needs MFA, was refused
+and warden failed closed with self-revocation. Nothing was projected and audit-core was
+untouched. Next: sign out of KeyCape (or use a fresh private window), complete
+password+OTP (aal2), reissue a near E2 receipt and run the launcher once. T03 stays
+`wait` until that E2 evidence exists.