# Windows uninstall reproduction

Build each commit in its own checkout after `vp i`:

```
cd apps/server
vp run build:exe --target win-x64
```

Commits:
- Base: [d1f7683d7e](https://github.com/pingdotgg/t3code/commit/d1f7683d7ecc244271748edc720693a9d7045f39)
- Head: [04e6643412](https://github.com/pingdotgg/t3code/commit/04e6643412e85b435c15b135df60d8df52942c7b)

On Windows Server 2025, install a clean standalone runtime:

```powershell
$env:T3CODE_HOME = 'C:\proof\install'
$env:T3CODE_INSTALL_BIN_DIR = 'C:\proof\bin'
irm https://t3.codes/install.ps1 | iex
```

For each side, copy that pristine install to `C:\proof\home`, replace only
`runtime\versions\0.1.10\t3.exe` with the executable built from that side's
commit, and run the attached `drive.ps1` with `-Side base|head -Sha <commit>`
on the logged-in desktop. Reset the home from the pristine install between sides.
The runtime layout and external dependencies come from standalone release 0.1.10.
No server, provider, database seed, or simulated platform is used.

The driver invokes the standalone executable with `uninstall --yes`, captures
both streams and its exit status, checks whether runtime remains, and records
the actual desktop at 500 ms intervals. It uses the absolute system cmd.exe
only for output redirection; the uninstall process inherits the deliberately
missing ComSpec. No CLI implementation is patched or mocked.

Observed base: false scheduling and uninstall-success messages, then unhandled
ENOENT, exit 1, runtime remains.
Observed head: scheduling failure and advice to delete runtime after the window
closes, no success message, exit 1, runtime remains.
