# Evidence provenance

PR [#24172](https://github.com/pingdotgg/t3code/pull/24172), mirror [#24172](https://git.cafe/pingdotgg/t3code/pulls/24172).

Local head verified as [2615e21dec](https://github.com/pingdotgg/t3code/commit/2615e21decad822bf4dd520cf103f9a8e33d49df), base [66ee628e08](https://github.com/pingdotgg/t3code/commit/66ee628e0875b2b735b199f42e6151e347833637).

No tests were rerun in this evidence-capture step. Raw logs are uploaded unchanged. They do not embed commit SHAs or full invocation commands; those cannot be independently recovered from their contents.

- prefix-run.txt: ThreadFork.execution.test.ts, native regression fails, portable passes; 1 failed / 4 passed, 1 file, 6.25 seconds. Lead attributes this to the old implementation. Do not describe it as a head failure.
- red-final.txt: ThreadFork.execution.test.ts, portable-empty regression fails, native passes; 1 failed / 4 passed, 1 file, 6.47 seconds. Lead attributes this to the earlier e928 fix plus new test (test-only commit [4bc67e687d](https://github.com/pingdotgg/t3code/commit/4bc67e687d513e5d71211eed9c56ffcf109e74f5)).
- green-final.txt: 41 passed / 0 failed, 3 files, 11.57 seconds, started 16:58:26 UTC. Supplied focused set: TurnStartReads.test.ts, ThreadFork.execution.test.ts, ProviderTurnStartService.test.ts, from apps/server. The summary itself does not list these filenames or the exact invocation. It predates both final commit timestamps and must be labeled pre-amend implementation evidence, not a rerun at final head.
- lint.txt: only the vp built-in invocation note, no diagnostics; captured exit code is not in the log.
- typecheck.txt: tsc --noEmit, cache disabled; 0 error diagnostics, 0 warning diagnostics, 312 suggestions; captured exit code is not in the log.

Git reflog shows [973840018c](https://github.com/pingdotgg/t3code/commit/973840018c0ed06a88bb68f5820db78763cda484) committed at 16:59:08 UTC and amended to [2615e21dec](https://github.com/pingdotgg/t3code/commit/2615e21decad822bf4dd520cf103f9a8e33d49df) at 16:59:38 UTC. Direct diff confirms only relocation of one existing comment; executable code and tests are unchanged between these commits. No claim is made that the raw green log stamps either SHA.

runtime-head-2615.md and runtime-head-2615.json: independently extracted persisted projections using SQLite URI mode=ro and PRAGMA query_only=ON, one consistent read transaction. Parent 3 completed runs / 6 messages / 3 provider turns. Native fork 1 completed run / 1 own message (/compact) / 1 provider turn / 1 native_fork transfer; compaction 84,252 -> 1,586 tokens. Empty control 1 failed run / 1 own message (/compact) / 0 provider turns / 0 compaction items; exact validation message retained. Fork createdAt 16:59:57.287Z, compact requestedAt 17:00:05.065Z; empty control createdAt 17:00:53.459Z.

Database has no SHA record and zero retained v2 events. Parent-on-e928, fresh fork/control-on-2615 and personal browser verification at head are attributed to the lead. This step did not launch a browser/server, change code/database/forge, push, watch, or poll. T3 PR registration was performed as required by the harness; no forge content was changed.

Portable fixture: both ASCII messages are 17,000 bytes; each exceeds the default 16k budget and is omitted whole. The guard rejects portable context with no surviving history before opening a provider session. Native fixture proves guard acceptance (its test adapter intentionally fails session open); the live native transcript proves completed provider compaction. Shared helper scans transfers and handoffs in O(T + H), O(1) extra space, with no message parser. Visual matrix is empty under the server-only exception. Two fresh MERGE reviews are lead-reported, not independently refreshed.

Friction: missing command/SHA/exit-code stamps in supplied logs; handled with explicit provenance rather than invented commands. No additional proof blocker found.