# Cross-environment pull request evidence

Run manual-server.mjs with arguments CHECKOUT SCRATCH_DIRECTORY SIDE on each commit separately. Install dependencies with vp i first. The helper creates fresh databases and a minimal git repository with the public T3 Code remote configured before registering it with both servers. No live database is copied.

1. Open the generated pairA URL in Chromium, using a 1280 by 800 CSS viewport and light appearance.
2. Open Settings → Environments. Install browser-driver.js as a browser-page evaluation before adding the second server.
3. Add the generated pairB URL. Wait for the Backend added notification, close Settings, and start recording.
4. Click Pull requests. Let both servers return open/all, authored, and reviewing lists (limit 99). The proxy delays only the second server's project shell over HTTP and WebSocket; real PR responses are forwarded unchanged.
5. Read window.__proof.read() for DOM row keys and observed RPC results. Confirm both all-list responses contain the same 99 URLs. Capture while the shell remains held.
6. Blur the focused input, take two screenshots 500 ms apart, and confirm pixel equality. Stop recording.
7. Stop the helper with SIGINT, which stops its own server children. Never upload generated state files: they contain pairing credentials.

Observed results are in observed-results.json. Before: 380 rendered rows, 190 unique URLs, Authored 198. After: 190 rendered rows, 190 unique URLs, Authored 99. Recordings show the navigation and list loading; stills show the settled list.
