# MCP disconnect checkpoint restore evidence

Linux web app, Chromium 156, 1280x800, light theme. Both sides use fresh isolated T3 homes and synthetic repositories, created through the server CLI/API. No provider account or live database is used.

The scenario runs the real dev server, web client, ACP provider adapter, MCP HTTP server, bridge finalizers, checkpoint restore and follow-up turn. The free replay agent supplies the model output.

`mcp-fault.mjs` is an external Node preload harness. It adds ACP MCP capability negotiation to the replay agent and has it initialize four MCP sessions. It redirects the bridge's real HTTP DELETE requests to a local HTTP listener that accepts the requests but never sends a response. It does not change production bridge, teardown, checkpoint or orchestration code. The transport log records request acceptance and cancellation without identifiers, headers or credentials.

Place the scenario in `scripts/scenarios/mcp-disconnect-bounded.e2e.ts` in a checkout with the scenario runner. Download the preload beside this file, then run from the repository root (set HARNESS to the downloaded file's absolute path):

```sh
T3CODE_DEV_SEED=0 MCP_EVIDENCE_LOG="$PWD/transport.ndjson" T3_SCENARIO_INHERIT_ENV='NODE_OPTIONS,T3CODE_DEV_SEED,MCP_EVIDENCE_LOG' NODE_OPTIONS="--import=$HARNESS" vp run scenarios:prove scripts/scenarios/mcp-disconnect-bounded.e2e.ts --base a99faf5a629023a5aca16fc8422553a5a4a9067f --head cf0b3ddfad334b0c8bddd84c515ba66c2a678305 --upload-command 'ghdrop upload'
```

The UI sends a second message, waits for its completed turn, then selects Edit from here and Revert files too. The prompt must return to the composer within 15 seconds. After restore, the scenario sends a follow-up and requires the replayed assistant response.
