Real-app terminal history verification
Environment: Linux, Chromium 156.0.8078.4, web client, 1280x800, light theme,
reduced motion, fresh isolated databases (T3CODE_DEV_SEED=0), devReplay agent.

Base: d06ba271669e035dd4094497b367072ccc8986be
Head: 902b6f6e5e3d98569d382de4152a93b0e41a30b0

Same driver on each checkout:
1. Add synthetic identity-probe project and a devReplay thread through the CLI.
2. Open the real web client and terminal drawer (Ctrl+J).
3. Run probe.py: emit tagged A ESC Z B once; collect the live Ghostty reply.
4. Reload the web client; normal snapshot restoration generates no duplicate.
5. Press r: probe reads the tagged payload from the real server's persisted
   terminal history file, prints its hex bytes, then writes those saved bytes
   to stdout of the running PTY (Ghostty's PTY writer remains attached).
6. Press v: display the number of replies received by the running process.
7. Before each published still, wait for two identical PNGs at least 500ms apart.

Observed base result:
{"replies":2,"done":true,"replayed":true,"savedHex":"41 1b 5a 42"}
The saved ESC Z caused another ESC[?62;22c reply during explicit live replay.

Observed head result:
{"replies":1,"done":true,"replayed":true,"savedHex":"41 42"}
The saved payload contained AB only; explicit replay generated no reply.

Scope: proves persistence filtering and replay with an attached PTY writer.
Normal page reload was silent on both sides because resetAndWrite detaches the
writer while restoring the snapshot; an ordinary-reopen duplicate was not seen.
Recordings begin after the probe clears the initial shell prompt, and include
reload, explicit replay, and final results. Initial shell paths are excluded.