Anyone know why the post /api/v2/ai/bots endpoint is throwing a 400 bad request when we try to push a bot definition from our appfoundry integration? we are using the latest rest api specs and the payload validates against the schema locally. the error message is vague, just saying ‘invalid input’ without pointing to the specific field. we have verified that the oauth token has the correct scope (ai:bot:write) and the organization id matches the context. this is happening consistently for our premium app clients who are trying to automate bot deployments via our sdk wrapper. the sdk version is 12.4.1. we tried stripping down the payload to just the name and description, which works, but adding the intents array causes the immediate failure. the intent ids are valid and exist in the target org. is there a known issue with batch intent association during bot creation or is this a rate limit masking as a 400? we are seeing this across multiple tenant environments so it seems like a platform side validation bug rather than a config error on our end. any insights from the api team or other developers hitting this wall would be appreciated.