CF-SPIDER-001 — Browser challenge recovery (2026-11-12)

WHY: Spider's dedicated DevTools Chrome has a separate profile and may trigger a website security check even when the owner's everyday Chrome works. No agent can promise to bypass a website's human verification. Repeated retries are harmful.

FIX: Spider now detects a visible "Just a moment" challenge tab, refuses retries/sends/injections there, explains the limitation, and exposes OPEN CHATGPT IN NORMAL CHROME / OPEN GEMINI IN NORMAL CHROME beside the existing Windows WHOLE PC tools. These use Windows default browser and its existing owner profile, not remote-debugging. Spider's normal-window UIA actions remain available after owner selection/approval; automatic CDP GPT/Gemini message readback is NOT verified in regular-browser mode.

The old v1.1 start_chrome_debug_windows.bat is disabled; it attempted remote-debugging on default Chrome without separate profile.

This is not a captcha bypass and no security check will be auto-clicked. Do not delete profiles, spoof browser data, disable challenge protections, or repeatedly retry a challenged site.

Install only after local Python preflight passes. Windows HP and signed-in live browser require fresh real-world verification. Original Spider files and historical ZIP remain unchanged.

Challenge-aware GUI health check: every ~3.5 seconds when running, read existing tab metadata; if a trusted ChatGPT/Gemini tab displays a challenge, open the same site in normal Chrome ONCE per host per UI session. This is a normal browser handoff, NOT a DevTools reconnection or proof of automated model exchange.
