PR #28368 runtime verification, Linux Boat VM main: 8b74a69019 (github/main) head: 958146763f04d78757b19530a6d870b80e91cc9f Build both revisions using: timeout 1800 vp run dist:desktop:artifact --platform linux --target dir --arch x64 --output-dir Both builds completed successfully. These are actual Electron packaged directory builds, not development-mode Electron. Stall setup: Isolated XDG_CONFIG_HOME=/tmp/pr28368-xdg-config and XDG_DATA_HOME=/tmp/pr28368-xdg-data. Created mimeapps.list and a named pipe mimeapps.list.new. The real /usr/bin/xdg-mime blocks while opening that pipe for its output. No replacement helper or mocked service. Launch the packaged t3code executable --no-sandbox --password-store=basic --remote-debugging-port=9223, with T3CODE_HOME=/tmp/pr28368-desktop-state and T3CODE_PORT=18368. MAIN: [02:06:09.136] INFO (#1): app ready Sun Nov 1 02:06:28 AM UTC 2026 PID PPID STAT ELAPSED COMMAND 28639 28540 Ss 00:19 /bin/sh /usr/bin/xdg-mime default com.t3tools.T3Code.desktop x-scheme-handler/t3code wait_for_partnerbackend_http=000 At the 19-second observation point, xdg-mime was blocked in wait_for_partner, no bootstrap log existed, and backend port 18368 refused connection. We terminated this known child to clean up the stalled baseline. HEAD, same named-pipe stall: [02:07:10.901] INFO (#1): app ready [02:07:15.921] WARN (#1): URL scheme handler registration failed [02:07:15.922] INFO (#1): bootstrap start [02:07:17.349] INFO (#202): backend ready [02:07:17.388] INFO (#202): main window created The child exited and HTTP GET / returned 200. HEAD, same actual helper also SIGSTOPed so it cannot act on SIGTERM: head-forcekill pid 32995 2026-11-01T02:08:08.527Z SIGSTOP actual child 33101 /bin/sh /usr/bin/xdg-mime default com.t3tools.T3Code.desktop x-scheme-handler/t3code PID STAT COMMAND [02:08:08.501] INFO (#1): app ready [02:08:14.527] WARN (#1): URL scheme handler registration failed [02:08:14.528] INFO (#1): bootstrap start [02:08:15.420] INFO (#205): backend ready [02:08:15.465] INFO (#205): main window created Repeated with the project already present: SIGSTOP child 37207 at 2026-11-01T02:10:57.158Z. [02:10:57.132] INFO (#1): app ready [02:11:03.159] WARN (#1): URL scheme handler registration failed [02:11:03.160] INFO (#1): bootstrap start [02:11:04.285] INFO (#205): backend ready [02:11:04.341] INFO (#205): main window created The stopped child no longer existed after startup recovery. The actual desktop client then completed a Codex gpt-6.1-sol turn reading startup-proof.txt and the current branch (see video). HEAD, normal registration, pipe removed: [02:08:23.463] INFO (#1): app ready [02:08:23.482] INFO (#1): registered URL scheme handler [02:08:23.483] INFO (#1): bootstrap start [02:08:24.534] INFO (#193): backend ready [02:08:24.587] INFO (#193): main window created $ XDG_CONFIG_HOME=/tmp/pr28368-xdg-config XDG_DATA_HOME=/tmp/pr28368-xdg-data xdg-mime query default x-scheme-handler/t3code com.t3tools.T3Code.desktop Real client/provider: Created pr28368-startup-check through the desktop client, with remote publication disabled. Codex gpt-6.1-sol ran git status and wrote startup-proof.txt. The on-disk file contains: linux desktop startup reached codex A second real turn after forced-kill recovery read that persisted file and reported branch main. Web dev neighboring behavior: Started vp run dev in background with explicit --home-dir /home/user/t3code/.t3 and seeding disabled. Actual dev-runner ports: serverPort=13773 webPort=5733. Drove /pair, Add project > New project (publication disabled), selected GPT-6.1-Sol and submitted a real turn through Google Chrome with repository Playwright dependencies. Response: web dev codex verified. this is a git repository on branch main, with a clean working tree. Blacksmith: vp test run apps/desktop/src/app/DesktopLinuxUrlHandler.test.ts: 16/16 passed. vp run check:changed HEAD^ on fetched exact PR head: format, lint, knip, affected typechecks and 16 tests passed. Limits: No AppImage mount/integrator path, other Linux desktop distributions, native mobile, macOS or Windows verification. The indefinite wait is induced by the isolated pipe; no claim about the original desktop-specific cause. No repository source changes were made.