# Linked issue accessibility proof

Run the real web app separately at base a6d2bed55b8ea1b4be27c9c77fdd65e0e7d479d5 and head d549a18d32d0f1d54eeff3095a4a025b17621beb.
Each has its own fresh database; start with `T3CODE_DEV_SEED=0 vp run dev --no-seed`.

Place seed-issue-proof.ts under scripts/scenarios next to the repository's t3.ts helper, and run it with the isolated home and web origin as its two arguments. If the tooling checkout differs from the tested app, set T3_SCENARIO_APP_DIR to the tested checkout.
The seed uses the real project API, Replay agent CLI, and orchestration RPC. It creates the project, plays a turn saying go, and links the synthetic GitHub issue 123 titled Sidebar flickers on resize.

Pair the preview browser using the tested server's pairing link. Wait for sign-in, then navigate to the path printed by the seed. Use Chrome 157 on Linux, 1280x800 CSS pixels, device scale 2, light theme on both sides. Keep the Thread details panel open. Run browser-inspect.js in the page and capture the preview accessibility snapshot.

Take two screenshots at least 500 ms apart and confirm exact pixel equality. Both sides returned zero differing pixels. Crop the Version Control section at device-pixel rectangle x=1978, y=358, width=556, height=346. This crop excludes unrelated environment information. The raw row images are otherwise unchanged.

The evidence images combine this crop with the observed DOM values and the linked-issue excerpt of the browser accessibility snapshot. The text files contain a larger Version Control excerpt with transient references and bounding boxes removed. The exposed second-line generic #123 on base is marked aria-hidden on head, while the link's name and visible row are unchanged.

Base DOM: keyAriaHidden=null, ancestorHidden=false, keyVisible=true.
Head DOM: keyAriaHidden="true", ancestorHidden=true, keyVisible=true.
Both link names: Issue #123: Sidebar flickers on resize.

No screen-reader audio was recorded. The proof covers accessibility exposure in the real browser.
