[BUG] claude --chrome-native-host crashes on Windows (Bun internal assertion failure)

## Bug Description

claude --chrome-native-host crashes immediately on startup with a Bun runtime internal assertion failure on Windows.
This prevents the Chrome extension from establishing a connection to Claude Code via Native Messaging, making the
"Claude in Chrome" feature completely non-functional.

## Steps to Reproduce

1. Install Claude Code CLI (v2.1.37) on Windows
2. Install Claude browser extension (v1.0.47) in Chrome
3. Start Claude Code with claude --chrome
4. Run claude.exe --chrome-native-host directly to reproduce the crash

## Error Output

[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-eason

Bun Canary v1.3.9-canary.51 (d5628db2) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2 avx512

panic(main thread): Internal assertion failure
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

https://bun.report/1.3.9/e_2d5628dbEkgggC+s1oU+vvkOu8t/uBysi5uB__qt24tCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKP
g

## Debug Log (from MCP server)

[Claude in Chrome] Attempting to connect to: C:\Users\eason\AppData\Local\Temp\claude-mcp-browser-bridge-eason
[Claude in Chrome] Socket error (code: ENOENT): Error: connect ENOENT
C:\Users\eason\AppData\Local\Temp\claude-mcp-browser-bridge-eason
[Claude in Chrome] No connected sockets in pool
[Claude in Chrome] Server is connected: false

The native host crashes before creating the named pipe, so the MCP server can never connect to the Chrome extension.

## Environment

• Claude Code version: 2.1.37
• OS: Windows 11 (x64)
• Chrome version: 144.0.7559.133
• Chrome extension version: 1.0.47 (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
• Bun: Canary v1.3.9-canary.51
• CPU features: sse42 avx avx2 avx512

## Additional Context

• The MCP server "claude-in-chrome" itself connects successfully to Claude Code (in ~263ms)
• Registry entries for Native Messaging Host are correctly set up
• The Chrome extension shows no errors in Service Worker console
• The issue is specifically the native host process crashing on Windows