Notes that are out of date (checked against cinny lotus on 2026-11-09):
Item 3, "reply currently misroutes": this is fixed. useTauriToastActions sends a thread toast's quick reply with its threadId (mx.sendMessage(roomId, threadId, …)), so it should post into the thread. Test it as a normal pass/fail.
Item 5, "until coalescing restored": this is restored (#17, closed). Toasts use the room:thread / lotus-invites tags, so rapid messages in the same room should replace each other rather than stack.
The rest of the checklist stands and still needs a Windows pass.
**Notes that are out of date** (checked against cinny `lotus` on 2026-11-09):
- **Item 3, "reply currently misroutes":** this is fixed. `useTauriToastActions` sends a thread toast's quick reply with its `threadId` (`mx.sendMessage(roomId, threadId, …)`), so it should post **into the thread**. Test it as a normal pass/fail.
- **Item 5, "until coalescing restored":** this is restored (#17, closed). Toasts use the `room:thread` / `lotus-invites` tags, so rapid messages in the same room should **replace** each other rather than stack.
The rest of the checklist stands and still needs a Windows pass.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Migrated from
LOTUS_TODO.mdon 2026-09-17 (the file is now reference-only).[desktop QA] Windows notification checklist (verify
0ddf86c6+ the above): (1) confirm the pre-fix symptom was focus-without-navigate; (2) message toast → click navigates to the message, quick-reply sends to the room; (3) thread toast → navigates, reply currently misroutes (until fixed above); (4) invite toast → navigates to invites; (5) rapid same-room messages → stacking until coalescing restored; (6) AUMID-missing/dev build → plain-notification fallback still shows; (7) web PWA unaffected.Notes that are out of date (checked against cinny
lotuson 2026-11-09):useTauriToastActionssends a thread toast's quick reply with itsthreadId(mx.sendMessage(roomId, threadId, …)), so it should post into the thread. Test it as a normal pass/fail.room:thread/lotus-invitestags, so rapid messages in the same room should replace each other rather than stack.The rest of the checklist stands and still needs a Windows pass.