Prepare Ceiling 1.5.30

[btsouth]

Cuts 1.5.30. Version bumped in all five locations from VERSIONING.md, BUILD_NUMBER=132, Cargo.lock regenerated, and the Unreleased entries moved into a dated section.

What's in it

A second click on the tray icon hides the dashboard (#283, closes #280). Left-click always reopened the stats window. First click shows it, second click hides it. A Windows double-click is ignored so the window does not flash.

Grok banked resets show up (#282). Codex already had the chip. Grok's redeemable reset tokens now appear on Overview, provider detail, and the taskbar flyout. Redeem stays on grok.com.

Settings says why the taskbar widget is hidden (#264). The strip could vanish with no explanation. The Taskbar Usage group now reports shown, no free space, waiting for landmarks, or no enabled providers.

The taskbar widget takes a second lane when the usual one does not fit (#281, closes #261). Left-aligned taskbars (and Windhawk "Start always on left") made the Widgets-to-Start gap go negative, so the strip hid. If that lane has no room, it now uses the stretch between Start and the tray.

Charts no longer mix one account's usage into another (#277). A removed account could inherit the machine-wide cache. Each account now has its own tab and cache identity.

Provider detail no longer applies a stale refresh (#278). A slower request from the previous seat could paint over the one you just switched to.

Credential status is scoped to the selected provider (#279). Opening provider B could show a protected store and revoke action that belonged to provider A.

Validation

scripts\local-check.ps1 -All -Version 1.5.30 passed except the known local PTY failure:

• cli::tty_runner::tests::test_run_sends_script_through_pty fails locally because %APPDATA%\npm has a cmd shim that is not a valid Win32 application. Same environment issue noted on Prepare Ceiling 1.5.29 #263. 877 other shared Rust tests passed.

Tauri Rust tests (517), frontend tests (525), frontend build, clippy, fmt, store-submission prep, and release-doctor all passed.

Three release-doctor warnings are expected pre-tag: no local v1.5.30 tag, no GitHub release yet, no local assets directory.

Affected areas

• Tray panel
• Settings UI
• Config file / settings persistence
• CLI
• Provider-specific behavior
• Installer / release packaging
• Startup / background behavior
• Documentation
• Other:

UI / tray proof

• Visual proof was not practical; manual validation and explanation attached

The tray toggle was click-tested on a local debug build of main before this version bump. Release notes are the changelog section in this PR.

Notes for reviewers

This PR is the version bump and changelog only. The signed installer is built by tagging v1.5.30 after merge.

[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	3b27fbc	Commit Preview URL Branch Preview URL	Aug 13 2026, 02:38 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: 9 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 Plus

Run ID: 73b4e3dd-484d-4e7a-a135-da551723f7aa

📥 Commits

Reviewing files that changed from the base of the PR and between 2382525 and 3b27fbc.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 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

---

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

[github-actions]

Automated review

Found 1 issue:

1. rust/tauri.conf.json version not bumped alongside other manifests

   rust/Cargo.toml:3 · disposition: fix-if-quick · confidence: medium · severity: medium · quick win

   Diff bumps to 1.5.30 in apps/desktop-tauri/src-tauri/tauri.conf.json:4, apps/desktop-tauri/package.json:4, rust/Cargo.toml:3, apps/desktop-tauri/src-tauri/Cargo.toml:3 and version.env:1-2, but tracked file rust/tauri.conf.json is absent from the diff. If that file still carries a "version" field (as in prior releases) it will remain at 1.5.29, leaving two Tauri configs disagreeing and any tooling reading rust/tauri.conf.json reporting the old version.

   Prompt for AI agents

   In rust/Cargo.toml around line 3: Grep rust/tauri.conf.json for version; if present bump to 1.5.30 to match other manifests, or delete the field if the file is legacy and should inherit from Cargo.toml. Verify with grep -R "1.5.29" rust/tauri.conf.json apps/desktop-tauri/src-tauri/tauri.conf.json. Verify against the current code first; if no longer valid, skip with a brief reason. Keep the change minimal.

_{For coding agents: fix BLOCK and FIX IF QUICK findings now; everything else is tracked or informational; never exceed one CodeRev fix round per PR.}

_{Advisory. Findings generated by grok-subscription and muse-spark-1.2-contributor, each filtered through a 3-vote deepseek-v4-flash refutation panel with the changed code in evidence.}

[btsouth]

Skipped the rust/tauri.conf.json version note. That file is leftover CodexBar config at 0.1.0. VERSIONING.md lists the five active locations, and 1.5.29 did not touch this file either.