Bug: Console Go provider.only: tencent breaks routing for mimo-v2.5

Description Console Go (opencode-go) is applying a provider.only: tencent preference that blocks access to mimo-v2.5. The model was working perfectly until ~30 minutes ago, then started consistently failing with a 404 error.

[404] No allowed providers are available for the selected model. Providers serving xiaomi/mimo-v2.5-20260422: gmicloud, deepinfra, xiaomi, parasail, streamlake, novita, but your request's provider.only preference permits only: tencent.

Expected behavior mimo-v2.5 should route to any of the available upstream providers (gmicloud, deepinfra, xiaomi, parasail, streamlake, novita) as it did before.

Actual behavior The backend forces provider.only: tencent, which does not serve mimo-v2.5, causing a 404.

Affected models

opencode-go/mimo-v2.5
opencode/mimo-v2.5-free (also affected)
Environment

OpenCode version: 1.18.25
Platform: Windows
Provider: Console Go (opencode-go)
Model: mimo-v2.5
Additional notes

This is a server-side bug in the /zen/go/v1 endpoint. The /zen/v1 (Zen) endpoint works fine.
Client-side config overrides (e.g. setting provider.only in opencode.jsonc) are ignored because the backend preference takes precedence.
The issue appeared suddenly after a backend change ~30 min ago; no client configuration was modified.
Request Please fix provider routing for mimo-v2.5 in Console Go. The provider.only: tencent preference should not be applied to models that Tencent does not serve.