Agent Scripting API 409 Conflict on Legal Hold Metadata

Just noticed that updating script metadata via the /api/v2/scripts/{scriptId} endpoint returns a 409 Conflict when attempting to tag recordings for legal discovery. The payload includes the correct legalHold flag and audit trail references, yet the response indicates a version mismatch despite using the latest ETag from the GET request.

This is blocking our bulk export jobs for digital channel transcripts in the London region. The API version is 2.0 and the environment is Genesys Cloud EU West. The conflict persists even after refreshing the script state immediately before the PUT request.