[Bug]: Mark unread immediately resets on the active thread

[ojowwalker77]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

When the currently open thread is marked unread from the sidebar context menu, nothing changes visually.

1. Open a completed thread.
2. Right-click the active thread in the sidebar.
3. Select Mark unread.

Expected behavior

The thread remains visibly unread until it is opened again.

Actual behavior

The unread state is immediately cleared, so the action appears to do nothing.

Impact

Cosmetic issue

Version or commit

0.0.31-nightly.20260729.948 (e698796)

Environment

macOS Tahoe

Logs or stack traces

Screenshots, recordings, or supporting files

Screen.Recording.2026-07-29.at.18.26.21.mov

Workaround

No response

[t3dotgg]

Thanks for the report. We believe this is fixed by PR #5486 and PR #5579.

The old read-tracking effect reacted to lastVisitedAt, so Mark unread immediately triggered another mark-read update. The replacement tracks thread identity and completion time instead, which lets an active completed thread remain unread when the user marks it unread.

I'm closing this as fixed as part of an automated pass on all open issues. If the unread state still resets in a build that includes both PRs, please reply with the exact thread state and whether it resets before or after navigation, and we can reopen it.