# A04 ROOT recapture — other/a.ts
Evidence addendum for [#33064](https://git.cafe/pingdotgg/t3code/pull/33064). Replaces only the ROOT other/a.ts sub-run of the rejected A04 pair. No other matrix row or nested-workspace sub-run is included.
Rendering environment: Linux 6.8.0-117-generic x86_64; Electron 44.10.1 / Chromium 152.0.7977.169, headless-desktop + Xvfb, --no-sandbox --disable-gpu; app surface 1440×1000 dark, DPR 1, 100% zoom/font scale, reduced motion, client Date frozen at 2026-11-10T12:00:00Z with timers running. The unscaled app occupies x=0..1439 of a 2360×1000 framebuffer; the passive 920-pixel trace window is beside it at x=1440. FFmpeg x11grab, H.264, 15 fps. No browser/device emulation or renderer bridge mocks.
Each revision was installed and built in its own requested checkout with its own Electron binary and fresh isolated database; every server used T3CODE_DEV_SEED=0. The supplied scripts generated synthetic root checkpoints through free Replay turns. Both fixtures have the same two changed files; only root other/a.ts is activated. No live userdata was used. The nested-project seeder quirk does not affect this root-only evidence.
Times below are the visible trace clock, not a latency measurement. The player starts slightly later; metadata records the recorder launch offset and the exact seek positions of the extracted stills. The activation narration is held with Reveal in Files highlighted, then Return is sent 0.6 seconds later. After the result, the same row's menu is reopened solely to show the complete trace and menu together; no second item is activated.
Before narrated steps: t+5.03s ACTION: right-click other/a.ts in ROOT changed-files card; t+6.92s MENU: native context menu; Reveal in Files; pointer remains on other/a.ts; t+8.53s SELECT: Down, Down highlights Reveal in Files; pointer stays on target row; t+9.97s ACTIVATE: Return invokes selected Reveal in Files (one activation); t+13.12s RESULT: one reveal RPC and one launcher invocation observed. Reopen menu without activating.
After narrated steps: t+4.82s ACTION: right-click other/a.ts in ROOT changed-files card; t+6.66s MENU: native context menu; Reveal in Files; pointer remains on other/a.ts; t+8.27s SELECT: Down, Down highlights Reveal in Files; pointer stays on target row; t+9.74s ACTIVATE: Return invokes selected Reveal in Files (one activation); t+12.89s RESULT: one reveal RPC and one launcher invocation observed. Reopen menu without activating.
| Matrix row / app viewport / theme | Before | After |
| --- | --- | --- |
| A04 ROOT — changed-files-card other/a.ts — desktop 1440×1000 dark | [A04-root-before.mp4](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/d0484620c0c4c308/A04-root-before.mp4)
[4c361199f4](https://github.com/pingdotgg/t3code/commit/4c361199f47f6ea32a2c14835df392640d0f7c63) | [A04-root-after.mp4](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/0436c681ed82e117/A04-root-after.mp4)
[93a2245059](https://github.com/pingdotgg/t3code/commit/93a2245059f7b9c2555269b24d168dbadc68b3c3) |
Before activation: 
After activation: 
Before result and reopened menu: 
After result and reopened menu: 
Both sides: exactly one shell.openInEditor RPC with editor file-manager, reveal true, cwd /tmp/lead-33064-r1/evidence-capture-2/project/other/a.ts; one successful RPC reply; one gdbus FileManager1.ShowItems stub argv with the matching URI. Before has no native reveal IPC; after has one actual request and false result. Buffered IPC/launcher display timestamps do not establish ordering or latency. Stubs prove invocation only.
I personally inspected all six extracted frames. The root other folder and a.ts filename, pointer, native reveal menu, and trace are visible without overlap or clipped text. Activation stills show the highlighted menu before dispatch; result/menu stills show the complete trace together. Incidental differences: Replay duration 5.3s/5.4s, event times/IDs, focus state, and asynchronous paint timing. No pixel-identity, Windows selection, or performance claim.
Evidence: [A04-root-before.txt](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c74ddea3a58aef52/A04-root-before.txt) · [A04-root-after.txt](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/b4c22b54f659c230/A04-root-after.txt) · [A04-root-before.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/100727ef7f32cbb8/A04-root-before.json) · [A04-root-after.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/7917930957a3728c/A04-root-after.json) · [A04-root-before-menu.png](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/b8dc4c7da2c97af3/A04-root-before-menu.png) · [A04-root-after-menu.png](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/4912d017297b8b08/A04-root-after-menu.png) · [capture-a04-root.mjs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/43b4bfc96cfa2164/capture-a04-root.mjs) · [A04-root-recapture-drivers.tar.gz](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/3407d8b7db8c83b2/A04-root-recapture-drivers.tar.gz) · [A04-root-manifest.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/6d1e841fd695842f/A04-root-manifest.json)
Validation: both desktop build:bundle commands passed; exact trace-count/path/IPC assertions passed; ffprobe verified 2360×1000, 15 fps H.264; six extracted frames inspected. No application source edits or code tests were needed for this evidence-only task.
Cleanup: all captured server, Xvfb, Electron, and recording processes were stopped; both cap2 worktrees removed. Evidence is retained in scratch after upload.
AI-assisted; verified with the tests and tools listed above.