# Evidence index — closed Claude transport interruption

Verdict: PASS for the narrow cleanup-interrupt correction. Capture rows completed/required: **0/0**; screenshots 0, recordings 0. Server-only diff; no UI captures required.

Head: [fddeb88fef](https://git.cafe/pingdotgg/t3code/commit/fddeb88fefc789de365cac1a7d138664aeebeb9f). Runtime before base: [f89855713d](https://git.cafe/pingdotgg/t3code/commit/f89855713d). Refreshed main: [44df336016](https://git.cafe/pingdotgg/t3code/commit/44df336016). Base refresh changes only unrelated mobile dependency/patch files and a web test; the changed adapter and regression-test files are identical across those bases.

Environment: fs-11, Linux x64; lead's isolated worktree `/home/ubuntu/wt/issue-25146`, T3 home `.t3`; web port 7810, server port 15850; Claude Opus 5.5 (model label supplied by lead). Real fresh throwaway git project. This audit launched no browser or server and reran no tests.

Reproduction: fresh root-checkout Claude thread calls `t3_worktree_handoff`, `startFromOrigin=false`, `runSetupScript=false`, with continuation requesting pwd/branch and `CLAUDE HANDOFF FINISHED`. Before branch `repro-25146-b`; after branch `repro-25146-c`.

| Evidence | Exact supported claim |
| --- | --- |
| [Proof audit](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/01bedf24c67e9901/proof-matrix.md) | Empty capture matrix: 0 required rows. |
| [Before runtime](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/773ff77adfdfe431/before-runtime.txt) | Cleanup interruption fails with ProviderAdapterInterruptError / ProcessTransport is not ready for writing. |
| [Red regression test](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/431574080e4f3c06/red-test.txt) | Supplied isolated test-only run on the before base fails for the matching closed-transport cause; not rerun by this auditor. |
| [After runtime](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/a96b2a26ff949ba0/after-runtime.txt) | Cleanup interrupt span exits Success on the fresh after thread. |
| [Changed-file checks](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/4ef5bf404025365d/check-changed.txt) | Recorded check:changed passes format, lint, knip, GraphQL, affected typecheck, and 236 adapter tests. Warnings/suggestions remain; full CI suites/build are outside this evidence. |

Thread identity independently checked against local `server.trace.ndjson`:
- Before thread `43491c61-d4fe-4448-aa74-19e7cdd49dbd`: Claude thread creation at line 8036; interrupt Failure at line 9204, span `de8768afe39f14a3`, trace `cc7e8afad5edc122af3afa854b2aa4d3`. Same-parent event-sink spans identify this thread.
- After thread `f0305734-2fb5-41fc-971f-df229ce13035`: fresh Claude thread creation at line 13948; interrupt Success at line 15184, span `1144ece9f981fb51`, trace `abd8b0d4deb40ba69584fe45b2005e52`. Same-parent event-sink spans identify this thread, ruling out a different thread's successful interrupt.

Publication audit: downloaded all five linked artifacts and confirmed byte-for-byte equality with local files. Reviewed repro excerpts, diff, and check summary; no credentials found in published artifacts. Raw server logs are deliberately excluded because they contain a pairing credential. No repository edits, pushes, merges, watches, screenshots, or new matrix files in the repository.

FRICTION
- Provider stream failure and queued continuation persist. Lead attributes this to separate [#22971](https://git.cafe/pingdotgg/t3code/issues/22971); this audit confirms persistence, not independent issue attribution.
- Evidence proves closed-transport cleanup interruption succeeds after scope closure. It does not prove successful end-to-end handoff continuation or repaired user-visible flow.
- No claims of verification for mobile, desktop, remote/relay/tunnel, other providers, or other entry points. Recorded runtime used local web with Claude only.
- Green checks and red-test execution are supplied recorded output, not independent reruns. The proof audit predates publication of the after/check artifacts; those are now published above.

Auditor: GPT-6.1-sol through Codex in T3 Code.