Manual web proof, two commits, fresh isolated state.
Requires repository dependencies, Node, Python 3, npx agent-browser, ffmpeg, and Pillow for privacy redaction. No paid providers are used.

Place these scripts in an empty proof directory. Link that directory's node_modules to the current-main checkout's scripts/node_modules after vp i. The copied start-app.ts and shell.ts are the scenario runner startup helpers from current main; only the replay default is changed to multi-turn.

For each side, from its checkout run:
T3CODE_DEV_SEED=0 node <proof>/start-app.ts web <proof>/<side>-home 127.0.0.1 <port>
Then run:
python3 <proof>/manual-proof.py <side> <checkout> <port>
python3 <proof>/verify-runtime.py <proof>/<side>-home <generated-run-directory>/worktree-demo

The driver seeds a synthetic git repository and project through the CLI, then drives real UI sends. The remote transport waits long enough to stop preparation, or independently exits unsuccessfully after eight seconds. It revisits the thread, dismisses the actual thread error banner and notifications, and sends a correction and a repeated follow-up. Final raw screenshots must match byte-for-byte across a pause of at least 500 ms.

The verifier reads only each isolated instance's database and provider event logs. It counts successful session/new requests, and independently checks /proc cwd for live dev-replay-agent processes in the synthetic project checkout. It emits no absolute paths.

Published failed-path captures have error detail regions masked to remove synthetic absolute paths. redact.py contains the exact postprocessing, including video time windows for these recordings; review window timing before sharing any new run. Stop-path captures are unchanged. Raw driver logs can contain local paths and pairing credentials and are not for publication.

Commits:
base 5f85768394f417f5bd098ca7fe4fc41ef07a7cda
head 8ec82fdd22306ac2736e6717bfa68cb63ec50e51
