Release Ceiling 1.2.0

[tsouth89]

Version bump to 1.2.0 across manifests + version.env, with the 1.2.0 changelog entry. No code changes beyond version strings; all feature work already merged and green on main.

Since 1.1.0

• Depletion ETA — Calm mode and the dashboard show "about ~42m left" instead of just flagging a running-low window (SOU-274, Concrete depletion ETA in Calm pace + dashboard (SOU-274) #64)
• statusline command — cache-only, prints remaining capacity for editor status bars without waking the app or hitting the network (SOU-271, Cache-only statusline command for editor status bars (SOU-271) #65)
• Per-project cost — 30-day spend split by project alongside model/effort (SOU-272, Per-project cost breakdown (SOU-272) #66)
• CSV export — export a provider's 30-day spend to Downloads from the charts view (SOU-273, In-app CSV export of spend (SOU-273) #67)
• Cursor activity card — activity-by-model share from local request logs (Cursor activity-by-model card from local tracking #61)

Release doctor passes. Tag v1.2.0 will be pushed after merge to trigger the signed Windows build.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	ceiling	3e0cd7c	Commit Preview URL Branch Preview URL	Jul 19 2026, 05:03 AM

[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: 26 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: CHILL

Plan: Pro

Run ID: ce66d00c-3f7c-40b7-a274-7f7c2c738d9a

📥 Commits

Reviewing files that changed from the base of the PR and between 8eb6f99 and 3e0cd7c.

⛔ Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock
• docs/images/ceiling-charts-detailed.png is excluded by !**/*.png

📒 Files selected for processing (6)

• CHANGELOG.md
• apps/desktop-tauri/package.json
• apps/desktop-tauri/src-tauri/Cargo.toml
• apps/desktop-tauri/src-tauri/tauri.conf.json
• rust/Cargo.toml
• version.env

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/1.2.0

---

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