# Refreshed runtime proof — SUFFICIENT within stated scope

PR [#23489](https://github.com/pingdotgg/t3code/pull/23489), exact HEAD [b459078b4b](https://github.com/pingdotgg/t3code/commit/b459078b4be677f49a3e2c10d9091c48f5ed7e17). Captured 2026-10-22 UTC by gpt-6.1-sol in Codex. Checkout /home/ubuntu/wt/issue-3714 clean before and after. No implementation edits, commit, push, forge commands, or dev server. App-only PR association was registered.

## Execution and identity

Unchanged runtime.mjs and compatibility.mjs copied from /tmp/issue-3714-evidence into /tmp/issue-3714-bot-evidence; old artifacts remain untouched. Invocations:

```sh
PLAYWRIGHT_BROWSERS_PATH=/tmp/tmp.LFIo8iGZQi T3CODE_SERVER_BROWSER_SANDBOX=0 node /tmp/issue-3714-bot-evidence/runtime.mjs /home/ubuntu/wt/issue-3714
PLAYWRIGHT_BROWSERS_PATH=/tmp/tmp.LFIo8iGZQi T3CODE_SERVER_BROWSER_SANDBOX=0 node /tmp/issue-3714-bot-evidence/compatibility.mjs /home/ubuntu/wt/issue-3714
PLAYWRIGHT_BROWSERS_PATH=/tmp/tmp.LFIo8iGZQi T3CODE_SERVER_BROWSER_SANDBOX=0 vp test run apps/server/src/preview/ServerBrowserPage.test.ts apps/server/src/mcp/PreviewAutomationBroker.test.ts
```

All exit 0. Tests: 2 files, 42 passed (42), 20.06 seconds. Test source hashes and the committed cause assertion are in test-source-proof.txt. The passing test “tells a click target that matches nothing from one that never becomes clickable” explicitly asserts absent.cause has name TimeoutError.

Runtime identity: Node v26.12.1, Linux x64, real installed Chrome for Testing headless shell 154.0.8037.92. Real PreviewAutomationBroker -> ServerBrowser -> ServerBrowserPage -> Chromium, temporary loopback HTML fixture and isolated state. Fixture environment identity and executable selection are dependency injections; browser/host are real. Runtime uses the driver's installed binary; focused tests use the requested bundled-browser directory. No live user data or credentials used. Scoped services and fixture finalized; fixture port no longer listening. No manually killed processes.

## Audited runtime results

All 22 labeled rows from the previous runtime driver are present, in the same order. Exact HEAD appears in identity and completion records. Only the five expected click timeout rows fail.

- Missing CSS and supported role locator each time out at 15000ms, retain target identity and server-browser client identity, and now warn that the click may have happened and removed its target or navigated; check the page before retrying, then take a fresh snapshot. Observed 15020ms and 15011ms respectively.
- Hidden/disabled controls still match and preserve their caution; no bad click occurred.
- Working CSS before failure, recovery afterward, fresh snapshot aria-ref, and coordinate click succeed. Final counters: clicks=4, badClicks=0, waitClicks=1, waitWasDisabled=true. Auto-wait succeeds after the fixture enables its control.
- Slow navigation dispatches exactly one GET and persists dispatched=yes. Click times out after 1835ms at a 1500ms timeout, preserves locator.click's original timeout text when the bounded observation cannot finish, then recovers after releasing navigation. This does not claim a deterministic timing regression test.
- Controlled compatibility probes preserve original errors for count rejection, count never settling (251ms), and coordinate failure. Old no-reason summary is unchanged, optional reason round-trips, server-browser reason caps at 500 characters, legacy-host reason stays absent, and each probe request is delivered once.

Diff audit from [f392d5468b](https://github.com/pingdotgg/t3code/commit/f392d5468b) to requested HEAD: three files, eight insertions/five deletions; stronger zero-match caution, ErrorOptions/cause retention, and matching assertions. No additional behavior changes found.

Prior base runtime and before proof (2 failing, 40 passing tests) remain valid historical evidence; not rerun or relabeled as current HEAD. [Prior report](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/b28448685f5ce988/issue-3714-evidence-report.md) retains those artifacts and limitations.

## Scope and FRICTION

Visual matrix EMPTY, 0/0. Server diagnostic change, no rendered UI changes. Snapshot bitmap intentionally omitted; textual snapshot/ref used for interaction only.

Native Electron attachment and MCP HTTP transport remain UNVERIFIED. Broker-visible isError is driver mapping, not an observed MCP HTTP envelope. Mobile-native, relay/tunnel, multi-environment transports and the original old desktop build are unverified. Direct isolated service runtime is the authorized proof path; no collaborative browser/dev server needed.

No execution blockers. Pending navigation exercised bounded original-error fallback. No new lint/typecheck; requested verification was two focused test files. Audit validated exact HEAD, clean checkout, complete runtime rows, counters, expected failures, tests and cleanup. Upload artifacts manually reviewed as synthetic fixture data and scanned for credential patterns; no secrets found. Drivers contain only code and fixed synthetic identifiers/paths.

Verdict: SUFFICIENT for refreshed exact-HEAD server-browser runtime, compatibility and 42-test proof. Does not establish native Electron or MCP HTTP verification.