mistral/devstral-2512 incorrectly marked status = "deprecated" (Mistral API reports it active)

[DagMariusR]

Summary

providers/mistral/models/devstral-2512.toml sets status = "deprecated", but Mistral's own API reports this model as active (deprecation: null). Because downstream consumers such as OpenCode hide any model with status = "deprecated" from their model picker, mistral/devstral-2512 becomes unselectable even for accounts that have full, valid access to it.

Evidence

models.dev registry data (providers/mistral/models/devstral-2512.toml):

name = "Devstral 2"
family = "devstral"
release_date = "2025-12-09"
status = "deprecated"

Mistral live API — GET https://api.mistral.ai/v1/models, object for devstral-2512:

{
  "id": "devstral-2512",
  "owned_by": "mistralai",
  "name": "devstral-2512",
  "description": "Official devstral-2512 Mistral AI model",
  "max_context_length": 262144,
  "aliases": ["devstral-medium-latest", "devstral-latest", "mistral-code-agent-latest"],
  "deprecation": null,
  "deprecation_replacement_model": null,
  "type": "base"
}

Note that Mistral not only reports deprecation: null, but the model is aliased as devstral-latest and mistral-code-agent-latest — i.e. it is a current, recommended model, not a deprecated one.

Impact

OpenCode (which bundles/caches this registry) filters out every model with status = "deprecated" from both the /models picker and -m provider/model resolution. As a result mistral/devstral-2512 (and the aliases devstral-latest / devstral-medium-latest, which resolve to the same model) silently disappear from OpenCode despite the API key having valid access. The only workaround end users have is to define a separate openai-compatible provider pointing at https://api.mistral.ai/v1, bypassing the registry entirely.

Suggested fix

Remove the status = "deprecated" line from providers/mistral/models/devstral-2512.toml (and please double-check the rest of the devstral-* family under providers/mistral/models/, several of which appear to carry the same status while Mistral still serves them).

Verification steps

curl -s https://api.mistral.ai/v1/models \
  -H "Authorization: Bearer $MISTRAL_API_KEY" \
  | jq '.data[] | select(.id=="devstral-2512") | {id, deprecation, aliases}'

[github-actions]

I've gathered authoritative evidence and it directly contradicts the issue's premise. I will not edit any files.

No automated fix opened

The issue requests removing status = "deprecated" from providers/mistral/models/devstral-2512.toml, claiming Mistral reports the model as active. However, Mistral's own first-party documentation explicitly marks devstral-2512 (Devstral 2, v25.12) as deprecated, which means the existing registry data is already correct and the requested change would make it less accurate.

Evidence that the current status = "deprecated" is correct

1. Devstral 2 model card (https://docs.mistral.ai/models/model-cards/devstral-2-25-12) states verbatim:

   "Deprecation date 5/22/2026" — "Replacement: Mistral Medium 3.5"

2. Models Overview → Legacy/Deprecated section (https://docs.mistral.ai/models/overview) lists:

   Devstral 2 — v25.12 — API devstral-2512 — Deprecation 5/22/2026 — Retirement 7/31/2026 — Alternative: Mistral Medium 3.5

3. The current date is July 5, 2026, which falls inside the official deprecation window (deprecation 5/22/2026 → retirement 7/31/2026). The model is still served but is officially deprecated, which is exactly what status = "deprecated" represents.

Why the issue's evidence does not justify a change

The issue relies on the live API GET /v1/models returning "deprecation": null for devstral-2512. That API field conflicts with Mistral's official model card and models-overview documentation, both of which are more authoritative for lifecycle status and both confirm the deprecation. The fact that the model is aliased as devstral-latest / mistral-code-agent-latest does not mean it is non-deprecated — per a Spring AI changelog PR citing Mistral's docs, devstral-latest is itself being deprecated.

Review notes

This needs maintainer review rather than an automated edit because the requested correction is contradicted by the authoritative first-party source. A possible follow-up for a maintainer: Mistral's live API deprecation field returning null for a model the docs call deprecated may be worth tracking as a separate data-quality/observability question, but that is not a catalog-data fix I can make here. The existing status = "deprecated" on the other devstral-* family entries (devstral-medium-2507, devstral-small-2505, devstral-small-2507) is also consistent with Mistral's Legacy/Deprecated table, so I did not touch those either.