# Evidence index — issue24549

Evidence inspection only; captures and test runs were produced by the primary lead. No implementation edits, commits, pushes, test runs, app/browser/server launches, or merge performed by this evidence sub-agent. Worktree was clean when inspected.

## Source identity

Git HEAD: [9c52670b39](https://git.cafe/pingdotgg/t3code/commit/9c52670b395884bbef37a6a255cee771404a9c28), full SHA `9c52670b395884bbef37a6a255cee771404a9c28`.
Base: [3afb9b366f](https://git.cafe/pingdotgg/t3code/commit/3afb9b366f271b56a3e49fd86f2594981ec11b66), full SHA `3afb9b366f271b56a3e49fd86f2594981ec11b66`.
Verified with git rev-parse HEAD and git show. Before transcript header identifies full base SHA; after header identifies abbreviated head, resolved above via git. Test output itself does not embed a commit SHA; commit attribution comes from lead context and current source, not a cryptographically bound test transcript.

Diff: only OpenCode adapter and its server adapter tests, 69 insertions / 3 deletions. No changed render paths. [Proof audit / empty render matrix](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/63d12c4b6b086e9d/issue24549-proof-audit-pass1.md). Zero recording rows; no recordings required. Screenshots illustrate outcomes, not visual differences.

## Test evidence

[Red transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/53af69c6fd80ed28/red.txt): `forks a stopped session whose interrupted event never arrived` fails with expected `ProviderAdapterProtocolError: ... Cannot fork OpenCode session ... while it is still working.` 1 failed / 78 skipped (79 total). It also logs replay-incomplete with six unconsumed entries after rejection; this is secondary fallout, not a separate successful proof. Run start 21:41:50 UTC.

[Green transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e5e7c5abf322610f/green.txt): one test file, 80 passed (80), 6.17 seconds, start 21:46:00 UTC. File is `src/orchestration-v2/Adapters/OpenCode2AdapterV2.test.ts` (explicit in red; green summary omits file name). Exact invocation/filter/exit status is not recorded in these output files; no command was reconstructed or rerun.

Source-confirmed names in the full adapter suite:

- `forks a stopped session whose interrupted event never arrived`
- `refuses to fork a stopped session OpenCode still runs`
- `drops the turns a rollback cut from the snapshot it returns`
- `starts a turn sent during a rollback only once the cut is made`
- `refuses to fork a session while OpenCode runs a follow-up on it`

The two existing rollback tests cover retained snapshot history and ordering during rollback. Their inclusion in the 80-test suite does not independently demonstrate rollback recovery under missing interrupted-event delivery; that audit branch remains a proof limitation.

## Runtime evidence

[Before transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/23b01bbcf6343721/runtime-before.txt): lead reports real OpenCode 2.1.2 / configured Claude Haiku 5.5, isolated worktree state, Linux, Chromium 1280x800 light. Normal delivery control succeeds. With proxy dropping `session.execution.interrupted`, Stop then fork/send fails with still-working protocol error at 21:38–21:39 UTC; dropped event timestamp 21:38:56.362Z.

[After transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/a7a0e01069f620d5/runtime-after.txt): lead reports same proxy/fault after source watch restart; dropped frames at 21:45:22.197Z–.201Z, seven streams including health probes. Stop then fork/send returns assistant `fork works`; lineage source Stopped. Source and target thread IDs recorded. Brief navigation/editor timing friction resolved by retry after navigation settled.

[Fault proxy source](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/39e732c088c45b0d/proxy.cjs): forwards to real OpenCode and drops SSE frames containing `session.execution.interrupted`. Generates a random password at runtime; no literal credential present. Drop filter is event-type-wide, not restricted to a source session. Unrelated traffic is forwarded by the inspected implementation. This file was inspected, never executed by this sub-agent. Credential-bearing `opencode.log` was neither read nor uploaded.

These are lead-authored narrative runtime captures, not raw HTTP/SSE traces. They do not directly show interrupt response `interrupted:true`, active-list response/request correlation, fork native ID/boundary, or exactly-once terminal events. No independent rerun or deeper protocol observation is claimed.

Before — inspected screenshot corroborates still-working rejection:

![Before: fork fails with OpenCode still-working protocol error](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/638eb0e07ecbd811/browser-screenshot-localhost-mvmx8odc-bd74f1b6.png)

After — inspected screenshot corroborates fork reply and stopped source lineage:

![After: fork conversation replies fork works and source lineage is Stopped](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/687bf2573b2996d4/browser-screenshot-localhost-mvmxhmx4-21c95765.png)

## Scope, safety, and FRICTION

All seven uploaded artifacts were inspected for publication safety: no literal credentials, pairing tokens, or private prompt content found; screenshots contain task fixture prompts and local workspace labels. Uploads used ghdrop upload -m per ghdrop skill. No opencode.log upload. No PR was created, modified, or reviewed in this evidence step.

FRICTION: web reader could not fetch the audit markdown; plain curl succeeded. No upload failures. Exact test invocation and historical test SHA are not present in raw output. Runtime proof is lead-authored and screenshot-corroborated, not an independently captured protocol trace. Missing-event rollback recovery, delayed-event race, and active-query failure branches are not newly demonstrated by these artifacts. Existing rollback test names and aggregate green count are recorded without overstating their coverage.