docs(devlog): release-readiness note for the cursor-call integration

[lidge-jun]

Summary

Release-readiness note for the cursor-call integration campaign (#1993 / #1994 / #1995, merged as 4f72d6f75).

Records the five release gates run against the merged dev SHA rather than the pre-merge tip — a merge commit is a tree nobody has tested until it is tested — and recommends cutting 2.25.0 as a minor, because the externally observable behaviour of a failed turn changed.

Says two things plainly instead of burying them: the merges were owner-authorized admin merges with CI waived, which is owner authority and not compliance with MAINTAINERS.md:48-49; and publishing is not one command away, since scripts/release.ts waits for Cross-platform CI and Service lifecycle at the exact release SHA.

Carries the five open follow-ups, led by the one the campaign's own docs previously overstated: the Cursor tool-result image encoder is correct and does not reach production, because every Cursor model is in noVisionModels and the vision sidecar strips images before the adapter runs.

Verification

Docs-only change — no source, tests, or build inputs touched.

The gates this note records ran on ssh lidge at 4f72d6f7555013ab231de78233d2aa95bd1e439c in a worktree pinned to that SHA, with HEAD re-asserted before each:

bun x tsc --noEmit          exit 0
bun run privacy:scan        Privacy scan passed
bun run audit:high          No vulnerabilities found (root + gui)
bun run build:gui           built in 205ms
bun test --isolate tests    green

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed. (This PR is that update.)
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults. (Docs only; privacy:scan green at the recorded SHA.)

Summary by CodeRabbit

• Documentation
  • Added release-readiness guidance for the cursor-call integration.
  • Documented validation requirements, governance considerations, cross-platform support, and service lifecycle checks.
  • Recorded the current version status and recommendation for version 2.25.0.
  • Listed promotion prerequisites, follow-up items, and known limitations.

[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: c3c29af6-f480-492c-8a72-558383de3db6

📥 Commits

Reviewing files that changed from the base of the PR and between 4f72d6f and 45ae409.

📒 Files selected for processing (1)

• devlog/_plan/260818_cursor_call_integration/060_release_readiness.md

---

📝 Walkthrough

Walkthrough

The release-readiness note documents the recommended 2.25.0 release, merged-SHA validation, promotion prerequisites, version state, unresolved integration gaps, and issue disposition.

Changes

Cursor-call release readiness

Layer / File(s)	Summary
Release evidence and version decision devlog/_plan/260818_cursor_call_integration/060_release_readiness.md	Lines 1–81 record merged PR ancestry, validation gates, governance conditions, platform requirements, live versions, and the 2.25.0 recommendation.
Promotion prerequisites and sequence devlog/_plan/260818_cursor_call_integration/060_release_readiness.md	Lines 83–101 define an unexecuted dev-to-preview and dev-to-main promotion sequence using required workflows and scripts/release.ts.
Remaining gaps and issue disposition devlog/_plan/260818_cursor_call_integration/060_release_readiness.md	Lines 102–132 list unresolved integration gaps and summarize the status of related issues.

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

Suggested reviewers: ingwannu

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/cursor-call-release-note

---

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.}