2 Commits

Include renames

Author	SHA1	Message	Date
Lotus CIandClaude Opus 5.5	3b6de2fdac	fix(desktop): hydrate Focus Assist on mount; thread-aware toast quick reply ... - useTauriFocusAssist queries the new `get_focus_assist` command on mount. The native poll's first reading is emitted during app setup, before the page listens, and the atom resets on every reload — so with Focus Assist already on, notifications leaked until the OS state flipped (cinny-desktop #15). - The toast quick reply takes the real `threadId` from the notification data and replies inside the thread (cinny-desktop #17). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA	2026-09-23 19:32:42 -04:00
jaredandClaude Opus 4.8	4509a2b6d3	feat(desktop): Tier B web side — toast actions, Focus Assist gate, folder DnD ... - P5-41/35 useTauriToastActions: native rich-toast click → navigate(path) (opens the room), quick reply → mx.sendMessage(roomId, m.text). The desktop bridge routes message notifications (tag=roomId) to show_rich_toast. - P5-56 useTauriFocusAssist + focusAssistActiveAtom: a native focus-assist-changed event drives the atom, OR'd into the existing quiet-hours gate in ClientNonUIFeatures so notifications+sounds suppress during Windows Focus Assist. - P5-48 recursive folder drag-drop: fileEntries.ts (sync webkitGetAsEntry capture → async batched readEntries traversal, path-prefixed names, 500-file cap) wired into useFileDrop, reusing the existing upload pipeline. +3 unit tests. Hooks no-op in the browser. Gates: tsc/eslint/prettier clean, build OK, 559 tests. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-01 10:01:10 -04:00