# E7 runtime evidence for [#32950](https://git.cafe/pingdotgg/t3code/pull/32950)

Rows captured / rows asked: **1 / 1**. E7 is covered by real before/after T3 source-server runs, with the same synthetic uvx package fixture and RPC driver.

Environment: Linux 6.8.0-117-generic x86_64; Node v26.12.1. Before [fa2f4ff2a2](https://git.cafe/pingdotgg/t3code/commit/fa2f4ff2a2bac5ac92e07749f6b83b0003d642a0); after [cb3c2692f5](https://git.cafe/pingdotgg/t3code/commit/cb3c2692f5340a2b9d960204a7d192dc726b4037). Server-only capture; no UI paths or native Windows claims.

## Fixture and method

Registry source, `agentId=proof-agent`, distribution `uvx`, package `proof-agent==1.0.0`, and an explicitly empty `commandPath` (no override). A synthetic executable named `uv` answers `tool list` and `tool dir --bin`; no install command or real registry/package download occurs. The managed bin directory is empty, while provider PATH contains `../bin`, exposing the ACP stub as `../bin/proof-agent`. Both persisted package receipts contain that relative executable. Thus these launches execute the managed-package resolution branch, rather than the local-command or override branch.

H (server process cwd) = `/tmp/lead-32950-r2/capture/20261110-e7/run-2026-11-10T11-12-35-140Z/fixture/home`.
B (after background cwd) = `/tmp/lead-32950-r2/capture/20261110-e7/run-2026-11-10T11-12-35-140Z/after/base/userdata/acp-registry/background-cwd`.

Each source server uses its own fresh `--base-dir`, `T3CODE_DEV_SEED=0`, synthetic settings/index, and an isolated synthetic HOME. No real T3 data or provider credentials were copied. A temporary Node preload observes synthetic child launches only. Linux AgentScope wraps each agent in `/bin/sh`; the transcript records its exact arguments, target command, cwd, and child PID. The wrapper then execs the same PID that the stub records. This observer does not replace resolution or spawning and neither source checkout was edited.

## Result

| Side | Server PID | Discovery / probe / sign-in PIDs | Resolved target | Actual agent cwd | Startup probe / discovery | Agent sign-in |
| --- | --- | --- | --- | --- | --- | --- |
| Before | 563751 | 563859 / 563888 / 564148 | `../bin/proof-agent` | H | success / success | succeeded |
| After | 564164 | 564361 / 564398 / 564470 | `H/../bin/proof-agent` (literal prefix, preserving `..`) | B | success / success | succeeded |

All six final-run ACP processes execute identical stub SHA-256 `eecb49a34c57fbb3b3ad300b4377a438d7015a0303245d20335cb2d25bdc653e`. All retain `--synthetic-distribution` and `STUB_DISTRIBUTION_MARKER=retained-registry-environment`. Probe and sign-in verification `session/new` cwd agrees with process cwd. Both watcher counters are 5 before and 1 after. The after background directory exists; the before one does not. No other unexpected functional difference or RPC/spawn error was observed. Package-manager queries retain H as their cwd on both sides.

Key transcript excerpts below are verbatim substrings, with one-based NDJSON line numbers.

**Before:** [before-e7-runtime.ndjson](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/706f6aa500f1845e/before-e7-runtime.ndjson)

- L33 package receipt: `"distribution":"uvx"`, `"executablePath":"../bin/proof-agent"`.
- L23 observed probe target: `"targetCommand":"../bin/proof-agent"`.
- L24 actual probe process: `"processCwd":"/tmp/lead-32950-r2/capture/20261110-e7/run-2026-11-10T11-12-35-140Z/fixture/home","watches":5,"procInotifyWatches":5`.
- L32 startup: `"probe":"success","authDiscovery":"success"`; actual probe initialize/session responses are L26 and L28.
- L59 sign-in: `"phase":"succeeded"`, `"message":"Sign-in complete."`; authenticate response is L51 and verification session response is L53.

**After:** [after-e7-runtime.ndjson](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/2aeb243843d4c0d5/after-e7-runtime.ndjson)

- L31 package receipt: `"distribution":"uvx"`, `"executablePath":"../bin/proof-agent"`.
- L23 observed probe target: `"targetCommand":"/tmp/lead-32950-r2/capture/20261110-e7/run-2026-11-10T11-12-35-140Z/fixture/home/../bin/proof-agent"`.
- L24 actual probe process: `"processCwd":"/tmp/lead-32950-r2/capture/20261110-e7/run-2026-11-10T11-12-35-140Z/after/base/userdata/acp-registry/background-cwd","watches":1,"procInotifyWatches":1`.
- L30 startup: `"probe":"success","authDiscovery":"success"`; actual probe initialize/session responses are L26 and L28.
- L59 sign-in: `"phase":"succeeded"`, `"message":"Sign-in complete."`; authenticate response is L51 and verification session response is L53.

## Uploaded reproduction files

[e7-capture-runner.mjs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/24cfd26057a3d779/e7-capture-runner.mjs)
[synthetic-uv.mjs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/6310dbe11e046d29/synthetic-uv.mjs)
[spawn-observer.mjs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/6d087c09238ae190/spawn-observer.mjs)
[rpc-driver.mjs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/1b5bc42a89961393/rpc-driver.mjs)
[stub-acp-agent.mjs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/6f83a56735877b13/stub-acp-agent.mjs)

Before settings: [e7-settings.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c7b287dfa4bb4421/e7-settings.json)

After settings: [e7-settings.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/dae3c17f2570b960/e7-settings.json)

Registry: [e7-registry.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/6b3469b2692b9a34/e7-registry.json)

Initial observer attempt: [initial-before-observer-attempt.ndjson](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/8c14f4036d174bfd/initial-before-observer-attempt.ndjson). It reached successful probe/sign-in but its observer only selected executable names, missing the Linux shell wrapper; runner validation rejected it. The final pair above was repeated with the corrected wrapper-argument observer.

Cleanup verification: [cleanup-verification.json](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/ad3473bd9f1efb41/cleanup-verification.json). All 36 recorded server/manager/agent PIDs across both attempts have exited. Servers received tracked-PID SIGTERM (application exit code 130); the temporary before worktree was removed with the prescribed command. The after checkout remains clean and unchanged. Evidence remains in the assigned scratch directory. Uploads contain only synthetic data and synthetic model names; private startup logs/auth material were excluded. No required evidence remains missing.

FRICTION:

tool | Initial spawn observer filtered only command names and missed the Linux AgentScope shell wrapper; its post-run assertion rejected otherwise successful runtime activity. | Observe the wrapper target argument as well; the final before/after pair uses the corrected observer.