Chatpane Files

A notification reliability release. New-message notifications rested on a single code path, and several everyday cases fell through it silently.

Bug Fixes\n\n- Updates install correctly. The Install button no longer cancels the update\n before the signed download begins. Checking and installing remain separate,\n explicit actions.\n

• The first message after you read a conversation now notifies. Notifications were only raised for a thread that was already unread, so the next message in a chat you had just read arrived silently — the common case, and the reason notifications felt intermittent rather than broken.
• A message identical to the previous one notifies again. Repeating the same text in a chat you had read was suppressed as a duplicate of the earlier delivery. This also holds when the window reloads between the two.
• Group notifications show a picture again. They now use the sender's own face where it is known, falling back to the group's members drawn together — never one member's face standing in for another. Sender faces are also collected while Carrier sits in the background, so they are ready by the time a notification actually arrives.
• Notifications survive the background refresh. Arrivals and delivery receipts are no longer lost when Carrier reloads a stale Messenger view, and a message that lands mid-reload is still reported.
• No more spurious breakage warning. "A Messenger update may have broken part of Carrier" could appear purely because the window was in the background.

Internal

• Substantial hardening of the notification fallback: delivery-race reconciliation, duplicate suppression, and read-state tracking across reloads.
• Row-mutation attribution is measured from the previous scan rather than a fixed window, so a scan delayed by a throttled background timer no longer discards the arrival it was scheduled for.