Desktop quit / backend ownership lock reproduction AI-assisted; verified with the tests and tools listed above. Build the desktop independently in each checkout with vp i and vp run build:desktop. Install Electron with node node_modules/electron/install.js in apps/desktop if needed. Requirements: Linux, headless-desktop, Python 3, sudo permission for ptrace, ffmpeg, xterm, xdotool, ImageMagick (import/compare). Place drive.py, tracer.py and dashboard.py together in an otherwise fresh scratch folder. Run separately and sequentially (replace placeholders): T3CODE_DEV_SEED=0 headless-desktop python3 /drive.py before T3CODE_DEV_SEED=0 headless-desktop python3 /drive.py after The driver launches the actual built Electron app and its actual managed backend, with a fresh isolated T3 home and XDG directories per run. Local is enabled by default. No copied database, provider turns, or project data are needed for this shutdown bug. The process/lock dashboard uses actual /proc process state and an independent SQLite BEGIN EXCLUSIVE attempt against the isolated server-owner.sqlite. Fault injection: PTRACE_SEIZE with PTRACE_O_TRACEEXIT on the managed backend. The debugger suppresses SIGTERM, then holds the kernel's pre-exit SIGKILL stop. This keeps process resources (including the ownership lock) and exit acknowledgement pending beyond the seven-second stop budget. No app source or built code is modified. The SIGKILL is the app's own escalation, not a simulated process handle. Timeline: quit via SIGTERM to the captured Electron main PID; inspect at 9 seconds; at about 10 seconds attempt a reopen using the same home; inspect at 14 seconds; at about 15 seconds release the debugger hold; close the intermediate reopen by its captured PID; at about 19 seconds reopen again and confirm a new backend owns the lock. Screenshots require two equal pixel captures 500 ms apart, so exact timestamps can slip slightly; each observed event and actual time is recorded in the dashboard. Recordings are continuous screen captures of the 1920x1080 Xvfb desktop, including the actual app on the left and process/lock observations on the right. The app closes its windows when quit begins on both sides; the main process is the differing state. Uploaded video copies redact the environment-name line during onboarding only. No updater installation is triggered; updater-specific UI remains unverified.