fix(catalog): exclude uncallable OpenCode Go and Zen models

[chilung-cgu]

Closes #2330

Summary

• Excludes four uncallable OpenCode models from the generated catalog via ROUTED_MODEL_COMPATIBILITY_EXCLUSIONS:
  • opencode-go/grok-4.6 (injected via augment metadata but absent from authoritative live discovery and rejected with 401)
  • opencode-go/mimo-v2-omni (returned by stale live models, absent from current Go docs, rejected with 400)
  • opencode-go/mimo-v2-pro (returned by stale live models, absent from current Go docs, rejected with 400)
  • opencode-free/deepseek-v4-flash-free (returned by Zen live models, absent from current Zen free docs, rejected with 400)
• Preserves the existing opencode-go/hy3-preview exclusion and retains valid live/preview augmentations (e.g. Ox Alpha Free).

Verification

• bun test tests/codex-catalog.test.ts (185 pass, 0 fail, covers shouldExposeRoutedModel for all 4 excluded slugs and control slugs)
• bun test tests/provider-live-models.test.ts tests/codex-catalog-sync-hardening.test.ts (all pass)
• bun run typecheck (clean)
• bun run privacy:scan (passed)
• git diff --check (clean)

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

Review readiness checklist

This PR stays in draft until every box below is ticked. Tick all four boxes once the requirements are met:

• All CI tests are green on my local testing.

• I pushed my PR to the latest dev commit.

• I resolved all correct Codex and CodeRabbit findings.

• My PR is ready for review.

Summary by CodeRabbit

• Bug Fixes

  • Improved routed model compatibility filtering so unsupported models are no longer presented as compatible options.
  • Excluded mimo-v2-omni and mimo-v2-pro from routed compatibility options while continuing to expose supported models.

• Changes

  • Removed thinking-toggle controls for mimo-v2-omni and mimo-v2-pro.

• Tests

  • Added coverage confirming unsupported models are excluded and supported routed models remain available.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 986eb405-0929-4b41-99fc-3e5a001ec0e6

📥 Commits

Reviewing files that changed from the base of the PR and between e5c8306 and e2424f3.

📒 Files selected for processing (3)

• src/codex/catalog/parsing.ts
• src/providers/registry.ts
• tests/codex-catalog.test.ts

---

📝 Walkthrough

Walkthrough

The routed catalog excludes two unsupported OpenCode Go models. The provider registry also removes their thinking-toggle and reasoning-summary configuration. Tests verify the exclusions and confirm three other OpenCode models remain exposed.

Changes

OpenCode model compatibility

Layer / File(s)	Summary
Compatibility exclusions and validation src/codex/catalog/parsing.ts, tests/codex-catalog.test.ts	The catalog excludes opencode-go/mimo-v2-omni and opencode-go/mimo-v2-pro. Tests retain opencode-free/deepseek-v4-flash-free, opencode-go/grok-4.6, and opencode-go/glm-5.2 as exposed control models.
Reasoning-toggle configuration src/providers/registry.ts	The opencode-go thinking-toggle model list removes mimo-v2-omni and mimo-v2-pro. The derived effort, toggle, and reasoning-summary configuration no longer includes those models.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: ingwannu

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	src/codex/catalog/parsing.ts excludes only three of the four models in issue #2330; grok-4.6 remains exposed despite the issue reporting it as uncallable.	Exclude opencode-go/grok-4.6 or stop metadata augmentation from adding it when authoritative discovery omits it, and update tests/codex-catalog.test.ts.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Out of Scope Changes check	✅ Passed	The production exclusion and compatibility-filter test directly address issue #2330, with no unrelated code changes identified.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the primary catalog change: excluding unsupported OpenCode Go and Zen models.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

⏳ DRAFT

• review readiness checklist open (3/4 boxes ticked).

What to do

• Tick all four boxes in the PR description once you're done (currently 3/4).

Review readiness checklist

• ✅ All CI tests are green on my local testing.
• ⬜ I pushed my PR to the latest dev commit.
• ✅ I resolved all correct Codex and CodeRabbit findings.
• ✅ My PR is ready for review.

3/4 boxes ticked.

Automatic draft conversion failed. Please convert this pull request to a draft manually until every box above is ticked.

[lidge-jun]

grok-4.6 should be live

[lidge-jun]

리뷰 · 우선순위 51 / 80

설명: 이 PR은 이슈 #2330 이 말한, 고를 수는 있는데 실제로는 호출이 안 되는 OpenCode 모델을 카탈로그에서 빼는 일이다. 지금 CURRENT dev HEAD 는 ced9a85c5 이다. origin/dev 는 지난 시간과 같은 커밋이다. 마지막 코드는 여전히 #2346 Opus Fast 카탈로그이고, #2348/#2349 는 문서만 착지했다. package.json 은 2.27.0 이다. 현재 src/codex/catalog/parsing.ts 의 제외 집합에는 #82 의 opencode-go/hy3-preview 하나만 있다. 라이브 /models 가 보여 주거나 메타데이터가 덧붙인 줄은 그대로 픽커에 나온다. 이 변경은 그 집합에 세 줄을 더한다. opencode-go/mimo-v2-omni, opencode-go/mimo-v2-pro, opencode-free/deepseek-v4-flash-free. shouldExposeRoutedModel 이 이미 이 집합을 보므로 새 호출 경로를 만들지 않은 것이 맞다. 이슈 본문은 네 모델이었다. 네 번째 opencode-go/grok-4.6 는 PR 본문이 뺀다고 적었지만 디프에는 없다. 테스트는 오히려 이 모델이 산다고 잠근다. 메인테이너가 이 PR에 grok-4.6 should be live 라고 달았으니 빼지 않은 것은 그 지시와 맞다. 다만 본문과 Closes #2330 은 아직 네 모델을 한 번에 끝내는 말투다. grok-4.6 이 라이브 discovery 에 없으면 JAWCODE_CATALOG_AUGMENT_PROVIDERS 의 opencode-go 가 생성된 메타데이터로 다시 넣을 수 있다. 그 구멍은 이 PR이 막지 않는다. 드래프트이고 체크리스트는 0/4 다. 카탈로그 팁은 여전히 Ox Alpha x-preview-f-free + deepseek-v4-flash-vision-exp. Cursor #2334 CursorCredentialRouter 는 여전히 src/providers/cursor-pool.ts 모듈+테스트만 있고 어댑터에 연결되지 않았다. #2332 H2 풀은 discovery 전용, 종료 훅은 #2338, Run 은 자기 세션이다. #2320 overflow + #2342 size prior 는 이미 dev 다. #2188 사이드카+routed vision 도 이미 dev 다. 세 줄 제외는 작고 맞다. 본문과 이슈 닫기가 어긋나고 드래프트라서 51.

src/codex/catalog/parsing.ts 라인 149 ROUTED_MODEL_COMPATIBILITY_EXCLUSIONS - hy3만 있던 집합에 mimo 둘과 zen free 한 줄을 더한다. grok-4.6 은 넣지 않는다
PR 본문 Closes #2330 / grok-4.6 제외 주장 - 디프와 테스트와 반대다. 메인테이너 댓글은 살려 두라는 뜻이다
JAWCODE_CATALOG_AUGMENT_PROVIDERS opencode-go - grok-4.6 이 라이브에 없으면 메타데이터가 다시 넣을 수 있다. 이 PR은 augment 경로를 안 고친다
tests/codex-catalog.test.ts shouldExposeRoutedModel grok-4.6 true - 컨트롤로 맞다. glm-5.2 도 산다
체크리스트 0/4 / 드래프트 - CI와 본문 수정 전에 머지 칸을 열지 말 것

메인테이너의 판단이 필요한 지점

• grok-4.6 를 라이브로 두고 [Bug]: Catalog exposes four uncallable OpenCode models from augmentation or stale discovery #2330 을 세 모델만으로 닫을지, augment 금지까지 보고 닫을지
• 제외 집합을 계속 손으로 늘릴지, 업스트림 unsupported/unavailable 응답으로 자동 제외를 나중에 열지
• 이 드래프트를 체크리스트 채운 뒤에 머지할지

너의 추천
본문에서 grok-4.6 를 뺀다고 한 문장을 고친다. 세 줄 제외는 머지 후보다. grok-4.6 는 메인테이너 댓글대로 제외 집합에 넣지 않는다. Closes #2330 은 grok-4.6 가 지금 라이브 /models 에 있는지 한 번 더 본 뒤에 둔다. 라이브에 없고 augment 만으로 살아 있으면 이 이슈를 닫지 말고 augment 쪽을 따로 연다. #2334 미연결 라우터, #2361 센티널과 묶지 않는다. types.ts/config.ts 스플릿과 무관하다. 라벨은 그대로 둔다. 프리뷰 배포가 아니다. 체크리스트 4칸을 채운 뒤에 머지 검토한다.

이 댓글은 grok-bot이 작성했습니다

[lidge-jun]

Verification blocker on e5c83067 — opencode-free/deepseek-v4-flash-free

Reviewed and verified this head locally against origin/dev. The opencode-go half is right, but the Zen entry breaks an existing test.

$ bun test tests/provider-live-models.test.ts
(fail) live provider model discovery (authority + fallback)
       > opencode-free live discovery exposes big-pickle plus -free ids

  [
    "big-pickle",
-   "deepseek-v4-flash-free",
    "hy3-free",
    "mimo-v2.5-free",
    "north-mini-code-free",
  ]
  at tests/provider-live-models.test.ts:163

 7 pass, 1 fail

An independent review lane also probed GET https://opencode.ai/zen/v1/models today and found deepseek-v4-flash-free still advertised live. So excluding it hides a model the gateway is currently serving, which is a different situation from the opencode-go entries.

This is the same class of correction you already made yourself in this PR: d587a4b4 added opencode-go/grok-4.6 to the exclusion set and e5c83067 retracted it once grok-4.6 turned out to be live. The Zen entry needs the same treatment unless you have a terminal HTTP 400 captured against it.

What lands cleanly today

The two opencode-go exclusions (mimo-v2-omni, mimo-v2-pro) match the maintainer triage and the docs, and hy3-preview retention plus the augmentation contract (x-preview-f-free, deepseek-v4-flash-vision-exp) are correctly untouched.

To unblock

Either drop "opencode-free/deepseek-v4-flash-free" from ROUTED_MODEL_COMPATIBILITY_EXCLUSIONS, or keep it and update tests/provider-live-models.test.ts:163 with the captured 400 as evidence in a comment.

Two smaller follow-ups, neither blocking:

• src/providers/registry.ts:445 — OPENCODE_GO_THINKING_TOGGLE_MODELS still lists mimo-v2-omni and mimo-v2-pro, which can no longer be exposed. Worth pruning so the config doesn't contradict the exclusion set.
• src/codex/catalog/sync.ts filters the exclusion set a second time, independently of shouldExposeRoutedModel. A test through observeAndMergeCatalog would stop an excluded slug resurrecting from the persisted catalog.

The other four PRs in this batch (#2309, #2339, #2335, #2313) verified clean and are proceeding; this one is held only on the failing test above. Happy to merge as soon as it's green.