# Binary path proof

Manual fallback after two scenario comparisons stopped on bootstrap/navigation errors. The completed evidence uses two separate checkouts: base b2e86d79020358d51bae4c30eb415c1a5da7c132 and head 70dd0a5832f8dacf10e7f504df1ab8c562e82795, each installed with `vp i` and run as the real web app/server. No application source was modified.

Both sides: Chromium through the T3 Browser panel, 1440×1100 CSS viewport, light theme, fresh databases, no projects or threads, the same synthetic provider settings and executable fixtures. The environment is labelled Scenario. No real provider turns or accounts are needed. Kiro and fx fixtures answer real subprocess probes; Antigravity resolves its executable file without spawning it.

Set and export `T3_PROOF_HOME` to a fresh synthetic fixture directory. Run `sh prepare-fixtures.sh`. Place the supplied `start-app.ts` and `shell.ts` together where their package imports resolve (the checkout's scripts directory works). From each app checkout, run the same script with a different fresh app home and web port:

```sh
T3CODE_DEV_SEED=0 node start-app.ts web <fresh-app-home> 127.0.0.1 <web-port>
```

The script starts the checkout's own dev runner with `--no-seed`, supplies an isolated server HOME, and creates synthetic provider settings. Pair the browser using the private `pairing-path` file under that app home. Wait for the Welcome page to finish loading before navigating to `/settings/providers`.

Run the operations in `manual-browser-driver.js` on each side. Capture the home-relative Kiro, fx and Antigravity panels, then scroll to Antigravity's Binary path. Next replace each Binary path with the absolute form under the fixture home, press Tab, refresh provider status, and capture the working absolute controls. Every published still was checked against an identical screenshot 500 ms apart and visually opened.

Observed base: home-relative Kiro and fx show Not found with no version; Antigravity rejects its custom executable. Absolute paths work for all three. Observed head: both path forms detect Kiro 2.32.0 and fx 0.0.13; Antigravity is installed with sign-in not checked. Kiro is deliberately signed out, and fx's authenticated status comes from the synthetic fixture.

The attempted input type masking was reset by React. Public absolute-control stills therefore redact the temporary path after capture. Public recordings redact the input column and play at 2× speed; provider status and versions remain visible. Home-relative paths are fully visible in the stills. No status or version was edited.

The included scenario file and fixture patch document the attempted automated comparison; neither is claimed as the successful proof. The manual captures and recordings are the proof.

AI-assisted; verified with the tests and tools listed above.