diff --git a/workplans/ACTIVITY-WP-0032-glas-profile-execution-contract.md b/workplans/ACTIVITY-WP-0032-glas-profile-execution-contract.md
index 21b7f26..9b60388 100644
--- a/workplans/ACTIVITY-WP-0032-glas-profile-execution-contract.md
+++ b/workplans/ACTIVITY-WP-0032-glas-profile-execution-contract.md
@@ -241,6 +241,17 @@ definition is proven end to end. Note that FI and Binky are unsuitable as the
 pilot while ACTIVITY-WP-0031-T01 is unresolved — their failures are currently
 provider-credential failures and would mask the result.
 
+Wait confirmed 2026-08-22 after T03/T04 source completion. The current
+rein-aharness claim consumer does not yet carry `harness_profile_ref` or
+`execution_refs` in `OpsRun.from_api`; its claim loop still calls the legacy
+`select_approach` matcher. Launching a profiled pilot now could silently ignore
+the authoritative selector, so Activity Core will not do that. Consumer handoff
+message `4ed3422a-b42c-4408-843c-f63c3e86cf3e` asks rein-aharness to invoke
+Glas for profiled rows with no legacy fallback and return the full
+`GatewayResult`. Glas was notified in thread message
+`6ac93cc9-6d5b-4039-aa89-81a025efef82`. Resume T05 only after that consumer
+slice is tested and deployed and a low-risk pilot is available.
+
 ## Acceptance
 
 - [x] Invocation shape decided and recorded as an ADR, with the boundary stated