diff --git a/workplans/WARDEN-WP-0027-credential-governance-lockdown.md b/workplans/WARDEN-WP-0027-credential-governance-lockdown.md
index 840f291..a111c31 100644
--- a/workplans/WARDEN-WP-0027-credential-governance-lockdown.md
+++ b/workplans/WARDEN-WP-0027-credential-governance-lockdown.md
@@ -222,6 +222,39 @@ test results, and infra acceptance. T02 remains `progress` until
 that owner gate is open; acceptance will permit preparation of a new scenario,
 not execution or reuse of the terminal one.
 
+**Owner gate CLOSED — accepted 2026-08-23, found 2026-08-28.**
+`railiance-platform` accepted the exact revision `0fae0904`. Recorded in their
+`RPF-WP-0017-attended-login-output-containment.md` (`status: finished`), which
+also records railiance-infra's independent approval at `186b030` and marks all
+five acceptance criteria met. The receipt digest was verified here rather than
+taken on trust: `docs/evidence/RAILIANCE-WP-0026-T01-ops-warden-receipt.json` at
+ops-warden `bc1966da` hashes to
+`d2ba444ed16989590325697e69d25283dc75a9432c29a72e627e80bf9fd987e4`, matching
+their record exactly.
+
+Note the identifier: the remediation interface recorded above as
+`RAILIANCE-WP-0026-T01` is `RPF-WP-0017-T01` in the owner's repo. Searching for
+the cited id finds an unrelated workplan, which is part of why this sat unnoticed.
+
+**Their acceptance is source acceptance only and authorizes no live OIDC or
+drill** — their words, and the boundary holds. So T02's state changes but its
+`Done when` does not: what was blocked was *preparing a new scenario*, and that
+is now permitted. The terminal NO-GO scenario and its receipts remain unusable.
+
+**Third instance of the same failure this session.** The acceptance existed for
+five days; no message reached ops-warden. Identically, `key-cape` accepted the
+WP-0033-T04 question on 2026-08-23 with no message, and nine unread messages
+were sitting on already-superseded threads. The `verified:` field added by
+WP-0033-T05 was built for exactly this and it works — what does not work is
+waiting for a counterparty to tell you. Re-checking a blocker means reading the
+owner's repository.
+
+**Remaining to close T02:** one attended production emergency seal/unseal drill,
+requiring a new scenario id, fresh owner receipts from platform/infra/master, a
+fully parameterized green preflight, and a new human GO. It is executed by the
+platform owner, never by a coding agent. That is an operator decision, not an
+agent one, so T02 stays `progress` and the decision is surfaced rather than taken.
+
 ## Task: Tamper-evident policy governance + reconcile
 
 ```task