[BUG] Chrome extension v1.0.40 does not connect to Claude Code CLI --chrome on Windows

Environment

• OS: Windows 10/11
• Claude Code version: 2.1.20
• Chrome extension version: 1.0.40
• Node.js: v24.11.1

Problem

After updating to Chrome extension v1.0.40, claude --chrome always reports "browser extension is not connected" even though:

1. Extension is installed and enabled
2. Native messaging host is correctly configured (registry + manifest)
3. Manual chrome.runtime.connectNative('com.anthropic.claude_code_browser_extension') from extension DevTools succeeds
4. Native host process starts and creates the named pipe

Debugging Done

• Confirmed native messaging works manually from extension console
• Killed all stale native host processes
• Reinstalled Claude Code
• Restarted Chrome multiple times
• Created both com.anthropic.claude_browser_extension and com.anthropic.claude_code_browser_extension registry entries pointing to Claude Code's native host
• Extension feature flags show chrome_ext_bridge_enabled: false

Root Cause Hypothesis

The extension v1.0.40 does not auto-initiate connectNative() when Claude Code CLI runs with --chrome. The CLI waits for a connection that never comes.

Impact

This breaks all browser automation workflows that rely on --chrome to use the real browser profile (avoiding bot detection like DataDome).

Related Issues

#20298, #20546, #20663, #20779, #20789

Expected Behavior

claude --chrome --print "Navigate to google.com" should trigger the extension to connect and perform browser automation.

Actual Behavior

CLI reports extension not connected. Extension never initiates native messaging connection automatically.