Agent Assist translation stream activation failing with 422 on atomic POST

genesyscloud Platform SDK is absolutely mangling the atomic POST to /api/v2/agent-assist/translation-streams/activate and throwing a 422 whenever the Python payload stacks source language references, target matrices, and domain adaptation directives. The activation validation logic doesn’t accept the profanity filter pipeline alongside the language pair check, even though the concurrency limits and automatic dictionary loading triggers are totally fine. Slapping on callback handlers for the external localization DB just spits out {"error": "stream_init_failed", "details": "format_verification_mismatch"}.