[Bug]: Pac模式下访问带cloudflare防护的网站出现无限循环cloudflare人机验证的问题

### 操作系统 / v2rayN / Core 版本

Windows11Pro /v7.24.9 /26.3.27

### 预期情况

正常访问带cloudflare人机验证的网站在点一次后会正常进入网站

### 实际情况

实际在访问的时候（PAC模式+V4全局默认配置）
会出现无限进入cloudflare人机验证的循环，无法正常进入网站，偶尔使用无痕模式可以在点一次验证后进入
内核日志无任何相应

### 复现方法

启动软件，将模式设置为pac+V4全局 （默认设置）
尝试访问网站
无限循环人机验证

### 软件日志

2026-09-13 01:43:43.0143-DEBUG Unhandled interaction exception in AppendQueueMsg at D:\a\v2rayN\v2rayN\v2rayN\ServiceLib\ViewModels\MsgViewModel.cs:77,Failed to find a registration for an Interaction.
2026-09-13 01:43:43.0143-DEBUG at ReactiveUI.Primitives.SubscribeExtensions.Rethrow(Exception exception) in D:\a\Primitives\Primitives\src\ReactiveUI.Primitives.Core\SubscribeExtensions.cs:line 31
at ReactiveUI.Primitives.Signals.AsyncSignal`1.GetResult() in D:\a\Primitives\Primitives\src\ReactiveUI.Primitives.Core\Signals\AsyncSignal.cs:line 248
at ServiceLib.Common.Extension.HandleSafe[TInput,TOutput](Interaction`2 interaction, TInput input, TOutput defaultValue, String memberName, String filePath, Int32 lineNumber) in D:\a\v2rayN\v2rayN\v2rayN\ServiceLib\Common\Extension.cs:line 149
2026-09-13 01:43:43.5468-DEBUG Unhandled interaction exception in AppendQueueMsg at D:\a\v2rayN\v2rayN\v2rayN\ServiceLib\ViewModels\MsgViewModel.cs:77,Failed to find a registration for an Interaction.
2026-09-13 01:43:43.5468-DEBUG at ReactiveUI.Primitives.SubscribeExtensions.Rethrow(Exception exception) in D:\a\Primitives\Primitives\src\ReactiveUI.Primitives.Core\SubscribeExtensions.cs:line 31
at ReactiveUI.Primitives.Signals.AsyncSignal`1.GetResult() in D:\a\Primitives\Primitives\src\ReactiveUI.Primitives.Core\Signals\AsyncSignal.cs:line 248
at ServiceLib.Common.Extension.HandleSafe[TInput,TOutput](Interaction`2 interaction, TInput input, TOutput defaultValue, String memberName, String filePath, Int32 lineNumber) in D:\a\v2rayN\v2rayN\v2rayN\ServiceLib\Common\Extension.cs:line 149
2026-09-13 01:58:49.2614-DEBUG Unhandled interaction exception in AppendQueueMsg at D:\a\v2rayN\v2rayN\v2rayN\ServiceLib\ViewModels\MsgViewModel.cs:77,Failed to find a registration for an Interaction.
2026-09-13 01:58:49.2614-DEBUG at ReactiveUI.Primitives.Signals.AsyncSignal`1.GetResult() in D:\a\Primitives\Primitives\src\ReactiveUI.Primitives.Core\Signals\AsyncSignal.cs:line 248
at ServiceLib.Common.Extension.HandleSafe[TInput,TOutput](Interaction`2 interaction, TInput input, TOutput defaultValue, String memberName, String filePath, Int32 lineNumber)
2026-09-13 01:59:02.2965-DEBUG Unhandled interaction exception in AppendQueueMsg at D:\a\v2rayN\v2rayN\v2rayN\ServiceLib\ViewModels\MsgViewModel.cs:77,Failed to find a registration for an Interaction.
2026-09-13 01:59:02.2965-DEBUG at ReactiveUI.Primitives.Signals.AsyncSignal`1.GetResult() in D:\a\Primitives\Primitives\src\ReactiveUI.Primitives.Core\Signals\AsyncSignal.cs:line 248
at ServiceLib.Common.Extension.HandleSafe[TInput,TOutput](Interaction`2 interaction, TInput input, TOutput defaultValue, String memberName, String filePath, Int32 lineNumber)
2026-09-13 02:06:03.4972-INFO OnClosing -> WindowClosing

### 内核日志

[VMess] v5【hk-sg】新加坡-01-(dns解锁)(azz6***top:18080)
C:\Program Files\v2rayN-Core\guiConfigs\pac.txt
2026/09/13 01:59:42.224241 [Info] infra/conf/serial: Reading config: &{Name:config.json Format:json}
2026/09/13 01:59:42.352499 [Warning] common/errors: The feature VMess (with no Forward Secrecy, etc.) is deprecated, not recommended for using and might be removed. Please migrate to VLESS Encryption as soon as possible.
2026/09/13 01:59:42.460719 [Warning] core: Xray 26.3.27 started
2026/09/13 01:59:43.269321 from tcp:127.0.0.1:8446 accepted tcp:www.google.com:443 [socks -> proxy]
2026/09/13 01:59:43.806568 from 127.0.0.1:6855 accepted //functional.events.data.microsoft.com:443 [socks -> proxy]
2026/09/13 01:59:44 当前延迟: 186 ms，none
2026/09/13 01:59:59.122263 from 127.0.0.1:7355 accepted //nav-edge.smartscreen.microsoft.com:443 [socks -> proxy]
2026/09/13 02:00:04.186469 from 127.0.0.1:11089 accepted //edge.microsoft.com:443 [socks -> proxy]
2026/09/13 02:01:04.269009 from 127.0.0.1:2941 accepted //cn.bing.com:443 [socks -> proxy]
2026/09/13 02:01:04.708416 from 127.0.0.1:10732 accepted //c.bing.com:443 [socks -> proxy]
2026/09/13 02:01:05.152696 from 127.0.0.1:11485 accepted //www.bing.com:443 [socks -> proxy]
2026/09/13 02:01:07.588312 from 127.0.0.1:1822 accepted //edge.microsoft.com:443 [socks -> proxy]
2026/09/13 02:01:07.892531 from 127.0.0.1:13822 accepted //edge.microsoft.com:443 [socks -> proxy]
2026/09/13 02:01:07.893595 from 127.0.0.1:1729 accepted //edge.microsoft.com:443 [socks -> proxy]
2026/09/13 02:01:16.191976 from 127.0.0.1:5352 accepted //th.bing.com:443 [socks -> proxy]
2026/09/13 02:01:16.345791 from 127.0.0.1:2500 accepted //vcf.bing.com:443 [socks -> proxy]
2026/09/13 02:01:16.457364 from 127.0.0.1:3690 accepted //storage.live.com:443 [socks -> proxy]

### 额外信息

实际上我测试后发现，只需要在pac.txt的文件中添加 "cloudflare.com", 就可以正常运行了，规则方面走代理（proxy）

### 我确认已更新至最新版本

- [x] 是

### 我确认已查询历史issues

- [x] 是

### 我确认系统版本是受支持的

- [x] 是

該 issue 是關於 PAC 模式導致無限 Cloudflare CAPTCHA 迴圈的問題。使用者透過將 'cloudflare.com' 新增到 pac.txt 檔案並經由 proxy 路由找到一個 workaround。先從程式碼庫中的 PAC 設定邏輯著手，通常在 pac.txt 解析與規則套用附近。查找網域如何被匹配和路由。透過修改 PAC 規則集測試修正，並驗證 Cloudflare 保護的網站可繞過該循環。

由索引模型根據 Issue 內容生成。