Add Pin and Hide Alerts to the conversation menu

[damonjanis]

Right-click a direct message to Pin or Unpin it, or to Hide or Show Alerts. The row updates immediately. imsg-read then clicks Messages' own menu item and checks the pinning plist or ignoreAlertsFlag. An unreadable database is a failure, not success.

Hide Alerts also stops Blip's own toasts for that chat. The conversation stays in the list. The muted ids come from the last full chat list and are kept across shallow polls. Groups are refused, because these items address a handle.

This is 3 of 3, stacked on #120 and #121. Review the top commit. Do not merge this before those two.

Test plan:

• bun test
• python3 scripts/test-read-ui.py
• python3 bridge/mac/test_read.py
• python3 bridge/mac/test_read_sync.py
• python3 bridge/mac/test_read_verification.py

[nixfred]

Reviewed as part of the series; the full list is on #120. The #122-specific blocker is the focus order in click_conversation_item (select_chat before wake_messages). I will merge the series together once #120's fixes land.

[nixfred]

Thank you, @damonjanis. Pin and Hide Alerts in the conversation menu fit Blip well: they use Messages' own menu, add no config surface, and treat alertsOff as a cache of remote state. The review asked for four fixes before merge. I added them as two commits on top of yours (cb0ebfc, 57162ff), and your commits are unchanged:

1. Focus is captured before the conversation is selected. click_conversation_item ran select_chat() first and wake_messages() second. open imessage: can bring Messages forward on its own, so the "previous" app was sometimes Messages and focus was never handed back. conversation_action() now calls frontmost() before selecting, and every exit path restores that app: selection failure, a menu error, and failed verification.
2. Verification has three states, covers the whole cluster, and fails closed. chat_pinned used to search every string in the plist, compared only one handle, and returned False when nothing could be read. It now reads Messages' ordered pin list (pD.pP with pZ aliases, through a new ordered_pins() in imsg) and matches every id in the conversation cluster, plus guids and group ids, the same way imsg chats does. chat_muted reads ignoreAlertsFlag on every chat row in the cluster. These all count as unknown: an unreadable or unrecognised pin list, a missing chat, a malformed properties plist, or an unreadable chat.db. Unknown exits 75 for Unpin and Show Alerts as well as for Pin and Hide Alerts, so a failed "off" action can no longer report success. imsg chats now reports muted over the same cluster, so the list and the write define "muted" the same way. The four flags also refuse group ids on the Mac side.
3. Mute state survives shallow polls. buildThreads sets muted: false, and only applyPins ran on shallow output, so a muted chat showed as unmuted after the next shallow poll and the menu offered "Hide Alerts" again. The new applyAlertsOff() reapplies the cached set, the same way pins are reapplied.
4. Tests for the four mutations and the read side effect. The mocked tests in bridge/mac/test_read.py never open Messages. For Pin, Unpin, Hide and Show they check: the front app is captured before selection and restored last; a dormant menu wakes Messages; selection failure never clicks; verified, failed and unknown outcomes are handled for each flag; groups are refused. On the read side effect: opening a DM to pin or mute it used to read it silently. The unread count is now recorded first and put back with Mark as Unread while the chat is still selected, including when the action itself fails. A restore that cannot land is reported on stderr. Synthetic-SQLite tests cover a pin stored under a merged DM's other handle, an empty pin list as a verified unpin, unknown pin layouts, and malformed or missing mute state. Collector tests cover deep→shallow mute state and a write that cannot be verified. Before relying on these, I reverted fixes 1 and 2 in a scratch copy: the new tests failed against both.

Results (GitHub CI on 57162ff, merged with current main, all steps green):

bun test: 720 pass, 0 fail (721 tests, 25 files)
QML badge regression (scripts/test-read-ui.py): 6 passed, 0 failed
OTP desktop adapter, Mac tools py_compile: pass
bridge/mac Python suites (all 17 CI steps): OK, incl. test_read.py 32 tests
bash -n + shellcheck -S warning: pass

I also ran the same checks locally on the branch and on its merge with main. Everything passed except read-sync.test.ts "every four-click offline read/unread sequence…", which hit its 20 s budget on a heavily loaded machine. It fails the same way there on 325c823, before these commits, and passes in CI.

Overlaps: #83 touches the same collector and bridge paths, and #25 touches the same UI files. Whichever lands second will need a rebase.

nixfred will merge it. Thanks again for building this.

[nixfred]

Merged, thank you Damon. Pin and Hide Alerts are live on both my machines with the new Mac bridge. The four review fixes went in on top of your commits, as described above. I re-checked the focus order myself before merging: the front app is captured before the conversation is selected and handed back on every exit. With #120 and #121 that completes the series.