Studio REST Proxy 403 on GDPR consent endpoint with valid Bearer token

The outbound compliance flow hits /api/v2/interactions/events/calls/consent and immediately throws a 403 Forbidden, even though the SNIPPET action is passing a freshly minted OAuth2 token with the interactions:read scope. Studio 2024.02.01 debug logs show the payload leaving the node, but the gateway drops it before the context variable even updates. UK data residency rules are locked down and the audit trail is doing jack all. It’s validating perfectly in Postman.