# Server-only evidence for issue 25370

Scope: [#25370](https://git.cafe/pingdotgg/t3code/issues/25370). Visual matrix rows: **0/0** (empty); no rendering changes and no screenshots. Only GitVcsDriverCore.ts and its existing test file change, 37 insertions. [Proof matrix](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/b1be92c2670cf3cf/proof-matrix.md).

Compared base [bfc7177f9f](https://git.cafe/pingdotgg/t3code/commit/bfc7177f9f54b0a4b9d3571d30723a51cd4b31bd) (`bfc7177f9f54b0a4b9d3571d30723a51cd4b31bd`) to head [c886ffb85d](https://git.cafe/pingdotgg/t3code/commit/c886ffb85dd0680c955e3cdebd6259cc44f37575) (`c886ffb85dd0680c955e3cdebd6259cc44f37575`). Red dev runtime identifies predecessor [c85909f372](https://git.cafe/pingdotgg/t3code/commit/c85909f3727b30ab139396a3d5d2de00fd4b7955) (`c85909f3727b30ab139396a3d5d2de00fd4b7955`), with zero dirty server files. Its GitVcsDriverCore.ts is identical to the compared base. Green runtime identifies the requested head, also with zero dirty server files.

## Before and after

| Evidence | Before | After |
| --- | --- | --- |
| Native Git control, noisy post-checkout hook | `exit=0 stderr_bytes=1100000` | `exit=0 stderr_bytes=1100000` |
| Regression tests, progress false and true | `2 failed`, both `Git output exceeded 1000000 bytes and was truncated.` | Full file: `165 passed (165)` |
| Isolated dev server, worktree-backed thread launch | Thread `failed`; Git worktree nevertheless exists | Thread `running`, managed path `/tmp/task-isolated-home/worktrees/repo/t3-noisy`; source and worktree HEAD both `58e26e1` |
| Original isolated serve reproduction | `Workspace preparation failed during provision worktree: ... Git output exceeded 1000000 bytes and was truncated.`; thread command exit 1 | See green dev transcript |

The red dev transcript's failure-detail section is empty; it establishes the failed state, not the error text. The original serve transcript and red unit log supply the explicit output-limit error. The original serve transcript does not independently record its source SHA. Green proves workspace provisioning, not a completed provider response.

## Commands and artifacts

Runtime script invocation: `bash /tmp/t3-25370/evidence/driver.sh <t3code-checkout> <red|green>`. This starts `vp run dev:server --home-dir /tmp/task-isolated-home`, then from `<checkout>/apps/server` runs:

```sh
node src/bin.ts project add --base-dir /tmp/task-isolated-home /tmp/t3-25370/repo
node src/bin.ts thread start --base-dir /tmp/task-isolated-home --provider codex --model gpt-5.4-mini --worktree main --branch t3/noisy /tmp/t3-25370/repo 'say hi'
node src/bin.ts thread show --base-dir /tmp/task-isolated-home <thread-id>
```

The driver creates a synthetic repository with this executable post-checkout hook:

```sh
#!/bin/sh
head -c 1100000 /dev/zero | tr "\0" x
```

It stops its captured server process group; both principal transcripts report `0 processes left`. The driver resets its fixed scratch home/repository; it is a historical reproduction artifact, not executed during this audit.

Unit-test reproduction commands (reconstructed from file/filter and runner output; exact original invocation and exit status were not saved): from `apps/server`, `vp test run src/vcs/GitVcsDriverCore.test.ts -t 'creates a worktree when checkout prints over 1 MB'` for the red cases, and `vp test run src/vcs/GitVcsDriverCore.test.ts` for the green file. The green log is summary-only, without SHA or individual cases. The existing test verifies returned worktree path and matching HEAD in both progress modes; it does not assert a progress callback after truncation.

- [Red test log](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/5970bda1880404b5/red-unit-tests.log)
- [Green test log](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/44746450c480b185/green-unit-tests.log)
- [Dev runtime driver](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/fdd83dbf789965db/driver.sh)
- [Red dev transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/48fdf5a9a1f4a9ac/red-dev-homedir-transcript.txt)
- [Red dev first run](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/53f37df22e1dee54/red-dev-homedir-transcript-run1.txt)
- [Green dev transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/83ab0d10859df7e2/green-dev-homedir-transcript.txt)
- [Original red serve transcript, full error](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/92bf2b0e5a455f02/red-serve-basedir-transcript.txt)
- [Original serve reproduction script](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/b708970b3da19e9d/original-repro.sh)

## Audit limits and FRICTION

Every file under the evidence directory was inspected for accuracy and secrets. Raw server-green.log, server-red.log, and server-red-run1.log contain dev pairing tokens and were deliberately not uploaded. Uploaded transcripts/scripts/test logs contain synthetic fixture paths and identifiers, no credentials found. Existing originals remain unchanged.

The initial changed-file check failed because a generated server-local compiler shim pointed at a removed TypeScript installation. After repairing the ignored shim to use the checkout's installed compiler, `vp run check:changed` passed format, lint, both knip checks, GraphQL, both affected package typechecks, and all 165 tests. [Final changed-file check log](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/2739f037352934fb/check-changed-repaired.log).

Proof audit pass 2: SUFFICIENT. Both independent code reviewers found no blockers. Public source artifacts were reviewed for secrets; raw server logs were excluded. No render paths changed.