Missing MODEL_MAPPING for new Kiro models

[jhong123]

Describe the bug

Kiro has added new experimental models, but they are not in MODEL_MAPPING, resulting in Unsupported model error.

Error: Unsupported model: minimax-m2.5. Supported models: claude-haiku-4-5, ...

To Reproduce

1. Configure kiro provider with model minimax-m2.5 (or deepseek-3.2, glm-5, minimax-m2.1, qwen3-coder-next)
2. Run opencode run -m kiro/minimax-m2.5 "hi"
3. See Unsupported model error

Expected behavior

These models should be recognized and routed to the Kiro API. I manually patched constants.js and confirmed all five models work correctly using the model ID directly as the mapping value.

Suggested change in constants.js:

// Add to MODEL_MAPPING:
'deepseek-3.2': 'deepseek-3.2',
'minimax-m2.5': 'minimax-m2.5',
'minimax-m2.1': 'minimax-m2.1',
'glm-5': 'glm-5',
'qwen3-coder-next': 'qwen3-coder-next',

Desktop:

• OS: macOS
• opencode: 1.3.16
• plugin: @zhafron/opencode-kiro-auth@1.8.1
• login: Sign in with AWS IAM Identity Center

---

[tickernelz]

This is partially fixed, but not complete yet.

Currently supported from this report:

• deepseek-3.2
• minimax-m2.5
• minimax-m2.1
• qwen3-coder-next

Still missing:

• glm-5

Keeping this open until glm-5 is added as well. The remaining specific model gap is also tracked in #90.