Brooklyn Nicholson 00694b935f perf(desktop): composer typing no longer re-renders ChatBar (imperative draft sync) ... The real composer state-engine fix. ChatBar subscribed to the full draft string (`useAuiState(s => s.composer.text)`), so every keystroke re-rendered the whole ~2k-line component even though the contentEditable DOM already owns the text. Replace that with: - an imperative composer-runtime subscription (useComposerRuntime().subscribe) that mirrors text into draftRef, repaints the editor ONLY on external changes (clear/restore/insert; the focused editor is the source otherwise), and drives the debounced per-session stash — all without a React render. This folds the old `[draft]` sync effect and the `[draft]` debounced-stash effect into one place keyed off the runtime, surviving core rebinds via the effect dep. - coarse edge selectors (hasText / isHelpHint / isSteerableText, plus isEmpty / hasHardNewline in useComposerMetrics) for the chrome, which only re-render when an edge actually flips. Net: typing within a line does zero ChatBar re-renders / style invalidations; work happens only on real edges. Behaviour-preserving — draftRef + editor are already kept current by every mutation path; verified by the composer DOM repro tests (enter-submit, IME composition, slash-nav) + text-guard.		2026-06-30 04:19:10 -05:00
..
bootstrap-installer	fix(desktop/windows): stop in-app update from cascading into a backend restart loop (#50381)	2026-06-21 13:10:32 -07:00
desktop	perf(desktop): composer typing no longer re-renders ChatBar (imperative draft sync)	2026-06-30 04:19:10 -05:00
shared	style(shared): apply workspace formatter to websocket helpers	2026-06-28 21:30:43 -05:00