🤖 fix: use double RAF in jumpToBottom for reliable scroll position

When switching workspaces, jumpToBottom was executing synchronously
before browser layout was complete. This caused scrolling to land
'almost at the bottom' instead of fully at the bottom.

The fix uses double requestAnimationFrame (matching performAutoScroll):
- First frame: allows DOM updates to complete
- Second frame: measures accurate scrollHeight after layout

setAutoScroll(true) is set immediately to prevent flicker of the
'jump to bottom' button.

Author: ammar-agent

src/browser/hooks/useAutoScroll.ts

@@ -38,10 +38,18 @@ export function useAutoScroll() {
   }, []); // No deps - ref ensures we always check current value
 
   const jumpToBottom = useCallback(() => {
-    if (contentRef.current) {
-      contentRef.current.scrollTop = contentRef.current.scrollHeight;
-      setAutoScroll(true);
-    }
+    if (!contentRef.current) return;
+
+    // Double RAF: First frame for DOM updates (async highlighting, image loads),
+    // second frame to scroll after layout is complete
+    requestAnimationFrame(() => {
+      requestAnimationFrame(() => {
+        if (contentRef.current) {
+          contentRef.current.scrollTop = contentRef.current.scrollHeight;
+        }
+      });
+    });
+    setAutoScroll(true);
   }, []);
 
   const handleScroll = useCallback((e: React.UIEvent<HTMLDivElement>) => {