diff --git a/.custodian-brief.md b/.custodian-brief.md
index f6c368a..ee9e27c 100644
--- a/.custodian-brief.md
+++ b/.custodian-brief.md
@@ -2,7 +2,7 @@
 # Custodian Brief — secrets-engine
 
 **Domain:** infotech  
-**Last synced:** 2026-10-09 18:10 UTC  
+**Last synced:** 2026-10-10 08:20 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
@@ -35,14 +35,7 @@ Progress: 5/6 done  |  workplan_id: `9c9e5164-b2f5-5ea2-a557-5368d65e9fe0`
 
 **Open tasks:**
 - ! No standing engine credential  `d7bc8bdc`
-  *(wait: RPF-WP-0035-T02 awaits coordinated platform-tenant live registration, credential custody and scoped attended JWT role provisioning with native login/negative/revocation proof. The historical env-auth acceptance is not service-JWT adoption.)*
-
-### KeyCape secrets-engine-openbao consumer custody acceptance
-Progress: 3/4 done  |  workplan_id: `143de42b-b568-5070-add0-d5e71eabd436`
-
-**Open tasks:**
-- ! Attended consumer-copy delivery  `1c3afd34`
-  *(wait: All upstream objects are live: CCR-2026-0033 applied, KeyCape registration live (KEY-WP-0037), CCR-2026-0038 JWT mount keycape-services / role secrets-engine-openbao applied 2026-10-08 (railiance-platform 1b36e14). Probe input ~/.secrets-engine/keycape/openbao-jwt-login.yaml written 2026-10-09 with founder approval (mode 0600, parsed by the engine loader; allowed by CCR-2026-0038 as amended in railiance-platform 93a4bc2). Founder runs the attended probe-openbao command in docs/keycape-openbao-consumer-custody.md.)*
+  *(wait: Positive service-JWT login proof passed 2026-10-10 (SECRETS-WP-0012-T03, docs/evidence/2026-10-10-keycape-openbao-probe.json). Waits on railiance-platform closing RPF-WP-0035-T02 with the CCR-2026-0038 negative checks, then on routing live engine actions through service-jwt instead of bootstrap/env.)*
 
 ## Inbox Hygiene