# Stale T3 Connect denial: manual proof

Base: 3e1b7c4e93d7f3d035d14296ebf45e373914ae8c
Head: c5559c2fb32e65f885da413aa637e89f28fbda7e

Environment: separate real development servers and fresh databases, test T3 Connect relay/Clerk account; iPhone 17 Pro simulator, iOS 27.2, T3 Code Dev, light appearance, 402x874 logical viewport. Both servers and mobile bundles were run from isolated checkouts. The fix only changes server files; mobile source and native fingerprint match between revisions. No test assertions or mocked server responses were used.

The approvers were the real web client (Chromium, 1280x800) and the real native iOS client, paired with access:write. A browser driver creates a new P-256 device key and sends real DPoP requests through the test relay. It deliberately does not retry its bootstrap exchange between approval and denial.

1. Sign the isolated host into the test stage with `t3 connect login --headless`, then `t3 connect link`, and restart it. Never use the production relay.
2. Pair the web and iOS clients with management permissions. Enable Require approval for new T3 Connect devices. Give the mobile connection the synthetic label Approval demo. Open Chats with one synthetic empty thread.
3. In the signed-in web page, evaluate device-driver.js. It uses the app's configured relay and Clerk JWT options, makes a new device key, connects through the real relay, and attempts bootstrap exchange. The server returns HTTP 403 connect_approval_pending. Both approvers show the same verification code.
4. Start the mobile device recording. Click Approve on the web toast (`button[data-slot="toast-action"]`). Do not consume the approved credential yet.
5. Tap the still-open native alert's Deny immediately, then capture the result and leave recording running long enough to include it.
6. Inspect Settings > Sharing & access > T3 Connect devices on the web client. Match its trusted row to the verification code in the mobile recording.

Base final run: code 3FTR-9ACJ. Deny silently closes the alert. The matching device remains Trusted in the real web UI.
Head final run: code E7YA-6ZQU. Deny shows Request no longer waiting / It expired or was answered elsewhere. The matching device remains Trusted. Exchanging its original approved bootstrap credential after denial returns HTTP 200 with token_type DPoP.

The screenshots show those final states. Each mobile still was checked against a second pixel-identical capture taken more than 500ms later. Trusted-list images are crops of actual web screenshots to exclude unrelated machine details. Videos are real device recordings, scaled to 402x874 and trimmed to their first 10 seconds; both include the denial outcome. No UI text was replaced.

Limitations: the approving desktop surface was web, not the Electron shell. The newly requesting device was the real relay/HTTP driver, not a third GUI client with a continuously connected WebSocket. The iPhone approver was paired directly to the isolated host. An initial exploratory run consumed the approved credential before denial and correctly displayed the gone message on base; the final runs follow approve then deny, with no intermediate credential consumption.

No scenario was used because this reproduction requires native alert state plus real T3 Connect device approval state, which t3.project/t3.thread do not create.
