feat(mistral-ai): update model YAMLs [bot]

[models-bot]

Auto-generated by poc-agent for provider mistral-ai.

---

Note

Low Risk
Metadata-only YAML change (deprecation flag and cost formatting); no runtime logic or security impact.

Overview
Updates mistral-medium-c21211-r0-75 metadata: marks the model as deprecated via isDeprecated: true, and rewrites output token pricing fields to scientific notation (2e-6 / 1e-6) to match the existing input cost style—values are unchanged from 0.000002 and 0.000001.

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

[github-actions]

/test-models

[harshiv-26]

Gateway test results

• Total: 1
• Passed: 0
• Failed: 0
• Validation failed: 0
• Errored: 0
• Skipped: 1
• Success rate: 0.0%

Provider	Model	Scenarios
mistral-ai	mistral-medium-c21211-r0-75	skipped: skip-check

Skipped (1)

mistral-ai/mistral-medium-c21211-r0-75 — skip-check (skipped)

Skip reason

deprecated or retired model

[cursor]

Cursor Bugbot has reviewed your changes using default effort 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 74ea376. Configure here.}

[cursor]

Conflicting lifecycle metadata fields

Medium Severity

This change sets isDeprecated: true while status remains active. Those fields describe the same lifecycle in opposite ways, so unified JSON and downstream tooling may treat the model as both fully supported and deprecated depending on which field they read.

Additional Locations (1)

• providers/mistral-ai/mistral-medium-c21211-r0-75.yaml#L29-L30

 

^{Reviewed by Cursor Bugbot for commit 74ea376. Configure here.}