Repository navigation
v2.3.3
A 5-agent Opus review of the v2.3.2 bug-hunt session (correctness, SwiftUI lifecycle, security, test quality, docs/release consistency) found real problems in what that session shipped. This release fixes the ones worth a new binary for.
Fixed
- Refresh no longer clears a question you were mid-typing. v2.3.2's fix for draft leakage across digest navigation was too broad — it also fired when the app auto-selected a new digest after a refresh finished, wiping what you were writing. Only navigating to a different digest yourself now clears the composer.
- An abandoned @-mention target could silently redirect a reply to the wrong person. Picking someone from the
@picker, then abandoning it and pressing REPLY on an unrelated owed reply, could send to the abandoned target instead. - A priority rule that suppresses every message now asks for confirmation before saving. A rule with no contact, keyword, or service condition — just "suppress" — matches every message, including urgent ones, with no warning until now.
- Closed a narrow window where auto-send could be saved without the confirmation dialog being shown. The v2.3.2 fix for a spurious confirmation popup relied on scheduler timing that wasn't actually guaranteed.
- The About tab now reports the correct version and license. The v2.3.2 binary said it was v2.3.1 (
Info.plistwas never bumped) and still said "MIT License" instead of Apache 2.0. - The accessibility-audit fix from v2.3.2 was a no-op, replaced with one that actually works — a SwiftUI
.accessibilityHiddenmodifier can't affect an AppKit-owned window's accessibility state. - Removed the Homebrew install instructions from the README — the tap has no LLMessenger cask yet, so the command failed for anyone who tried it.
Verification
730 tests green (6 new since v2.3.2), zero static-analyzer warnings, red→green verified for every regression test added.
Full Changelog: v2.3.2...v2.3.3