Live Pi cold-resume proof. No replay agent, mocks, or unit tests.

Requirements: dependencies installed in the two checkouts, Pi 1.5.2 configured
with a working anthropic/claude-haiku-5-5 model, Python 3, ffmpeg, gnome-terminal,
and headless-desktop (or an equivalent Xvfb + D-Bus session).

Run once per checkout, with a NEW empty output directory each time:
  headless-desktop bash record-live.sh base /path/to/base-checkout /path/to/new/base-output /path/to/unpacked/scripts
  headless-desktop bash record-live.sh head /path/to/head-checkout /path/to/new/head-output /path/to/unpacked/scripts

The driver starts each checkout's real dev server with T3CODE_DEV_SEED=0 and
an explicit isolated home. It creates a synthetic project using the real T3 CLI,
starts Pi / Haiku 5.5 with ONE, stops the spawned server process group, restarts
with the same state, sends TWO, then repeats for THREE. All turns wait for the
real server's completed reply. The script terminates only its spawned group.

pi-probe.cjs transparently forwards T3's stdin and Pi's stdout, logging RPC
command types and sanitized launch arguments. probe.ts records actual extension
factory execution and Pi lifecycle events. Discovery processes using --no-session
are retained in raw probe.jsonl but excluded from the live display and counts.
Paths are reduced to basenames or <path>; no credentials or prompt bodies are logged.

live.mp4 is an unedited screen recording of the live terminal output, not a
reconstruction. Each summary lists the observed factory and switch counts.
Base PNG: two live screenshots taken over 500 ms apart were pixel-identical.
Head PNG: extracted from the recorded final summary after finding two frames
500 ms apart that were pixel-identical (the original still pair differed only
at the blinking terminal cursor). Both captures are 1306x758 in the same terminal.
