Real-server proof, no tests and no replay.
Use the same instructions in an installed worktree of each commit.
Base: 121f0cf014dcd6e94327588bf3f1f200a5f07ad7
Head: 6ea930929dd269920e6ce7f5ff8c69f49b34785d

1. Copy claude-proof-driver.ts into scripts/ in that worktree.
2. Make claude-capture.py executable. Its final exec runs the installed real Claude
   at /usr/local/bin/claude; adjust that public executable location if necessary.
3. Choose a new empty HOME_FOR_PROOF and an ABSOLUTE_WRAPPER path, then run:
   python3 prepare-proof.py "$HOME_FOR_PROOF" "$ABSOLUTE_WRAPPER"
4. Start the real server in its own shell:
   T3CODE_DEV_SEED=0 PROOF_ARGV_LOG="$ARGUMENT_CAPTURE" node scripts/dev-runner.ts dev:server --home-dir "$HOME_FOR_PROOF" --no-seed --port 16381
5. In a second shell in the worktree:
   node scripts/claude-proof-driver.ts "$HOME_FOR_PROOF"
6. Inspect ARGUMENT_CAPTURE. Cases in order: off, off-1m, on, unset.
   The driver saves each selection via t3_thread_configure, reads it back,
   sends a message and waits for the real provider run. All synthetic model
   calls receive API Error 400 from the gateway after the CLI has launched.
7. Stop the server and repeat on the other commit with a different fresh home.

The PNG files are rendered copies of the filtered server/CLI transcript,
not screenshots of the web UI. The wrapper records only four public flags
and passes all original arguments unchanged to the real Claude executable.
The registration/removal UI and persistence across a restart were not driven;
the proof starts directly with an empty custom-model catalog and saved choices.
