Evidence for the built-in No project MCP deletion guard.
Environment: Linux, two detached worktrees, real development servers run with vp run dev.
Each force setting uses a separate fresh home outside Git with T3CODE_DEV_SEED=0.
Driver seeds through HTTP MCP, never through SQL. SQL is read-only observation.
Full-access external MCP client credentials use the same production auth issuance as t3 thread CLI.
No provider subprocess was started; all seeded threads are idle, with one pinned and one archived.
Model metadata and absolute environment paths were removed from public MCP output.
The terminal is 1600x1000, dark background, same font and viewport in every recording.
Each log line is paced for readability. Videos are live X11 captures of xterm executing the driver.
The PNGs show final video frames; identical frames 500ms apart were confirmed before selection.

Re-run, with CHECKOUT, HOME, ORIGIN and OUTPUT chosen for each isolated side:
  T3CODE_DEV_SEED=0 vp run dev --home-dir HOME
  headless-desktop ./record.sh CHECKOUT HOME ORIGIN SIDE SHA true OUTPUT
Use false instead of true and a new server HOME to repeat without force enabled.
The driver requires the app dependencies installed by vp i, sqlite3, ffmpeg and xterm.
No tests are used as evidence. AI-assisted; verified with the tests and tools listed above.