chore(release): bump to 0.7.2

[GeiserX]

Prepares v0.7.2, shipping the fixes merged since v0.7.1 as installable binaries (on the now-fixed release packaging → 3 uniquely-named assets):

• Correct container CPU% (fix(runtime): compute real container CPU% from two samples #49) — two-sample delta instead of a meaningless lifetime average; memory matches docker stats. Verified live (~101% for a pegged core).
• Low-severity correctness batch (fix: batch of low-severity correctness bugs #47) — regex hoisting, bufio pull-log cap, round() negative-rounding, surfaced credential-decrypt error, and Firebase-key redaction so secrets can't leak into persisted earnings.error.
• Dead-data cleanup (refactor: remove dead AppState.History and ServiceEarning.Delta #48) — dropped a 200-row query from every state read.

Bumps wails.json, both package.json, and the frontend lockfile to 0.7.2. The footer reads the version from package.json (Vite define), so the UI now shows v0.7.2. After merge, tagging v0.7.2 builds the 3-platform release.

[coderabbitai]

Warning

Review limit reached

@GeiserX, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 008ff576-8e87-4705-a07d-690cb1cdc492

📥 Commits

Reviewing files that changed from the base of the PR and between 18af150 and 30497bf.

⛔ Files ignored due to path filters (1)

• frontend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• frontend/package.json
• package.json
• wails.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/v0.7.2-release

---

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