# Issue 24002 runtime triage

Commit: d73fd1279a (origin/main, 2026-10-26).
Machine: fs-14, Linux x64.

Commands:
- git fetch origin main
- git worktree add /home/ubuntu/wt/issue-24002 origin/main
- vp install
- vp run dev (server 14538, web 6498, isolated .t3 state)
- vp run --filter @t3tools/desktop build (passed)
- node node_modules/electron/install.js (apps/desktop)
- headless-desktop with Electron --no-sandbox --disable-gpu, VITE_DEV_SERVER_URL=http://localhost:6498, T3CODE_PORT=14539, isolated T3CODE_HOME=.t3/desktop

Fixture: issue-24002.pdf, one page, generated with Helvetica text “PDF annotation reproduction”.

Attempt 1: Pair the web browser with the isolated server, open Files, select the PDF. It renders successfully in the file viewer. This surface has no preview-annotation control. Saved web screenshot.

Attempt 2: Build and start the actual Electron desktop app under Xvfb. Pair it to the separate server at port 14538 (distinct from its own desktop backend on 14539). Select the existing server project/thread, open Files, select issue-24002.pdf, click the globe action “Open file in preview browser”. Chromium renders the PDF in a local browser-preview tab for the connected environment. Click Annotate preview. Region is selected automatically. Drag from screen (1070,310) to (1390,380). A blue region appears around the heading and the note editor opens. Enter “Please revise this heading.” and click Attach. The annotation chip appears in the composer and the overlay closes. No provider turn was started.

Rendering: Electron 44.9.3 on Linux x64, Xvfb 1920x1080, app window 1100x780, light theme, default scaling, desktop UI driven by xdotool; whole-display PNG captures via ImageMagick import.

Files:
- desktop-pdf.png: PDF rendered in Files panel.
- desktop-region.png: selected region and annotation editor in browser preview.
- desktop-attached.png: annotation attached to the composer.

Existing fix: 6ba807810b2fa93ed5ef75fde82639f7007868e4, merged PR 24022, fixes Chromium PDF viewer swallowing annotation input. The PR explicitly references issue 24002 and includes earlier before/after recordings.

Limits: server is a separate paired process on the same VM, not a second physical machine. Agent-opened streamed browser tabs and macOS/Windows were not retested. Exact reporter opening route remains unspecified. No source edits, tests, or new PR needed.
