Evidence drivers for Send now failure handling

Run each .e2e.ts file from scripts/scenarios in current origin/main with scenarios:prove, using base [26f70e72fa](https://github.com/pingdotgg/t3code/commit/26f70e72fa4ca3fb4144b46d3001f5584e030ebe) and head [a5eb233223](https://github.com/pingdotgg/t3code/commit/a5eb23322332babaea604daa019856d3dd9f83a8). Every file contains one scenario. No product code was modified.

All servers use T3CODE_DEV_SEED=0 and synthetic projects/threads created through the scenario helpers. Web uses Chromium, 1280x800, light theme. iOS uses the cached native development client, an iPhone 18 Pro from the device pool, 402x874 logical viewport, light theme. Both commits load their own server and client source.

The web driver panel is added by the evidence script and labeled DRIVER. It renders an observed real WebSocket response; no response or error is fabricated. Workspace text is masked to [workspace].

queued-send-now: starts a streaming Replay showcase turn, queues a follow-up with Control+Enter, clicks Stop then Send now on the next event-loop tick (0ms timer), observes the real promote-to-steer rejection, captures the unchanged queue, then clicks Send now again and captures the accepted retry. Replay runs the normal orchestration path; it does not execute a real sleep subprocess.

queued-send-resume: stops the active run, then injects a real thread.archive command immediately before the actual UI queued-run.start request on the authenticated socket. The server rejects the resume because the thread is no longer active. This supplemental case verifies the resume branch notification, not queue retention after archive.

queued-send-interrupted: stops the active run, then sends the standard RPC Interrupt frame immediately after the real UI queued-run.start request. It requires that request's FIRST server Exit to be a Failure with Interrupt-only cause. Both commits should stay silent; this is a negative control, so scenarios:prove correctly exits 1 because base also passes.

queued-send-mobile: a pending-question Replay turn keeps the native run active. The CLI queues /compact. Tapping native Send now produces the real server validation rejection that compaction must run separately. After capturing the alert (or its absence), dismiss the alert if present, capture the retained queue, stop the active run, and retry Send now. The retry is accepted and the queue row is removed; Replay does not implement compaction, so this does not claim that compaction itself completes successfully.

Runner configuration: actionTimeout was increased from 30000 to 180000 milliseconds to allow installation of the cached native client. Mobile recording is explicitly started after pairing and stopped after retry, avoiding installation footage and a large video download. Native pool environment variables are inherited with T3_SCENARIO_INHERIT_ENV='SIMLOCK_*,AGENT_DEVICE_*,EXPO_TOKEN'.
