diff --git a/workplans/AUDIT-WP-0013-cross-repo-sender-admission.md b/workplans/AUDIT-WP-0013-cross-repo-sender-admission.md
index e35c23a..d4276dd 100644
--- a/workplans/AUDIT-WP-0013-cross-repo-sender-admission.md
+++ b/workplans/AUDIT-WP-0013-cross-repo-sender-admission.md
@@ -44,15 +44,25 @@ AUDIT-IN-0006 / FLEX-WP-0031-T02. Unblock with the six exact source registration
 
 ```task
 id: AUDIT-WP-0013-T03
-status: wait
+status: done
 priority: high
-blocking_reason: "Gate House GH-WP-0004-T12 must supply the final decision and any canonical failure-path declaration shape."
-blocked_on: message-from:gate-house
 state_hub_task_id: "310e28d2-849d-549a-8c4b-d82c23ebad93"
 ```
 
 Message 715cf1f2-55dd-4d2d-9b7b-c5dffa0181e5 is a reading, expressly not a ruling. Keep restrictive released_uncommitted classes non-atomic/non-conformant under current text. Do not treat attributive completeness_trade as an exception. This blocks conformance/exception declaration, not custody preparation in T02. Require the decision ID, applicable text/schema revision, classes, failure condition and detection obligations before implementing a new field.
 
+**Resolved 2026-10-10 by GH-DEC-2026-024** (gate-house@0192273, message
+8b375579): the §9.6 failure-path release is refused. A load-bearing source
+gets no declared, detectable, direction-limited release, and §11 gets no
+declaration for one, so no new field is introduced. `completeness_trade` keeps
+its attributive-only meaning. That is already enforced:
+`SenderIdentity` rejects a `completeness_trade` on a load-bearing source
+(`audit_core/senders.py`,
+`tests/test_senders.py::test_a_load_bearing_source_cannot_be_given_a_completeness_trade`).
+A `released_uncommitted` class stays non-conformant. audit-core's
+evidence-source status is `no` (GH-DEC-2026-018, AUDIT-IN-0005). Registering the
+AUDIT-IN-0006 senders is still this repo's job, under T02/T05.
+
 ## Implement receiver process-instance accepted counts
 
 ```task