chore(main): release 0.5.62

[bhekanik]

🤖 I have created a release beep boop

0.5.62 (2026-06-11)

Features

• issue a safety override token in the blocked-send error (abe45ed)
• per-action destructive scopes for agent profiles (1577177)
• persist mutation job history across daemon restarts (02d5b43)
• reply to the Reply-To address when the sender set one (af02b7c)
• surface scheduled sends lost to a crash mid-flush (d3157b4)
• tell users when a mutation's undo could not be recorded (be880f5)

Bug Fixes

• detach sync on timeout instead of cancelling mid-flight (67c1329)
• signal clients to resync when their event stream lags (eae6756)
• stop silently dating/attributing mail to wrong values (f70b52d)
• web: handle SyncError, ReminderTriggered, and reconciliation events (21528ba)

Refactoring

• classify every IPC request exhaustively for safety policy (83c5a80)
• consolidate the parse+schema+build query idiom (9ba92e1)
• log best-effort cleanup failures instead of swallowing them (72e2365)
• web: guard RightRail attachment payload instead of casting (21ce202)

---

This PR was generated with Release Please. See documentation.

---

Summary by cubic

Release 0.5.62 improves safety controls and sync reliability. Adds override and scope controls, persists job history, respects Reply-To, and surfaces failed scheduled sends and undo gaps.

• New Features

  • Safety override token on blocked send; per-action destructive scopes for agent profiles.
  • Persist mutation job history across daemon restarts.
  • Respect Reply-To when replying.
  • Surface scheduled sends lost during crash; notify when undo recording fails.

• Bug Fixes

  • Detach sync on timeout and resync clients when event streams lag.
  • Correct mail date and sender attribution.
  • Web: handle SyncError, ReminderTriggered, and reconciliation events.

^{Written for commit 526b905. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
mxr-mail	Ready	Preview, Comment	Jun 11, 2026 12:36am

[coderabbitai]

Warning

Review limit reached

@bhekanik, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 7 minutes and 50 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 020930d3-6f0d-487b-b8af-c9e81fdfa62d

📥 Commits

Reviewing files that changed from the base of the PR and between dec375f and 526b905.

📒 Files selected for processing (3)

• .release-please-manifest.json
• CHANGELOG.md
• Cargo.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main

---

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 and usage tips.}

[cubic-dev-ai]

No issues found across 3 files

_{Re-trigger cubic}