feat(cursor-review): bump opus model to 5

[claude]

Requested by Benjamin Lu · Slack thread

Description

Bumps the Anthropic pin in the cursor-review panel from claude-opus-4-8-thinking-max to claude-opus-5-thinking-max, and the judge_model default the same way, since judge_model was also pinned to the same Opus 4.8 tier.

Note on scope: the model is configured here, in Comfy-Org/github-workflows (.github/workflows/cursor-review.yml) — not in Comfy-Org/cloud. cloud's .github/workflows/ci-cursor-review.yml is only a thin, SHA-pinned caller into this repo's reusable workflow; it carries no model configuration of its own.

Files changed (5 occurrences, all in this repo)

• .github/workflows/cursor-review.yml — judge_model input default (line 56) and the Anthropic entry in the panel's model-pin array (line ~332), plus the rationale comment above the array.
• .github/cursor-review/README.md — the panel table's Anthropic row and the inputs table's judge_model default, both documentation mirrors of the same pin.
• .github/cursor-review/prompt-judge.md — an illustrative attribution-string example in the judge prompt that referenced the old model id.

No other behavior changes.

⚠️ ZDR eligibility — could not confirm, needs human verification before merge

This Anthropic pin exists specifically because it must be ZDR-eligible in Cursor's catalog (this panel reviews private-repo diffs — see the existing comment explaining why Fable 5 is excluded from the panel for exactly this reason). I could not confirm whether claude-opus-5-thinking-max (or Opus 5 generally) carries the same ZDR eligibility in Cursor's catalog:

• No CURSOR_API_KEY / cursor-agent CLI was available in the environment that made this change, so I could not query Cursor's live model catalog the way this workflow's own preflight step does at runtime.
• I attempted to verify via public sources (Cursor's docs, cursor.com/data-use, the Cursor announcement tweet, a mirror of that tweet, and the Cursor community forum) — every direct fetch returned HTTP 403. I was not able to directly read any primary source's actual content, only a search-engine-generated summary, which I'm not treating as verification.

Please confirm Opus 5's ZDR status against Cursor's live catalog/dashboard before merging. I've updated the rationale comment above the model-pin array in cursor-review.yml to say this plainly rather than assert it's confirmed. If Opus 5 turns out not to be ZDR-eligible in Cursor's catalog, this PR should not merge as-is — the Anthropic pin would need to stay on Opus 4.8 (or another ZDR-eligible tier) until that's resolved.

Separately, this workflow's own preflight step (Validate model pins against live catalog) will independently catch it if claude-opus-5-thinking-max is simply not present in Cursor's catalog at all (fails the run loudly, per the existing kimi-k2.5 precedent) — but that check does not verify ZDR status, only presence.

Rollout — no manual follow-up needed in cloud

cloud's .github/workflows/ci-cursor-review.yml caller is SHA-pinned to this repo's main. Per this repo's bump-cursor-review-callers.yml, once this PR merges and the floating major tag moves, the caller pin in cloud (and any other consumer repo) will be auto-bumped by that workflow — no manual follow-up PR is needed there.

---

Generated by Claude Code