# Pending request steering proof

Surface: real web client, Chromium, Linux, 1280 x 800, light theme. Separate fresh dev homes; no production database was read or copied. Provider: built-in Replay (dev), question and approval recordings, supervised runtime mode.

For each commit, install with `vp i`, then start the real app with `T3CODE_DEV_SEED=0 node scripts/scenarios/start-app.ts web "$PWD/.t3/manual" 127.0.0.1 <web-port>`. This helper disables paid providers and writes a reusable pairing path to the dev home. Pair before recording; do not publish the pairing path.

`seed.sh` creates the initial synthetic project and question. `mcp-call.mjs` is a generic external MCP driver. Create its dev-only credential with `node apps/server/src/bin.ts auth session issue --subject mcp-client --token-only --ttl 1h --base-dir .t3/manual > .t3/manual/mcp-token`; never upload that token file. `seed-proof.mjs <home> <project-id> question` and `seed-proof.mjs <home> <project-id> approval` create the matched proof threads through the real server, then queue `First queued follow-up` and `Promoted queued follow-up`.

Matched recordings: open the seeded thread, wait for its question/approval, start recording, wait two seconds, click the second queued message's Send now button (`[data-thread-queue] li:nth-child(2) button:has-text("Send now")`), wait four seconds, stop recording. Each side used this same sequence. Base visibly marks the original turn Superseded attempt / Cut off by a steer. Replay starts a replacement request. Head preserves the original request and puts Promoted queued follow-up ahead of First queued follow-up.

Delivery recordings on head: answer the original question by clicking Strict schemas (Recommended), then answer each replayed follow-up question until idle. The promoted message runs before the original first queued message. Approval delivery: click Approve; the original turn completes and the promoted follow-up begins, while First queued follow-up remains queued.

Additional exploratory check: `mcp-send.mjs <home> <thread-id> auto "Automatic MCP follow-up"` queued on both commits with replay's ACP capabilities. This does not prove the native Claude auto-steering path.

The attempted one-test scenario was run twice. Its first run failed at a sidebar text locator, and the corrected run reached a choice-only replay question whose composer is not editable. Neither runner result is claimed as proof. The manual recordings above are the evidence.

Scope: shared server guard through queued-message promotion, questions, approvals, answerability and queued delivery. Native Claude priority-now behavior, a separate composer message during a pending question, and an auto send from a real second agent thread remain unverified.