Correct WP-0024 lease selection contract

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa

workplans/RAILIANCE-WP-0024-audit-core-custody-and-recovery-coordination.md

@@ -126,6 +126,9 @@ therefore aborts unless the exact runtime prefix has one live handle whose
 issue time coheres with the ExternalSecret refresh. A live read-only check
 observed exactly one handle, 0.073 seconds of issue/refresh skew, and no secret
 values. It was not revoked.
+The procedure's responsibility table now uses the same metadata-only selection
+rule; it no longer claims lease metadata exposes or matches a mounted database
+username.
 
 ## T03 — Define the coordinated railiance01 reboot exercise
 
@@ -168,6 +171,15 @@ pending example intentionally fails. Creating the secret-bearing snapshot and
 its off-host copy remains an attended platform-custody action near the future
 reboot window; no snapshot was created in this implementation step.
 
+**Prior-evidence audit (2026-08-22):** rapp-postgres evidence from the
+2026-08-16 reboot proves the same PVC returned without re-bootstrap, original
+audit triples and the isolation fixture survived, platform-pg recovered, and
+audit-core readiness lagged by roughly 40 seconds. It remains a baseline, not
+T03 completion: that reboot was not driven by continuous synthetic accepts and
+did not measure the complete post-unseal ESO, audit-chain, and accepted-event
+recovery path required here. T03 therefore still needs one deliberate run, but
+does not need to rediscover the expected boot order.
+
 ## T04 — Route the contracts and approval gates
 
 ```task