Bug Description

When configuring the Kimi provider in Hermes, the auto-discovered model name k2p6 (shown in the dropdown/model list) does not match the actual model ID expected by the Moonshot API (kimi-k2.6). This causes all API requests to fail with a model-not-found error.

Steps to Reproduce

1. Go to model configuration for the Kimi provider.
2. Select k2p6 from the auto-discovered model list.
3. Try to send a message.
4. Actual: Connection fails / model not found error.
5. Workaround: Manually type kimi-k2.6 as the model name instead of using the dropdown.
6. Expected: API works correctly.

Root Cause

The model display name / auto-discovery list uses k2p6, but the API expects kimi-k2.6. The two are not mapped correctly for the Kimi provider.

Environment

• Hermes version: latest
• Provider: Kimi (Moonshot)
• Model: k2p6 (auto-discovered) vs kimi-k2.6 (manual)

Related

• Possibly related to fix(models): raise auto-correct cutoff to prevent version-variant false positives #13692 (model auto-correct logic), but this is specifically a display name ↔ API model ID mapping issue for the Kimi provider.