# Line-link marker reproduction

Base: [d5f8a7573a](https://github.com/pingdotgg/t3code/commit/d5f8a7573a3817d8c20f7491e7672443355c4083)
Head: [3f814fce70](https://github.com/pingdotgg/t3code/commit/3f814fce70c85a0f53c5a2b9563be351805de21a)

Manual proof: same leased iPhone 18 Pro (iOS 27.2) and Pixel 9 (API 36), dark appearance, portrait. Native clients prepared with `vp run mobile:install <platform> --prepare` from each commit. Fingerprints: iOS base 9f6baf01f19a3d8235651fed31b2a10431ed8c62, head 364c0ca72dd14bf282e162a6fcdf567b3f8ffcef; Android base 08557d8a6c12c219d83194973807f16df26eb40f, head 15400cf552e61ea29b3393bc0a2656817a8bcb08.

Each commit ran its own server and Metro from a separate worktree, fresh isolated database, T3CODE_DEV_SEED=0. Run seed.ts using the scenario helper from a current-main checkout: set SCENARIO_RUNNER_DIR to that checkout and T3_SCENARIO_APP_DIR to the app checkout; pass the isolated home and server port as its two arguments. It creates a synthetic 1,150-line doc.md and a real Replay thread through the server API/CLI. It replaces only the command-output Replay fixture with the four file links. No database rows are copied or edited.

Pair the client with that server. Open the Line-link proof thread. Set word wrap on using File actions > Enable word wrap, then return to chat. Run drive.py <agent-device-session> <ios|android> <base|head>. It records: tap L645-647, capture wrap on; File actions > Disable word wrap; back to chat; tap L645-647 again, capture wrap off. The iOS head recording continued with those same remaining commands after the capture driver was interrupted; the stills were obtained with stable.py.

stable.py takes two screenshots at least 500ms apart and requires identical pixels. iOS stills exclude the top 50 logical pixels (the OS status bar) because the charging battery glyph animates; app pixels are unchanged. iOS stills are 402x824, from a 402x874 viewport; Android stills are 1080x2424. Crops are enlargements of those stills, without changing image content: iOS (0,265)-(180,355), 5x; Android (0,220)-(400,400), 3x.

Observed: wrap on highlights L645 on both commits and both platforms. Wrap off lands at the same position per platform, with no marker on base and a light marker on head. Android's rounded top corner clips the upper portion of its marker. L646 and L647 remain unmarked in both modes on both commits: this fix does not implement range highlighting.

The scenario runner was attempted first, but both commits stopped before any test ran because the bundled agent-device client reported an incompatible daemon RPC protocol. The scenario file is supplied for reproducibility, not as proof of a passing scenario. The manual captures and recordings are the evidence.
