Manual proof drivers for issue 35934

Use separate checkouts of base 2e0bd97e86c700a59c9b5c35ea1b8bb85414161b and head c45c9da25644aa68ed151d039f3b6c59b40d6f43. Install each with vp i. Place these scripts together and make their node_modules resolve the checkout scripts/node_modules (the launcher uses Effect).

For each checkout, run with its own empty proof home and port:
T3CODE_DEV_SEED=0 node start-app.ts web <proof-home> 127.0.0.1 <port>
Run seed.py <checkout> <proof-home>. It writes cleanup settings, creates a tiny git project, starts a read-only showcase replay in review-readonly, and checks clean status and HEAD equality with main.
Stop the launcher by its terminal session (Ctrl+C). Restart the same command with T3_EVIDENCE_REUSE_HOME=1, preserving the synthetic state. The startup sweep is the reproduction.
Run capture.py <agent-browser-binary> <isolated-browser-session> <proof-home> <origin> <new-output-directory>. It pairs, opens the completed thread, records navigation to Maintenance, and captures the startup report. It requires two identical screenshots 500ms apart. Both commits use this same capture driver. Videos show inspection after the startup sweep, not the server process restart itself.
Run verify.py <checkout> <proof-home> for filesystem, git worktree registration, and read-only synthetic thread-state verification.

The showcase agent emits a canned reply mentioning edits; it does not write files. seed.py independently checks the worktree is clean and has no commits beyond main.

Environment: Linux web dev app, Chromium 151, 1280x800 viewport, light theme, fresh synthetic databases, no live user data. No source changes or commits were made.
