Testing & Agent Automation Skills

Fan external-reachability work out to parallel subagents over the shared vpn-egress Mullvad browser stack. Use when a batch of targets each need real per-target investigation -- diagnosing why each of N sites fails, auditing many domains and reading each one's config -- or when a list is large enough that wall-clock matters. NOT for simply checking several URLs: check-url.js already takes many URLs in one invocation, and one call beats any fan-out. Covers stack lifecycle ownership, the literal-command dispatch contract, the concurrency ceiling, and merging JSON results.

Stand up the vpn-egress Mullvad tunnel + browser stack from scratch, or repair one that won't start. Use when the stack has never been built on this machine, when gluetun won't come up or restart-loops, when Mullvad credentials need rotating, or when docker exec playwright-vpn fails because the container is missing or broken. NOT for running a check against a URL -- that is vpn-egress-testing, which assumes the stack already works.

General-purpose outside-the-network browser for testing ANY url -- your own, someone else's, one you were asked to check -- from a genuine external vantage point, using the Mullvad-tunneled browser stack in projects/vpn-egress. Use whenever asked to check if a site/URL is reachable, verify a domain is up, or test something 'from outside the network' -- and NEVER trust a direct request from the local shell or WebFetch for this (both give false negatives on this network). Sweeping every domain you own is ONE use case this supports, not the default mode -- see the branch below. For many URLs across parallel subagents, use vpn-egress-orchestrator; for a stack that won't start, vpn-egress-setup.