# Android diff navigation proof fixture

Run each app commit from its own checkout with dependencies installed and a fresh T3 home. Use a pooled Pixel 9, Android API 36, portrait 1080 × 2424, light theme.

The upstream GitHub responses are synthetic: two changed files and a current published inline discussion on `src/first.ts:3`. The server, RPC, mobile application, native diff renderer and navigation stack are real and unmodified. No real forge writes or paid agent turns occur.

1. Set `PROOF_ROOT` to an empty scratch directory. Run `node fixture.mjs` to serve the synthetic upstream responses on its Unix socket.
2. Create an isolated `GH_CONFIG_DIR/config.yml` with `http_unix_socket: <PROOF_ROOT>/forge.sock`. Start each backend with this isolated `GH_CONFIG_DIR`, `GH_TOKEN=synthetic-fixture`, `T3CODE_DEV_SEED=0` and `T3CODE_AUTO_BOOTSTRAP_PROJECT_FROM_CWD=0`.
3. Start `node scripts/dev-runner.ts dev:server --home-dir <home> --no-seed --port <port> --host 0.0.0.0`. Start Metro from the matching checkout, serving the device-reachable address. Install with `vp run mobile:install android --session <session> --metro <metro-url>` and pair with the repository's mobile pairing helper.
4. From the matching checkout run `python3 seed.py <home> <port> <synthetic-workspace>`. Use the same synthetic workspace on both backends; no existing database is copied.
5. Once the app has loaded and paired, run `python3 drive.py <before|after> <home> <session> <new-output-directory>`.

The driver opens Overview, scrolls its first-file row above the floating toolbar, records opening it, long-presses line 1, opens the published discussion, taps View file diff, picks the second file from Changed files, returns through Discussion, and opens Diff options. The native diff content has no accessibility nodes, so the long-press and discussion tap use positions checked against the screenshot. Every retained still is verified against an identical screenshot taken at least 500 ms apart.

The base should clear the earlier selection and omit Copy line; the head should preserve the original first-file selection and Copy line. The driver reports the action's presence; visual captures establish the result.
