4 Commits

Include renames

Author	SHA1	Message	Date
Lotus CIandClaude Opus 5.5	a8db61f79f	fix(threads): viewing a room no longer marks threads you follow read (#217) ... markAsRead ran on every room visit (timeline at the bottom and focused) and sent a threaded receipt for every unread thread, so a reply in a thread you started or replied in lost its unread badge the moment you glanced at the room, without opening the thread. Reads from just viewing the timeline are now "passive": - threads you follow (started, replied in, or were mentioned in) stay unread until their panel is opened; other threads are still cleared so they don't keep the room dot lit forever; - while a followed thread has an unread reply, the main receipt is scoped to the main timeline instead of unthreaded, because an unthreaded receipt also reads every older thread reply (the next main message would clear the thread anyway). The check also asks whether the latest reply is read, since the thread's count lags when the reply and a main message share a sync; - the thread open in the panel is skipped, as the panel sends its own receipt (was two identical receipts per reply). Explicit "mark as read" (room menu, Escape, bulk actions) still clears everything. Unit tests for each rule plus a local-homeserver e2e that checks the server's per-thread count survives a reply + newer main message. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA	2026-09-26 19:31:00 -04:00
jaredandClaude Opus 4.8	85ac8de5d9	style: apply prettier across fork files ... check:prettier was not part of my gate routine, so formatting drift accumulated across the session's touched files (and a few older ones). Run prettier --write to bring the repo back to 'All matched files use Prettier code style!'. Formatting only — no logic changes. tsc/tests/build all green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-11 13:52:36 -04:00
jaredandClaude Opus 4.8	f12175e76f	fix(unread): stop stuck/resurrecting read indicators ... handleReceipt recomputed unread from getUnreadNotificationCount, which is server-computed and stale on the synchronous synthetic receipt echo (the SDK only zeroes it immediately when the last event is our own message). Reading someone else's message therefore PUT the stale non-zero count back -> dot stuck or resurrected on the ack-sync ordering race. Restore upstream cinny's optimistic DELETE on our own receipt; the UnreadNotifications listener re-asserts the accurate badge on the server ack. Also collapse a {total:0,highlight:0} PUT to a DELETE in the reducer (a present map entry lights the dot via hasUnread=!!unread, so phantom {0,0} PUTs from the UnreadNotifications listener left stuck dots). Mark-as-Unread (MSC2867): clear the flag directly in markAsRead (opening an already-read room sends no receipt, so the receipt-driven auto-clear never fired), and gate the receipt auto-clear to main/unthreaded receipts so reading one thread no longer wipes the whole-room flag. Tests: 700/700 pass; typecheck + prod build clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-03 22:07:21 -04:00
jaredandClaude Opus 4.8	abd0753148	fix(notifications): safe thread receipts on mark-read (fixes read-receipt regression) ... The prior thread-receipt change (8192da5a) broke read receipts globally. Exact cause: markAsRead used `thread.lastReply() ?? thread.rootEvent`. When a thread's replies weren't loaded (lastReply() null — common on room open), it sent a receipt for the thread ROOT. Since roots are "in the main timeline", threadIdForReceipt() makes that a MAIN receipt at an old event; when the root isn't in the loaded timeline the SDK's backward-guard falls back to timestamp and applies it, moving the main read receipt onto an event we don't have, so getEventReadUpTo() returns null and roomHaveUnread() reports the room unread — re-broken on every mark-read, amplified by the bulk mark-all-orphan-rooms-read callers. Fix: main unthreaded receipt unchanged; the thread loop now sends a threaded receipt ONLY for a genuine loaded thread reply (thread.lastReply()), never the root — if replies aren't loaded, skip. New notifications.test.ts locks the regression (null lastReply → no root receipt) + the main/threaded/no-op cases. Gates: tsc/eslint/prettier clean, build OK, 672 tests (7 new). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-02 17:09:28 -04:00