Agent Scripting API returns 422 when routing +61 inbound on Sydney edge

Pushing a standard agent script assignment through /api/v2/interaction/interactions/{interactionId}/scripts on mypurecloud.com.au and the Sydney edge keeps throwing a 422 Unprocessable Entity. The payload includes a valid script_id and acma_compliance=true flag, but the response body just spits back {"error":"VALIDATION_FAILED","message":"Script template mismatch for region APAC-SYD"} while the US Virginia edge handles the exact same JSON without blinking. We’re on platform version 2023-09-20 with flow v3.1.2, and the +61 prefix triggers the mismatch right at the Set Script step, leaving the compliance queue doing jack all and the agent mic staying hot with no prompt while the Architect console just hangs on the step transition.