# Issue 24256 diagnostic observations

Host: fs-22, Linux x86_64, 24 October 2026, about 20:18–20:25 UTC.
Source: clean origin/main 8176b58931, branch fix/issue-24256; no source changes.

1. Installed dependencies with vp install and ran vp run dev in /home/ubuntu/wt/issue-24256, isolated .t3 state. The live-data snapshot seed failed because its migration names differ; dev started with a new database successfully. Used the app's initial project/thread, without running an agent.
2. Paired native collaborative Browser panel with the dev web app, opened its server-drawn browser, navigated to https://dash.cloudflare.com/login. Default profile was new. chrome-headless-shell 154.0.8037.92 reached the login form with verification error and disabled Sign in. No credentials or sign-in attempt. Refresh and clear-cookies retained the form failure; the original checkbox loop did not appear.
3. Stopped the owned dev session. Downloaded https://storage.googleapis.com/chrome-for-testing-public/154.0.8037.92/linux64/chrome-linux64.zip and extracted it outside the repository. ldd reported no missing libraries. Temporarily replaced ONLY the isolated cache executable with a symlink to full Chrome; no launch flags or source changes. Restarted vp run dev.
4. In the same real app opened a fresh Incognito browser and navigated to the same URL. Full Chrome 154.0.8037.92 also showed the verification error and disabled Sign in. /proc executable links confirmed the browser processes were the full Chrome binary. No credentials or sign-in attempt.

The full-Chrome experiment does not isolate Cloudflare's deciding signal and does not establish what would happen in a non-automated Chrome on this VM. It rules out claiming that swapping the same-version binary alone fixes this observed failure. Cloudflare documents automated browsers and Playwright as unsupported for solving production challenges:
https://developers.cloudflare.com/cloudflare-challenges/reference/supported-browsers/

Screenshots: original runtime at 1280x800 outer viewport, full-Chrome experiment at 1280x800; both show the real app and streamed browser. These are diagnostic observations, not a before/after fix claim.