Real-app proof driver

Both runs use fresh scenario homes, synthetic projects, Chromium at 1280x800, and the light theme. No live database is copied.

Place auto-send-during-stop.e2e.ts in scripts/scenarios/. Apply provider-fixture.patch to the scenario launcher. Place delay-replay.mjs in the directory named factory-pr-34163-evidence-1 under the system temporary directory (create it first). Then run:

vp i
T3CODE_DEV_SEED=0 vp run scenarios scenarios/auto-send-during-stop.e2e.ts --target web --action-timeout 15000

Run the identical files in separate base and head checkouts. The provider-only fixture delays the replay cancellation response by 8 seconds so the driver can reliably hit the stopping window. It substitutes a synthetic workspace path in replay tool output before display. Application server and client code are unchanged.

The fixture saves each replay process's own MCP credential locally with restricted permissions. The driver uses Thread B's live credential to invoke the real MCP endpoint. These private credential files are not evidence and must not be shared.

The driver starts a turn in Thread A, queues a user follow-up through the composer with Control-click, clicks Stop, then sends from Thread B with mode auto and clientRequestId auto-during-stop. It repeats that same payload, then sends an explicit steer with a different request id. The driver records actual MCP responses and waits for Stop to finish. It captures identical final screenshots 500 milliseconds apart and checks the queue is still held, contains two messages, and contains one automatic follow-up.

Before: auto is rejected while stopping, retry returns the stored rejection, and only the original queued message remains.
After: both calls return delivery queued with the same messageId and runId; both queued messages remain held after Stop. Explicit steering is rejected on both sides.

The MP4 clips remove only initial setup/loading from the full browser recordings.

AI-assisted; verified with the tests and tools listed above.