fix(cursor-review): bump dead kimi-k2.5 model id to kimi-k2.7-code

[mattmillerai]

ELI-5

Our PR-review bot asks four AI models to look at each change. One of them, Kimi, got renamed on Cursor's side, so it's been silently coming back blank — we've quietly been reviewing with three models instead of four. This swaps in the current Kimi model so all four vote again.

What changed

1. Panel matrix model kimi-k2.5 → kimi-k2.7-code in .github/workflows/cursor-review.yml.
2. Model table in .github/cursor-review/README.md updated to match.

Why

cursor-agent --model kimi-k2.5 now exits 1 with empty stdout and stderr Cannot use this model: kimi-k2.5. The run step's || true swallows the exit code, so extract-findings.py sees empty stdout and scores the cell empty — indistinguishable from "the model ran and found nothing." Both Kimi cells (adversarial + edge-case) drop out on every run and show up as Reviewers that did not contribute.

kimi-k2.7-code is the only Kimi model left in Cursor's catalog (verified live — it returns output normally). The other three pins — gpt-5.3-codex-xhigh, claude-opus-4-8-thinking-xhigh, gemini-3.1-pro — are all still current and unchanged.

Follow-up

A separate change will make an unknown/delisted model id fail loud (a catalog preflight, or scoring the cell error instead of empty) so the next time Cursor rotates its catalog it surfaces immediately instead of quietly degrading the panel.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 10 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 9cdb2a40-ef7f-4694-a38a-9f70f129dfe4

📥 Commits

Reviewing files that changed from the base of the PR and between b7b94bc and b0af3d5.

📒 Files selected for processing (2)

• .github/cursor-review/README.md
• .github/workflows/cursor-review.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch matt/bump-kimi-k2.7-code

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch matt/bump-kimi-k2.7-code

---

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