[Bug]: WSL环境下间歇性无法连接浏览器插件

### Description

在 WSL 环境下使用 OpenCLI 时，间歇性出现无法连接到浏览器插件的情况。连接有时正常，有时突然断开或无法建立。
但是在Windows环境下使用是正常的 所以我理解并不是浏览器插件安装有什么问题

### Steps to Reproduce

1. 在 WSL 中启动 opencli
2. 正常使用一段时间
3. 偶尔出现无法连接浏览器插件的错误

### Expected Behavior

OpenCLI 应在 WSL 环境下能稳定连接浏览器插件。

### OpenCLI Version

1.7.20

### Node.js Version

20.x

### Operating System

macOS

### Logs / Screenshots

```shell
opencli doctor
⚠️ Stale daemon detected (v1.7.12 ≠ v1.7.20). Restarting...
⏳ Starting daemon...
opencli v1.7.20 doctor (node v24.15.0)

[OK] Daemon: running on port 19825 (v1.7.20)
[MISSING] Extension: not connected
[FAIL] Connectivity: failed (Browser Bridge extension not connected)

Issues:
• Daemon is running but the Chrome/Chromium extension is not connected.
If the extension is already installed, try: opencli daemon restart
If the extension is not installed:
1. Download from https://github.com/jackwener/opencli/releases
2. Open chrome://extensions/ → Enable Developer Mode
3. Click "Load unpacked" → select the extension folder
• Browser connectivity test failed: Browser Bridge extension not connected

Extension update available: v1.0.5 → v1.0.14
Download: https://github.com/jackwener/opencli/releases
```

Start by reproducing the WSL scenario with `opencli doctor` and inspect the daemon and Browser Bridge extension connectivity reported there. Compare the intermittent failure with the working Windows behavior; done means the extension remains connected and the connectivity check succeeds reliably under WSL.

Written by the indexing model from the issue text.