# Live Pi restart proof

Use isolated checkouts for the two commits in runtime-transcript.json. Install each with `vp i`.
Install Pi 1.5.2, @mwolson-org/pi-xai-ws 1.5.0 and `ws`. The existing Pi xai configuration must have working provider credentials; no credentials are included here.

1. Set EVIDENCE_OUTPUT to a new directory and PI_XAI_EXTENSION_DIR to the installed extension directory. Run prepare-state.py. It creates two fresh T3 homes and an isolated Pi agent configuration using only the existing xai provider settings.
2. Set PI_CODING_AGENT_DIR to the generated pi-agent directory. Start drop-after-25.mjs with node from a directory where ws resolves. It listens only on loopback port 19081.
3. In each checkout, start `T3CODE_DEV_SEED=0 PI_XAI_WS_URL=ws://127.0.0.1:19081/<side>/responses vp run dev --home-dir <generated-side-home> --no-seed`, using base or head for side. The Pi agent directory must also be inherited by the server.
4. Run seed-thread.sh with that side's T3 home and a synthetic project directory. Open its returned thread through the app's normal pairing flow and thread URL. Hide the thread details panel to keep the environment label out of recordings. Expand Thinking.
5. Start a browser recording. The proxy holds after 25 reasoning deltas. GET http://127.0.0.1:19081/release/<side> releases that gate and drops the connection. It forwards provider content unchanged, pacing reasoning deltas at 300 ms. Pi's extension reconnects and restarts the same block.
6. Watch the next streaming update. Base appends the replacement to the abandoned text. Head replaces the old text. The proxy holds after another 25 reasoning deltas for inspection. Stop the recording, release the second gate using the same URL, and stop the turn.

Both captures use Linux Chromium, 1280x800 CSS pixels and light theme. The provider is real xai/grok-4.7 through the configured CLIProxyAPI hub, not an ACP replay. Fresh databases contain only synthetic projects and threads. The recordings show the restart while the turn is still streaming, before final content can replace it. No unit tests are offered as evidence.

The live provider did not produce an empty retry; empty replacement completion and text-block restarts remain unverified.
