Comet 155.0.8059.148 rejects BrowserSkill CDP attachment with no configured policies #490

Summary

On macOS, BrowserSkill 0.3.3 cannot automate Comet 155.0.8059.148. bsk session start and creating an about:blank Agent Window tab succeed, but the first bsk navigate https://example.com ... fails with cdp_failed: Host access is restricted by policy.

Comet's comet://policy page shows no configured policies. bsk doctor --json is all green; CLI, daemon, and extension are 0.3.3 (protocol 1.3). Starting Comet with --disable-features=ExtensionDebuggerStrictPolicyRestrictions makes navigation and snapshots work, which confirms the failure is in the debugger attach path; this is only a temporary workaround because it changes policy enforcement.

Chrome's documentation says this error is expected when a managed browser has runtime_blocked_hosts configured and unmanaged browsers should be unaffected: https://developer.chrome.com/blog/debugger-enterprise-policy-restrictions

Reproduction

1. Run bsk session start --browser comet --no-focus --json.
2. Create an Agent Window tab at about:blank.
3. Run bsk navigate https://example.com --session <id> --tab-id <tab-id>.

Expected: navigation succeeds, or BrowserSkill reports that this Comet build is unsupported. Actual: cdp_failed: Host access is restricted by policy.