feat(aws-bedrock-mantle/minimax.minimax-m2): add new models [bot]

[models-bot]

Auto-generated by model-addition-agent for aws-bedrock-mantle/minimax.minimax-m2.

---

Note

Low Risk
Config-only addition with no runtime or auth changes; the stub may need follow-up if consumers expect full model metadata like the aws-bedrock entry.

Overview
Adds a new provider catalog entry at providers/aws-bedrock-mantle/minimax.minimax-m2.yaml for minimax.minimax-m2, registering 14 AWS regions under costs and setting mode: unknown.

This is a minimal auto-generated stub (no limits, pricing fields, or status) alongside the fuller aws-bedrock definition for the same model id.

^{Reviewed by Cursor Bugbot for commit 268e3c7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 268e3c7. Configure here.}

[cursor]

Region list copied from wrong model variant

Medium Severity

The region list in this minimax.minimax-m2 config contains 13 regions that exactly match aws-bedrock/minimax.minimax-m2.1.yaml, not the 10 regions in aws-bedrock/minimax.minimax-m2.yaml. Specifically, eu-north-1, eu-central-1, and ap-southeast-3 are present in the m2.1 model but absent from the m2 model. This suggests the auto-generation bot used the wrong reference model when populating regions.

 

^{Reviewed by Cursor Bugbot for commit 268e3c7. Configure here.}