Support Qwen / opencode-go Qwen Max model family in agent-model compatibility detection

[MumuTW]

Summary

oh-my-opencode doctor reports opencode-go/qwen3.7-max as an unknown model for planner/orchestrator agents, even though OpenCode can list and use the model successfully.

This is not a hard runtime failure, but it looks like a missing model-family mapping / prompt compatibility support item.

Environment

• OpenCode: 1.15.12
• oh-my-opencode / oh-my-openagent: 4.5.1
• Provider: OpenCode Go
• Model: opencode-go/qwen3.7-max

Config

{
  "agents": {
    "prometheus": {
      "model": "opencode-go/qwen3.7-max",
      "fallback_models": [
        { "model": "pioneer/claude-opus-4-8" }
      ]
    },
    "atlas": {
      "model": "opencode-go/qwen3.7-max",
      "fallback_models": [
        { "model": "pioneer/claude-opus-4-8" }
      ]
    }
  }
}

Doctor output

⚠ 1 issue found:

1. Configured models rely on compatibility fallback
   prometheus=opencode-go/qwen3.7-max (unknown), atlas=opencode-go/qwen3.7-max (unknown)
   Affects: prometheus, atlas

Expected behavior

opencode-go/qwen3.7-max should be recognized as a Qwen model family, or at least as a supported OpenCode Go Qwen model, so planner/orchestrator agents do not show an unknown compatibility warning.

Ideally, Prometheus / Atlas could use a Qwen-specific prompt variant or a documented generic Qwen compatibility path.

Actual behavior

The model is callable by OpenCode:

opencode models opencode-go

includes:

opencode-go/qwen3.7-max

But OMO doctor treats it as unknown and falls back to compatibility prompt handling.

Why this matters

Qwen Max is a strong long-context / planning model and fits planner/orchestrator roles such as Prometheus and Atlas. Users with OpenCode Go subscriptions may want to route these roles to Qwen Max intentionally, but the doctor warning makes the setup look degraded or unsupported.