Prepare Ceiling 1.5.29

[tsouth89]

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

Supersedes 1.5.28, which was tagged but whose build was cancelled before it signed or uploaded anything, so that version produced no artifacts. The v1.5.28 tag stays as a marker — the repo's "Protect release tags" ruleset blocks deletion and non-fast-forward on v*, which is why the contents ship under a new number rather than by moving the tag.

What's in it

Cursor's on-demand spend reads as money on every surface (#260, reported in #191). 1.5.27 taught the Overview card to show dollars and stopped there. The taskbar tile picked the on-demand lane correctly then drew 62%; the hover flyout discarded any lane whose name matched on-demand before building rows, so the tile named a lane the panel beneath it refused to show; the floating bar had the same percentage-only defect; and Activity listed the row faithfully then headlined it 56% used. Uncapped on-demand now reports spend-to-date instead of going blank, and the tile picks the widest spelling that fits its 72–104px cell since the strip paints without clipping.

A monthly quota can raise a pace warning (#258). Follow-up to #256, which fixed the on-screen verdict but not the toast. Predictive warnings read only primary and secondary; monthly quotas arrive in the tertiary slot, so a month on course to run dry could never warn. Two slots sharing a cadence now collapse to one warning instead of clobbering each other's observation state.

Settings controls have reachable accessible names (#259, closes #215, contributed by @Vermitrude). Field rendered its label as a bare <span> with nothing tying it to the control; TextInput accepted no ariaLabel at all. Injection is scoped to nameable controls — a layout <div> is left alone, since aria-label is prohibited on the implicit generic role.

Validation

scripts\local-check.ps1 -All -Version 1.5.29 passed. Three warnings are expected pre-tag: no local v1.5.29 tag, no GitHub release yet, no local assets directory.

Two notes for the record:

• cli::tty_runner::tests::test_run_sends_script_through_pty is flaky in CI, not just locally — it failed on Associate Field's label with the control it wraps #259 at the output assertion (tty_runner.rs:717) and passed on a plain re-run with no code change. Locally it fails differently: %APPDATA%\npm contains shims named cmd/cmd.cmd that precede System32 on PATH, so which("cmd") resolves to a bash shim. Worth its own issue.
• Let a monthly quota raise a pace warning #258's two same-cadence review findings were already addressed in ec4282a3 before merge; Associate Field's label with the control it wraps #259's isHostElement finding was real and fixed on the branch.

After merge

Tag v1.5.29 to trigger the signed build and draft release. The draft still needs the manual installer and portable smoke test on a clean Windows profile before publishing, per docs/RELEASING.md.

[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	c3a9b65	Commit Preview URL Branch Preview URL	Aug 12 2026, 12:47 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: 14 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: b813554b-6373-4bbc-95d7-82af10beb065

📥 Commits

Reviewing files that changed from the base of the PR and between 09fdf11 and c3a9b65.

⛔ 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 2 issues:

1. Duplicate '### Fixed' heading fragments release notes

   CHANGELOG.md:14 · disposition: fix-if-quick · confidence: high · severity: low · quick win

   The new 1.5.29 section introduces a '### Fixed' at line 10 for the two new bullets and then a second '### Fixed' at line 14 for the carried-over Cursor on-demand bullets. Two sibling Fixed headings under one version breaks the single-heading convention used elsewhere and can confuse changelog parsers and auto-generated release notes.

   Prompt for AI agents

   In CHANGELOG.md around line 14: Merge both bullet groups under a single '### Fixed' heading for 1.5.29. Verify against the current code first; if no longer valid, skip with a brief reason. Keep the change minimal.

2. Version bump may be incomplete if rust/tauri.conf.json still carries a version

   version.env:1 · disposition: advisory · confidence: medium · severity: low · quick win

   All active manifests are bumped to 1.5.29 (apps/desktop-tauri/package.json, apps/desktop-tauri/src-tauri/Cargo.toml, rust/Cargo.toml, apps/desktop-tauri/src-tauri/tauri.conf.json, version.env). rust/tauri.conf.json is tracked but not in the diff; if it still contains a version field it will remain at 1.5.28 and diverge from the other manifests.

   Prompt for AI agents

   In version.env around line 1: Check rust/tauri.conf.json for a version field and bump it to 1.5.29 if present, or confirm it is intentionally frozen and document the exception. 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.}