[laneysmith]

Context

Muted conversations should not trigger the sidebar's floating unread notification.

Problem

Muted channels can retain invisible unread markers after their visible dots are suppressed. The scroll indicator still counts those markers, leaving a misleading “1 unread” notification.

Solution

Exclude confirmed-muted destinations from the scroll indicator's count and avatar previews, including DMs, Solo chats, mentions, manual unread and thread replies. Keep their unread state intact so unmuting restores the indicators.

Test Steps

1. Run this branch locally with bin/just desktop and use your configured Buzz account.
2. Mute an unread conversation and scroll it outside the sidebar viewport. It should contribute nothing to the floating unread count or avatar previews.
3. Unmute it. Its unread indicator should return without requiring a new message.

Automated validation passed: 15,978 unit tests and 14 sidebar browser checks across Chromium and WebKit. A separate browser reproduction confirms the baseline retains “1 unread” after muting the only unread DM and this branch removes it. Native app and human acceptance remain pending.

Videos and Screenshots

Same synthetic browser fixture and 1440 × 500 viewport; before is the base commit and after is this branch.

Before	After

[salman1993]

🤖 Reviewed by sol, Salman's AI agent, on his behalf at 7d7fc5310755c7e38d145a8956a2f93db8e00908.

No blocking findings. Confirmed mute state excludes both unread and thread markers before the sidebar derives counts, avatar previews, and reveal targets. The attribute observer handles mute/unmute changes without requiring another message, and the unread stores remain untouched.

Validation:

• All 14 sidebar browser checks passed across Chromium and WebKit.
• The two sidebar test files plus CommunityPicker passed on a focused rerun: 72 tests.
• Removing the mute filter made five regression cases fail; restoring it returned all 14 SidebarUnread tests to green. The working tree is clean.
• Full Vitest: 15,977 passed, 21 skipped, one failure in the unchanged CommunityPicker.test.tsx:434 right-click focus assertion. That entire file passed on rerun. Its test does not render the changed components, so I do not consider it a blocker for this fix.
• Required CI and DCO are green at this head.

Native app and human acceptance remain pending, as documented in the PR. This review does not attest those checks.