# Runtime evidence for [#32950](https://git.cafe/pingdotgg/t3code/pull/32950) **Captured 9/9 required POSIX rows: R1–R8 and E5.** Before [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e); after [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340). W1–W3 remain `cannot-verify windows`. The optional E rows were not captured separately. This report supplies runtime evidence; it does not replace the focused tests recorded in the proof audit. ## Environment and isolation Linux x86_64, kernel `6.8.0-117-generic`; source servers and RPC runner use Node `v26.12.1`. The executable stub uses its Node shebang and the provider environment selects Node `v26.13.0` on both sides. Captured on 2026-11-10, 10:09:43–10:10:14 UTC. No browser or rendered UI applies. Each server ran directly from its recorded checkout with `T3CODE_DEV_SEED=0 node /apps/server/src/bin.ts serve --base-dir --host 127.0.0.1 --port <18461-before|18462-after> --no-browser`, started with process cwd H. The before source used its own installed dependencies in a detached checkout. No source overlays, production edits, package downloads or paid provider calls were used. Every database was freshly created by that side’s own server; the local base was then reused once for the persistence observation. No live data directory was read or seeded. Both sides use the exact same executable stub, settings structure, RPC driver and directory tree; only log/base locations and the loopback port differ. H and P are shared across the sequential before/after runs. Each transcript begins with the full SHA. The fixtures select a relative local `commandPath` for R1–R8 and a relative **registry override** for E5. Excerpts below project recorded fields and replace only the path prefixes shown here. Full timestamps, full paths, responses, identities and the directory listings are in the uploaded NDJSON. `watches` counts live `fs.watch` handles; `procInotifyWatches` independently counts Linux `/proc/self/fdinfo` inotify entries. These metrics do not establish native Windows or macOS behavior. ```text CAPTURE=/tmp/lead-32950-r1/evidence-capture/run-2026-11-10T10-09-43-345Z H=CAPTURE/fixture/fakehome (1,666 directories including root) P=CAPTURE/fixture/project (5 directories including root; deliberately no Git repository) B=CAPTURE//base-local/userdata/acp-registry/background-cwd B_registry=CAPTURE//base-registry/userdata/acp-registry/background-cwd ``` Raw ACP session setup can contain synthetic MCP bearer credentials. Uploaded copies omit those credential fields and ACP prompt contents; the original synthetic user request remains in the RPC `message.dispatch` record. Raw originals stay private in the allocated scratch directory. No private runtime model identifier is published. `synthetic-model` is an invented fixture ID. ## R1 — Startup status probe and sign-in discovery **Before shows the bug; after fixes it.** The initialize client names distinguish discovery (`t3-code-provider-auth`) from the status probe (`t3-code-provider-test`). Both start in H with 1,666 watches before, and B with one watch after. Only the status probe creates a session. This actual launch also covers E2: the settings value is `../bin/stub-acp-agent.mjs`, and the spawn records identify the executed script and its SHA-256. | Before | After | | --- | --- | | [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e) | [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340) | | 
{"event":"server.start","pid":1726757,"cwd":"H","base":"CAPTURE/before/base-local"}
{"event":"request","pid":1727021,"method":"initialize","processCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"response","pid":1727021,"method":"initialize","protocolVersion":1}
{"event":"request","pid":1727022,"method":"session/new","processCwd":"H","sessionCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-test","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1727022,"method":"session/new","sessionId":"synthetic-session-1727022"}
| 
{"event":"server.start","pid":1728600,"cwd":"H","base":"CAPTURE/after/base-local"}
{"event":"request","pid":1728902,"method":"initialize","processCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"response","pid":1728902,"method":"initialize","protocolVersion":1}
{"event":"request","pid":1728903,"method":"session/new","processCwd":"B","sessionCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-test","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1728903,"method":"session/new","sessionId":"synthetic-session-1728903"}
| ## R2 — Agent-managed sign-in and session verification **Before shows the bug; after fixes it.** The foreground auth child initializes, answers `authenticate`, and verifies via `session/new` in the same PID. The RPC returns `starting`; subscription completion records `succeeded`. No separate env-var sign-in was executed: the matrix accepts this capture of their shared runtime/cwd route. | Before | After | | --- | --- | | [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e) | [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340) | | 
{"event":"rpc.call","rpcId":"3","tag":"provider.auth.start","payload":{"instanceId":"proof-acp","methodId":"synthetic-agent"}}
{"event":"request","pid":1727326,"method":"initialize","processCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1727326,"method":"authenticate","processCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741825}
{"event":"request","pid":1727326,"method":"session/new","processCwd":"H","sessionCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741826}
{"event":"auth.complete","methodId":"synthetic-agent","phase":"succeeded","message":"Sign-in complete."}
| 
{"event":"rpc.call","rpcId":"3","tag":"provider.auth.start","payload":{"instanceId":"proof-acp","methodId":"synthetic-agent"}}
{"event":"request","pid":1729289,"method":"initialize","processCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1729289,"method":"authenticate","processCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741825}
{"event":"request","pid":1729289,"method":"session/new","processCwd":"B","sessionCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741826}
{"event":"auth.complete","methodId":"synthetic-agent","phase":"succeeded","message":"Sign-in complete."}
| ## R3 — Terminal login through the real PTY **Before shows the bug; after fixes it.** This is the actual PTY child, not an ACP probe. It receives both terminal-method arguments, logs cwd and both watcher counts, emits terminal success, and exits 0. The controller only reports success after its PTY exit and subsequent verification. | Before | After | | --- | --- | | [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e) | [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340) | | 
{"event":"rpc.call","rpcId":"4","tag":"provider.auth.start","payload":{"instanceId":"proof-acp","methodId":"synthetic-terminal"}}
{"event":"spawn","pid":1727434,"argv":["/home/user/.local/share/vite-plus/js_runtime/node/26.13.0/bin/node","CAPTURE/fixture/bin/stub-acp-agent.mjs","--synthetic-login","--synthetic-login-marker"],"processCwd":"H","watches":1666,"procInotifyWatches":1666}
{"event":"terminal-login","pid":1727434,"argv":["/home/user/.local/share/vite-plus/js_runtime/node/26.13.0/bin/node","CAPTURE/fixture/bin/stub-acp-agent.mjs","--synthetic-login","--synthetic-login-marker"],"exitCode":0}
{"event":"auth.complete","methodId":"synthetic-terminal","phase":"succeeded","message":"Sign-in complete."}
| 
{"event":"rpc.call","rpcId":"4","tag":"provider.auth.start","payload":{"instanceId":"proof-acp","methodId":"synthetic-terminal"}}
{"event":"spawn","pid":1729556,"argv":["/home/user/.local/share/vite-plus/js_runtime/node/26.13.0/bin/node","CAPTURE/fixture/bin/stub-acp-agent.mjs","--synthetic-login","--synthetic-login-marker"],"processCwd":"B","watches":1,"procInotifyWatches":1}
{"event":"terminal-login","pid":1729556,"argv":["/home/user/.local/share/vite-plus/js_runtime/node/26.13.0/bin/node","CAPTURE/fixture/bin/stub-acp-agent.mjs","--synthetic-login","--synthetic-login-marker"],"exitCode":0}
{"event":"auth.complete","methodId":"synthetic-terminal","phase":"succeeded","message":"Sign-in complete."}
| ## R4 — Post-terminal verification in a fresh ACP process **Before shows the bug; after fixes it.** The verification PID differs from the terminal-login PID. It initializes, creates a session, then the sign-in flow completes successfully. | Before | After | | --- | --- | | [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e) | [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340) | | 
{"event":"terminal-login","pid":1727434,"exitCode":0}
{"event":"request","pid":1727459,"method":"initialize","processCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1727459,"method":"session/new","processCwd":"H","sessionCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1727459,"method":"session/new","sessionId":"synthetic-session-1727459"}
{"event":"auth.complete","methodId":"synthetic-terminal","phase":"succeeded","message":"Sign-in complete."}
| 
{"event":"terminal-login","pid":1729556,"exitCode":0}
{"event":"request","pid":1729609,"method":"initialize","processCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1729609,"method":"session/new","processCwd":"B","sessionCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1729609,"method":"session/new","sessionId":"synthetic-session-1729609"}
{"event":"auth.complete","methodId":"synthetic-terminal","phase":"succeeded","message":"Sign-in complete."}
| ## R5 — Auth-controller logout **Before shows the bug; after fixes it.** `provider.auth.logout` creates a fresh auth-controller child; the actual wire method is `auth/logout`. Its empty valid response is followed by the server’s `Signed out.` completion. This is ordinary registry logout, not the management fallback. | Before | After | | --- | --- | | [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e) | [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340) | | 
{"event":"rpc.call","rpcId":"5","tag":"provider.auth.logout","payload":{"instanceId":"proof-acp"}}
{"event":"request","pid":1727486,"method":"initialize","processCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1727486,"method":"auth/logout","processCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1727486,"method":"auth/logout","result":{}}
{"event":"rpc.complete","rpcId":"5","tag":"provider.auth.logout","value":{"instanceId":"proof-acp","phase":"idle","flowId":null,"authorizationUrl":null,"expiresAt":null,"message":"Signed out.","methods":[{"id":"synthetic-agent","name":"Synthetic agent sign-in","description":null,"type":"agent"},{"id":"synthetic-terminal","name":"Synthetic terminal sign-in","description":null,"type":"terminal"},{"id":"synthetic-env","name":"Synthetic environment verification","description":null,"type":"agent"}],"interaction":null,"credentialOwner":"provider"}}
| 
{"event":"rpc.call","rpcId":"5","tag":"provider.auth.logout","payload":{"instanceId":"proof-acp"}}
{"event":"request","pid":1729656,"method":"initialize","processCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1729656,"method":"auth/logout","processCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1729656,"method":"auth/logout","result":{}}
{"event":"rpc.complete","rpcId":"5","tag":"provider.auth.logout","value":{"instanceId":"proof-acp","phase":"idle","flowId":null,"authorizationUrl":null,"expiresAt":null,"message":"Signed out.","methods":[{"id":"synthetic-agent","name":"Synthetic agent sign-in","description":null,"type":"agent"},{"id":"synthetic-terminal","name":"Synthetic terminal sign-in","description":null,"type":"terminal"},{"id":"synthetic-env","name":"Synthetic environment verification","description":null,"type":"agent"}],"interaction":null,"credentialOwner":"provider"}}
| ## R6 — Background directory persistence across restart **New persistence behavior.** Before never creates B. After creates B at the first startup, leaves it present and empty after SIGTERM, reuses the same base and B for two new startup children with one watch each, then leaves B present and empty again. This proves persistence and the fixture’s empty listing; it does not claim arbitrary agent-created files would be cleaned. | Before | After | | --- | --- | | [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e) | [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340) | | 
{"event":"server.exited","pid":1726757,"exitCode":130,"signal":null}
{"event":"directory.list","label":"after-stop","path":"B","exists":false,"entries":null}
{"event":"server.start","pid":1727610,"cwd":"H","base":"CAPTURE/before/base-local"}
{"event":"request","pid":1727905,"method":"initialize","processCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1727910,"method":"initialize","processCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-test","version":"0.0.0"},"requestId":1073741824}
{"event":"directory.list","label":"after-stop","path":"B","exists":false,"entries":null}
| 
{"event":"server.exited","pid":1728600,"exitCode":130,"signal":null}
{"event":"directory.list","label":"after-stop","path":"B","exists":true,"entries":[]}
{"event":"server.start","pid":1729816,"cwd":"H","base":"CAPTURE/after/base-local"}
{"event":"request","pid":1730120,"method":"initialize","processCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-auth","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1730121,"method":"initialize","processCwd":"B","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-test","version":"0.0.0"},"requestId":1073741824}
{"event":"directory.list","label":"after-stop","path":"B","exists":true,"entries":[]}
| ## R7 — Real project thread and completed turn **Unchanged: P on both sides.** The project is created through `projects.mutate`, followed by `thread.create` and `message.dispatch` through `orchestration.dispatchCommand`. The real thread child and session cwd remain P with five watches. The prompt returns `end_turn`; a persisted `run.updated` event reports `completed`, and a final projection is read. P intentionally has no Git repository, so both sides record the same `missing` checkpoint result; this does not prevent a completed prompt/run. | Before | After | | --- | --- | | [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e) | [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340) | | 
{"event":"rpc.call","rpcId":"6","tag":"projects.mutate","payload":{"type":"project.create","commandId":"command:project-create","projectId":"project:synthetic-capture","title":"Synthetic capture project","workspaceRoot":"P"}}
{"event":"rpc.call","rpcId":"8","tag":"orchestration.dispatchCommand","payload":{"type":"thread.create","commandId":"command:thread-create","threadId":"thread:synthetic-capture","projectId":"project:synthetic-capture","title":"Synthetic cwd capture","createdBy":"user","creationSource":"web","modelSelection":{"instanceId":"proof-acp","model":"synthetic-model"},"runtimeMode":"full-access","interactionMode":"default","branch":null,"worktreePath":null,"createdAt":"2026-11-10T10:09:46.400Z"}}
{"event":"rpc.call","rpcId":"10","tag":"orchestration.dispatchCommand","payload":{"type":"message.dispatch","commandId":"command:message-dispatch","threadId":"thread:synthetic-capture","messageId":"message:synthetic-capture","text":"Return the synthetic completion.","createdBy":"user","creationSource":"web","attachments":[],"dispatchMode":{"type":"start_immediately"},"createdAt":"2026-11-10T10:09:46.414Z"}}
{"event":"request","pid":1727580,"method":"session/new","processCwd":"P","sessionCwd":"P","watches":5,"procInotifyWatches":5,"clientInfo":{"name":"t3-code","version":"0.0.0"},"requestId":1073741825}
{"event":"request","pid":1727580,"method":"session/prompt","processCwd":"P","watches":5,"procInotifyWatches":5,"clientInfo":{"name":"t3-code","version":"0.0.0"},"requestId":1073741826}
{"event":"response","pid":1727580,"method":"session/prompt","result":{"stopReason":"end_turn"}}
{"event":"run.updated","sequence":31,"status":"completed"}
| 
{"event":"rpc.call","rpcId":"6","tag":"projects.mutate","payload":{"type":"project.create","commandId":"command:project-create","projectId":"project:synthetic-capture","title":"Synthetic capture project","workspaceRoot":"P"}}
{"event":"rpc.call","rpcId":"8","tag":"orchestration.dispatchCommand","payload":{"type":"thread.create","commandId":"command:thread-create","threadId":"thread:synthetic-capture","projectId":"project:synthetic-capture","title":"Synthetic cwd capture","createdBy":"user","creationSource":"web","modelSelection":{"instanceId":"proof-acp","model":"synthetic-model"},"runtimeMode":"full-access","interactionMode":"default","branch":null,"worktreePath":null,"createdAt":"2026-11-10T10:10:01.100Z"}}
{"event":"rpc.call","rpcId":"10","tag":"orchestration.dispatchCommand","payload":{"type":"message.dispatch","commandId":"command:message-dispatch","threadId":"thread:synthetic-capture","messageId":"message:synthetic-capture","text":"Return the synthetic completion.","createdBy":"user","creationSource":"web","attachments":[],"dispatchMode":{"type":"start_immediately"},"createdAt":"2026-11-10T10:10:01.123Z"}}
{"event":"request","pid":1729733,"method":"session/new","processCwd":"P","sessionCwd":"P","watches":5,"procInotifyWatches":5,"clientInfo":{"name":"t3-code","version":"0.0.0"},"requestId":1073741825}
{"event":"request","pid":1729733,"method":"session/prompt","processCwd":"P","watches":5,"procInotifyWatches":5,"clientInfo":{"name":"t3-code","version":"0.0.0"},"requestId":1073741826}
{"event":"response","pid":1729733,"method":"session/prompt","result":{"stopReason":"end_turn"}}
{"event":"run.updated","sequence":31,"status":"completed"}
| ## R8 — Session-management caller cwd **Unchanged: P on both sides.** `server.listAcpRegistrySessions` forwards the project’s workspace root into the shared management runtime. The management initialize client name, actual process cwd, request cwd, empty agent result and successful RPC result are all shown. Other operations sharing this factory were not separately executed; internal management logout remains source coverage only. | Before | After | | --- | --- | | [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e) | [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340) | | 
{"event":"rpc.call","rpcId":"7","tag":"server.listAcpRegistrySessions","payload":{"instanceId":"proof-acp","projectId":"project:synthetic-capture"}}
{"event":"request","pid":1727535,"method":"initialize","processCwd":"P","watches":5,"procInotifyWatches":5,"clientInfo":{"name":"t3-code-session-manager","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1727535,"method":"session/list","processCwd":"P","sessionCwd":"P","watches":5,"procInotifyWatches":5,"clientInfo":{"name":"t3-code-session-manager","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1727535,"method":"session/list","result":{"sessions":[]}}
{"event":"rpc.complete","rpcId":"7","tag":"server.listAcpRegistrySessions","value":{"sessions":[],"nextCursor":null,"canLoad":false,"canResume":false,"canDelete":false}}
| 
{"event":"rpc.call","rpcId":"7","tag":"server.listAcpRegistrySessions","payload":{"instanceId":"proof-acp","projectId":"project:synthetic-capture"}}
{"event":"request","pid":1729702,"method":"initialize","processCwd":"P","watches":5,"procInotifyWatches":5,"clientInfo":{"name":"t3-code-session-manager","version":"0.0.0"},"requestId":1073741824}
{"event":"request","pid":1729702,"method":"session/list","processCwd":"P","sessionCwd":"P","watches":5,"procInotifyWatches":5,"clientInfo":{"name":"t3-code-session-manager","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1729702,"method":"session/list","result":{"sessions":[]}}
{"event":"rpc.complete","rpcId":"7","tag":"server.listAcpRegistrySessions","value":{"sessions":[],"nextCursor":null,"canLoad":false,"canResume":false,"canDelete":false}}
| ## E5 — Relative registry executable override **Before shows the bug; after fixes it.** Both sides execute the same relative registry override and retain the npx distribution’s harmless argument and environment marker. No package is installed. The valid synthetic cached index is loaded through the catalog’s cached-index path; no search/refresh/prepare RPC is issued. The cache SHA-256 stays `b97ea4082c9f0e30c3e109219ccc14e4ae2d713b91a80988424066ee5f1d515f` before and after each run, so no refresh replaced the fixture. This does not claim package-install or unoverridden binary coverage. | Before | After | | --- | --- | | [ca796d5211](https://git.cafe/pingdotgg/t3code/commit/ca796d52119592de771d8ccfa955d70dba84d11e) | [db9f0faa91](https://git.cafe/pingdotgg/t3code/commit/db9f0faa91e4cfdd62af3ace9c2d42ffae517340) | | 
{"source":"registry","agentId":"synthetic-registry","commandPath":"../bin/stub-acp-agent.mjs","distribution":"npx","args":["--synthetic-distribution"],"env":{"STUB_DISTRIBUTION_MARKER":"retained-registry-environment"}}
{"event":"server.start","pid":1728024,"cwd":"H","base":"CAPTURE/before/base-registry"}
{"event":"spawn","pid":1728444,"argv":["/home/user/.local/share/vite-plus/js_runtime/node/26.13.0/bin/node","CAPTURE/fixture/bin/stub-acp-agent.mjs","--synthetic-distribution"],"script":"CAPTURE/fixture/bin/stub-acp-agent.mjs","identity":"eecb49a34c57fbb3b3ad300b4377a438d7015a0303245d20335cb2d25bdc653e","distributionMarker":"retained-registry-environment","processCwd":"H","watches":1666,"procInotifyWatches":1666}
{"event":"request","pid":1728449,"method":"session/new","processCwd":"H","sessionCwd":"H","watches":1666,"procInotifyWatches":1666,"clientInfo":{"name":"t3-code-provider-test","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1728449,"method":"session/new","sessionId":"synthetic-session-1728449"}
| 
{"source":"registry","agentId":"synthetic-registry","commandPath":"../bin/stub-acp-agent.mjs","distribution":"npx","args":["--synthetic-distribution"],"env":{"STUB_DISTRIBUTION_MARKER":"retained-registry-environment"}}
{"event":"server.start","pid":1730362,"cwd":"H","base":"CAPTURE/after/base-registry"}
{"event":"spawn","pid":1730834,"argv":["/home/user/.local/share/vite-plus/js_runtime/node/26.13.0/bin/node","CAPTURE/fixture/bin/stub-acp-agent.mjs","--synthetic-distribution"],"script":"CAPTURE/fixture/bin/stub-acp-agent.mjs","identity":"eecb49a34c57fbb3b3ad300b4377a438d7015a0303245d20335cb2d25bdc653e","distributionMarker":"retained-registry-environment","processCwd":"B_registry","watches":1,"procInotifyWatches":1}
{"event":"request","pid":1730834,"method":"session/new","processCwd":"B_registry","sessionCwd":"B_registry","watches":1,"procInotifyWatches":1,"clientInfo":{"name":"t3-code-provider-test","version":"0.0.0"},"requestId":1073741825}
{"event":"response","pid":1730834,"method":"session/new","sessionId":"synthetic-session-1730834"}
| ## What else changed - No additional functional difference was observed in the exercised protocol responses, sign-in outcomes, logout result, model discovery, session list, synthetic prompt response or persisted run outcome. Both sides produced 15 local children across the integrated run/restart, two registry children, and 31 thread subscription messages. The same script identity was executed on both sides. - The intended cwd relocation changes background `session/new` cwd as well as process cwd, reduces both watcher metrics from 1,666 to 1, and creates/reuses B. Project process/session cwd and its five-watch metric remain unchanged. - Incidental values differ: source SHA/checkout, fresh base/log paths, loopback port, server and child PIDs/PPIDs, timestamps, auth expiries, session IDs derived from PIDs, flow/event/session UUIDs, and interleaving of concurrent background events. The synthetic payloads, directory tree, executable bytes and registry distribution args/env are the same. - Both source-server runs emit the environment’s unavailable native-telemetry-sidecar warning. Both project runs use a non-Git P and have missing checkpoints. These are shared fixture/environment limits. No test runner was substituted for runtime capture. - The after checkout was clean when capture began. A separate process subsequently added ten lines to `AcpRegistrySupport.test.ts`; After capture completed, that change was committed as [3bb686070c](https://git.cafe/pingdotgg/t3code/commit/3bb686070ca455657e4a8fa32765692cf6d02040). The only difference from the captured head is that test file; production modules are unchanged. This report remains pinned to the requested capture head, not the later commit. The capture worker made no checkout edits. ## Unverified rows and scope | Row | Status and reason | | --- | --- | | W1 | `cannot-verify windows`: no native Windows cwd/PTY/restart host in this capture. | | W2 | `cannot-verify windows`: no native Windows drive-relative, root-relative, ordinary-relative or UNC executable launch capture. | | W3 | `cannot-verify windows`: no native Windows reparse/symlink-plus-`..` executable identity capture. | There are **no missing required POSIX rows**. Optional E1/E3/E4/E6/E7/E8 were not run separately. R1 supplies the integrated relative-local launch required alongside E2. This report does not claim real third-party agent behavior, real package installs, Windows proof or native macOS watcher proof. ## Evidence and reproducible scripts The following is the `ghdrop upload -m` output, pasted verbatim: [before-runtime.ndjson](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/5ccb4ab4c0e580d3/before-runtime.ndjson) [after-runtime.ndjson](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/2f881045ab63594c/after-runtime.ndjson) [stub-acp-agent.mjs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/5da320b9d5d8881f/stub-acp-agent.mjs) [rpc-driver.mjs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/b5e6a7ed54d3c9d6/rpc-driver.mjs) [capture-runner.mjs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/a1319c644bcd68fb/capture-runner.mjs) [before-local-settings.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/bd2f3a9d1b4df32e/before-local-settings.json) [after-local-settings.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/9779392af62dc712/after-local-settings.json) [before-registry-settings.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/1532b7fc1e0484fa/before-registry-settings.json) [after-registry-settings.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/418da468ea34e384/after-registry-settings.json) [registry-fixture.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/a9e51fc0593fc76c/registry-fixture.json) [capture-manifest.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/aab438521d1749f9/capture-manifest.json) Run `node capture-runner.mjs` with the uploaded stub and RPC driver in the same scratch directory after preparing the two source checkouts named in the script. It creates a new timestamped fixture/base directory and records every spawned server PID. Its credential-issuing CLI runs only against its own synthetic base; credentials are held in memory and never written to the transcript. The settings and registry fixtures are uploaded above. The runner includes deadline guards, not elapsed-time assertions or delay-based completion; auth and turn completion come from RPC streams and file events. ## Cleanup and verification Every captured PID from all attempts has exited: nine source servers and 61 synthetic stub invocations; no process was killed by pattern. The final complete run accounts for six servers and 34 stubs. All servers were stopped by their captured spawn handles and awaited to completion. The detached before worktree was removed. The after checkout was not edited by this worker. Scratch/raw originals remain under the allocated capture directory; nothing was committed or pushed. Disk space after capture: 242 GiB available. AI-assisted; verified with the tests and tools listed above. FRICTION: ```text tool | The server package does not expose ws directly to a scratch driver; the first connection attempt could not resolve it. | Resolve ws through the existing @effect/platform-node dependency. brief | The published ACP stub only handled startup, so it could not capture auth, PTY, logout, thread completion or management. | Supply the extended stub and RPC driver included with this report. runbook | The scratch thread driver initially supplied createdBy as an object, then watched a nonexistent completion event name. | Use the current contracts: createdBy="user" and run.updated payload.status="completed"; the final full run uses those schemas. other | Another process modified a test file during evidence collection and committed it after capture. | Freeze checkout edits during capture; no production file changed, and both transcript headers record the agreed capture SHA. infra | Native Windows execution is unavailable on this Linux host. | Run W1–W3 on a Windows host; they remain cannot-verify windows. ``` Captured 9/9 required rows (R1–R8, E5); W1–W3 cannot-verify windows.