Desktop updater evidence driver Captured with GPT-6.1 Sol through the Codex harness. No repository changes or tests were used as evidence. The app under test is a packaged Linux x64 AppImage at desktop version 0.0.1, built separately from each source commit. Run vp i in each checkout first. Build with: node scripts/build-desktop-artifact.ts --platform linux --target AppImage --arch x64 --build-version 0.0.1 --mock-updates --mock-update-server-port 4141 --output-dir /-build The install and recovery cases use actual additional AppImages packaged from the head checkout at versions 0.0.2 and 0.0.3. Those were packaged with the same command, adding --skip-build and changing --build-version and --output-dir to release-02 and release-03. The already-built app code is retained; the Electron package version changes. These are synthetic release fixtures, not publicly released builds. Place drive.mjs, subreaper.py and the artifact directories together, then run one case at a time: headless-desktop python3 subreaper.py node drive.mjs Each run creates its own timestamped directory, fresh T3 home, provider config homes, XDG config/data/cache, and random CDP port. T3CODE_DEV_SEED=0 prevents live data seeding. No projects or real conversations are imported. The local HTTP server serves the generic feed and logs requests before responding. The real electron-updater handles checks, downloads, hash validation, and installation. download: startup offers 0.0.2; publish 0.0.3; call the same desktopBridge.downloadUpdate IPC used by the sidebar. install: startup offers 0.0.2; download and retain its real AppImage; publish 0.0.3; invoke desktopBridge.installUpdate('0.0.2'). Verify the hash of the replaced executable, then relaunch that executable and observe its currentVersion and next startup check. fallback: startup offers 0.0.2; make feed requests return HTTP 503 while artifact requests remain available; invoke downloadUpdate. The head logs a warning and downloads the known offer. withdrawn: startup offers 0.0.2; change the feed to the running 0.0.1 version; invoke downloadUpdate. The head returns completed:false and makes no artifact request. recovery: a synthetic corrupt database causes the real backend startup to fail and opens the native recovery window. After its 0.0.2 offer, publish 0.0.3 and click its actual update link via CDP DOM/Input. Verify the installed executable hash and relaunch it. The database deliberately remains corrupt, so successful update selection does not repair the unrelated fixture corruption. Download/fallback/withdrawn fixtures use small fake AppImage bodies with matching sha512, as in triage. They are never installed. Install/recovery fixtures use real packaged AppImages. Recordings are raw ffmpeg X11 captures without text overlays. Normal captures are 1200x850, light theme. Recovery captures show the top 640x180 of the real 640x480 recovery window, including the entire update action; the error output and filesystem footer are excluded for privacy. Stills are saved only after identical screenshot buffers 500ms apart. Uploaded transcripts combine timestamped feed/IPC/hash observations with real app updater and recovery log blocks; filesystem paths are redacted. After an install, the driver terminates any remaining app descendants and relaunches the replaced AppImage with the VM's --no-sandbox, --disable-gpu and CDP flags. Thus executable replacement and the next launch/check are demonstrated; unattended automatic relaunch without those flags is not claimed. subreaper.py makes orphaned installer children remain owned by the driver for cleanup. Only descendants spawned by this run are stopped. Each Xvfb/D-Bus session ends after its case.