# Delegated result delivery proof

Use a checkout of the public [T3 Code repository](https://github.com/pingdotgg/t3code) at runner commit [721542cac7](https://github.com/pingdotgg/t3code/commit/721542cac7). The application revisions under test are base [634ee43deb](https://github.com/pingdotgg/t3code/commit/634ee43deb6d5fc0feae77153d33df1e97ffb303) and fix [6b6cc8cd65](https://github.com/pingdotgg/t3code/commit/6b6cc8cd65cf2e498d8139cca9e47a354655ea45).

Extract this archive at that checkout's root. It includes the scenario, its local harness imports (`t3.ts`, `shell.ts`, `start-app.ts`, `e2e.config.ts`, and `prove-scenario.ts`), and dependency manifests. The external `e2e` package is declared in `scripts/package.json` and installed by `vp i`; it is not a private harness file.

```sh
vp i
node scripts/node_modules/playwright-core/cli.js install --only-shell chromium ffmpeg
T3CODE_DEV_SEED=0 vp run scenarios:prove scripts/scenarios/delegated-result-once.e2e.ts --base 634ee43deb6d5fc0feae77153d33df1e97ffb303 --head 6b6cc8cd65cf2e498d8139cca9e47a354655ea45
```

The runner installs and runs each application revision in its own temporary worktree. Its proof is written to `scripts/.e2e/prove/proof.json`. Add `--upload-command "ghdrop upload"` when uploads are configured.

The single scenario runs the actual web client, server, provider adapters, MCP delegation, and persistence. It creates a synthetic git project and uses two embedded local replay binaries: an ACP parent and a Claude SDK child. No model account or OAuth session is needed. The child starts real Node subprocesses, and their exits emit native background-task completion frames. These produce the application's own notification and follow-up runs; the driver does not insert events or database rows.

The parent echoes the application's delegated wake text, trimming only the surrounding harness instructions. The driver counts actual delegated wake prompts, separately from normal server-restart continuation prompts. It covers an unchanged self-started result, a changed result with the original-task label, an identical user-requested result, an answered delivery interrupted by restart, and an unanswered delivery interrupted by restart.

Both runs use a light theme and a 1600 by 1000 viewport. During each server restart the browser visits a neutral local gate page, then recreates its document while preserving client storage; this avoids a renderer crash seen when repeatedly reloading the active thread. The server restarts through its dev watcher by changing the entry file's timestamp, without changing its contents or database. Captures wait for message syncing to finish.

All fixture text and project data are synthetic. The scenario and this bundle are scratch proof artifacts, not production changes.
