Unix socket IPC fails with EPERM in sandboxed environments, blocking all page-level actions

## Problem When running the chrome-cdp skill in a sandboxed environment (common in enterprise deployments, containerized setups, and cloud-hosted AI coding tools like Claude Code on the web), **all page-level commands fail** because the per-tab daemon cannot create its Unix domain socket. The daemon uses Unix sockets at `/tmp/cdp-.sock` for IPC between the CLI and the persistent CDP connection. Sandboxed environments block the `socket()` / `bind()` syscalls for `AF_UNIX` at the kernel level, producing: Error: listen EPERM: operation not permitted /tmp/cdp-XXXXXXXXXX.sock This means none of the following commands work in a sandboxed environment: - `snap` / `shot` / `html` — cannot take page snapshots or screenshots - `eval` — cannot evaluate JavaScript on the page - `nav` / `click` / `type` — cannot navigate or interact with page elements - `net` — cannot capture network requests - `loadall` — cannot inject lazy-loaded content Only `list` partially works (when it falls through to a direct WebSocket connection), but any command that requires a daemon — which is all per-tab commands — fails immediately. ## Impact This effectively makes the skill **unusable in any sandboxed environment**. Since sandboxing is increasingly common in enterprise settings (Docker containers, cloud workspaces, managed developer environments), this is a significant limitation that blocks a large class of users from using the skill at all. ## Root Cause The daemon in `cdp.mjs` calls `s...