# Named secret legacy-client proof

Use the scenario runner from commit 370b1fde77 or newer. Install its dependencies with `vp i`.

Export the entire legacy client source at commit 7085c47776 into a fresh scratch directory (using `git archive 7085c47776 | tar -x -C "$legacy"`) and run `vp i` there. This uses the actual pre-fields web/client-runtime/contracts code, without mocking its form or its submitted answer.

Apply legacy-client-runner.patch to scripts/scenarios/start-app.ts. It changes only the web process checkout to T3_SCENARIO_LEGACY_CLIENT; the server still comes from the base or head commit selected by scenarios:prove. Put named-secret-legacy-client.e2e.ts in scripts/scenarios/.

Run with the absolute legacy source directory in T3_SCENARIO_LEGACY_CLIENT:

```sh
T3_SCENARIO_LEGACY_CLIENT="$legacy" T3_SCENARIO_INHERIT_ENV=T3_SCENARIO_LEGACY_CLIENT T3CODE_DEV_SEED=0 vp run scenarios:prove scripts/scenarios/named-secret-legacy-client.e2e.ts --base 7d3677fe70b39d9207ab5470a5ef9a02ee8117e5 --head 314045b856e87727c2f5ecedc5774df01a922115 --upload-command 'ghdrop upload'
```

The deterministic ACP replay calls the real request_secret MCP service with the reporter's exact arguments. No paid provider is needed. The app's real UI fills the legacy password input and clicks Save securely. The agent reads the returned files.test_field and verifies the exact synthetic value before confirming delivery in chat. Both runs create fresh data through the app APIs. Chromium viewport is 1280x800, light theme, Linux web. The iOS binary is not exercised.
