# Issue 19124 — evidence index

Scope: [#19124](https://git.cafe/pingdotgg/t3code/issues/19124), branch `fix/issue-19124`, [70e5e384da](https://git.cafe/pingdotgg/t3code/commit/70e5e384da) → [13f0f0a1d4](https://git.cafe/pingdotgg/t3code/commit/13f0f0a1d4). Inspected HEAD `13f0f0a1d4800b575147a24da1cd9d05a84ea2da` in `/home/ubuntu/wt/issue-19124`. No PR, repository edits, commits, push, browser/server launch, or watcher by this evidence agent.

## Applicability and disposition

Named render matrix `issue-19124-render-fixtures-v1`: EMPTY, rows 0/0. Only the server recovery service and focused test changed. Explicit server-only exception applies: red test plus runtime transcripts; viewport/theme/capture fixtures are not required. Runtime recovery evidence supports the claimed fix for Linux/web/Codex. Raw green verification independently captured here; historical red result is a supplied summary, not raw runner output. Do not claim independently replayed baseline or exhaustive surface coverage.

## Artifact inventory

- [Baseline transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/de9f0d1d1e83264c/issue-19124-runtime-before.txt)
- [Fixed transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/9debbafec6db6c84/issue-19124-runtime-after.txt)
- [Red-test summary](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/53c22b1eb2860056/issue-19124-red-test.txt)
- [Raw green test output](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/37700de71fd5263a/issue-19124-green-test.txt)
- [Persisted run-state export](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/998cc5965867721f/issue-19124-run-state.json)
- [Proof audit pass 1](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/a2e3795323aab108/issue-19124-proof-audit-pass-1.md)

## Inspected behavior and controls

- Baseline transcript: actual app at baseline completed READY; fast-forward merge, managed worktree removal and branch deletion preceded AFTER_CLEANUP and RETRY failures. Logs show `ref_not_found`. Restoring only `t3/reply-ready` allowed automatic directory recovery and RESTORED_BRANCH success. This controls for recovery when the branch still exists.
- Fixed transcript: same isolated database, fixture project and conversation; successful worktree removal and branch deletion preceded AFTER_FIX. Response completed; exact managed path returned, and `main` and `t3/reply-ready` both resolved to `acfbbddb6a4701f02033b4be498c4834cea609ae`. This supports project checkout HEAD as the recreated branch base.
- Persisted export matches the fixed transcript's embedded data: five runs, completed/failed/failed/completed/completed, identical `provider_thread_id`. READY ran 22:31:50.145–22:31:55.016Z; failures began 22:32:05.723Z and 22:32:31.210Z; RESTORED_BRANCH ran 22:32:46.226–22:32:49.065Z; AFTER_FIX ran 22:47:31.379–22:47:36.538Z, all 2026-10-21. Export inspected as an artifact, not independently re-queried from the DB.
- Code inspection: missing managed path with recorded branch first prunes and attempts existing branch checkout; only `ref_not_found` retries with `refName: HEAD`, `newRefName: branch`, same path and project root cwd. Existing eligibility and outer error/interruption handling remain. Git driver translates newRefName to `git worktree add -b`.
- Focused command: `node_modules/.bin/vp test run apps/server/src/orchestration-v2/ProviderTurnStartService.test.ts`. Independently captured at fixed HEAD: 1 file, 23/23 tests passed, exit 0. No full typecheck or broad suite run.
- Historical red summary identifies baseline, red-test commit, command, failing final-call assertion, 1 failed/22 passed. It lacks raw runner output and explicit numeric exit status; these cannot be reconstructed honestly. New regression checks final cwd/newRefName/path, but not explicit HEAD, exact retry count, unrelated-error exclusion, or provider completion. Runtime transcript supplies continuation proof; it does not make those unit assertions exhaustive.

## Supplemental visuals — not matched pixel UI evidence

Inspected both screenshots: baseline displays missing-workspace/provider failure; fixed screenshot shows earlier failed turns, RESTORED_BRANCH and AFTER_FIX. Visible changes include timestamps, new turns, scrolling and provider update toast. No render edits. Linux Chromium, 1280×800 desktop UA, no emulation; DPR unknown (not queried). These are existing artifacts, not new captures.

Before — missing workspace failure:

![Before: AFTER_CLEANUP fails with missing managed workspace](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/2d54443c99ae066a/browser-screenshot-localhost-mviotm9d-55729949.png)

After — continued thread replies AFTER_FIX:

![After: existing conversation completes AFTER_FIX](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/5db28c3defec7481/browser-screenshot-localhost-mvipddf0-76326cdd.png)

[Supplemental after recording](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/ff467e4bb317b867/mcp-launch-client-3af0bd65b4-1580-4c7d-a80f-264a7193468f-fwd-3a4efab5d2a12dbef7d-1c3a74cd-704d-4e89-9213-53c6e725207f-mp4.mp4): linked as supplied, not independently played by this agent. Transcript reports 22:47:18.501–22:47:48.321Z, submission and completion matching persisted timestamps.

## Coverage limits

Direct runtime coverage: actual isolated Linux web app, Codex CLI 0.163.0, GPT-6.1-Sol, existing conversation after managed worktree/branch deletion. Server path is shared, but Electron, native iOS, native Android, other operating systems/providers, remote/relay/tunnel, MCP and scheduled entry points were not directly exercised here. No client render or wire-contract changes. No new integrated runtime pass was performed by this agent; primary had already completed it once.

## Local artifact SHA-256

- `issue-19124-runtime-before.txt`: `a440e2014215273cab035165266a61c7db7502166f613b0e2020bd6b29348861`
- `issue-19124-runtime-after.txt`: `3355ad8425c8bf9dca0cb8127144764c654e4979f34ae0fd844eb7e2d01fe77a`
- `issue-19124-red-test.txt`: `719400bf9a057879c9806bc2a952776719e8f081a38112b888844f36e3181435`
- `issue-19124-green-test.txt`: `4d933015a926beea7873413203b77cdfd1a7586a3a9b1ad20aa858c20142a64a`
- `issue-19124-run-state.json`: `2ec06f232029f41fd17d6b2c92e3b8bf9dbaf23441cad4f636c639b0635b9535`

## FRICTION category | happened | avoid

- Evidence fidelity | Historical red artifact is a summary, raw green was absent | Capture one focused green run; retain explicit historical-red limitation.
- Discovery | Broad /tmp filename search encountered protected system directories; one guessed GitWorkflow path did not exist | Use supplied artifact paths and actual driver/service paths; no permission changes.
- Visual scope | Screenshots differ in conversation state and toast; DPR absent | Label supplemental, DPR unknown; no pixel-diff or fixture coverage claim.
- Operational isolation | Primary already performed runtime pass | Reuse artifacts; no additional browsers or servers, no repository mutations.