# ACP v2 Registry work-state proof

Environment: Linux web client, scenario runner Chromium, 1280 x 800, light theme. Each revision starts a fresh isolated T3 home. One synthetic git project (ACP demo), one fixed thread title (ACP v2 proof). No real user data, provider credentials, or paid model.

This is a deterministic ACP v2 protocol replay through the actual Local ACP Registry provider, server, orchestration, database, and browser. It is not a real codex-acp run and does not actually create a model goal. The fixture supplies the goal continuation's protocol events.

## Repeat

Use a checkout of current main with the scenario runner and run `vp i`. Copy acp-v2-work-state.e2e.ts and acp-v2-proof-agent.mjs into scripts/scenarios/. Replace scripts/scenarios/start-app.ts with the supplied start-app.ts; its only change from the runner is registration of acpProof as an enabled local ACP Registry provider using the fixture. The app revisions themselves are unchanged.

Run:

```sh
T3CODE_DEV_SEED=0 vp run scenarios:prove scripts/scenarios/acp-v2-work-state.e2e.ts --base ff75365c7d0fd1df24649ac75719893bb8c33f31 --head db9a210ea2583982615e4313cf575098b327d6da --upload-command "ghdrop upload"
```

The one scenario creates the project and starts the first turn through T3's CLI with the fixed title, opens the thread by link, submits the goal-continuation prompt through the composer, and captures the result. The first prompt has a user_message_chunk echo and returns ACP_FIRST_OK. The second prompt has a whole-message user_message echo containing the exact outbound prompt blocks, emits PHASE_ONE_DONE, then idle; 2.5 seconds later it emits running, PHASE_TWO_DONE, idle, without another session/prompt request. Both sides get exactly the same fixture and steps.

Observed: base displays PHASE_ONE_DONE but drops PHASE_TWO_DONE. Head displays both, removes Stop generation, and retains PHASE_TWO_DONE after reload. The runner exited 0, with failsOnBase=true and passesOnHead=true. The base failed its visibility assertion for PHASE_TWO_DONE, not setup or navigation.

Prompt echo limitation: the full second prompt appears once on BOTH revisions. The specified merge-base already contains the outgoingPrompt/content-equality echo reconciliation also present on head. This capture therefore proves the autonomous-work change only, and does not establish a duplicate-message regression on this commit pair.

The MP4s are the runner's recordings trimmed to start at the composer interaction, excluding sign-in. Head also shows the reload check. Final screenshots are the original runner captures. No product code was modified and no unit tests are used as evidence.
