feat: easy proxy recover — break-glass network recovery (#28)

[montoyaedu]

Problem

When the proxy is recreated without joining the backends' Docker networks, nginx can't resolve the upstreams and aborts at startup — every proxied site goes down. Recovery meant a manual docker network connect loop.

Fix

easy proxy recover — a break-glass tool that restores service and explains the misconfiguration.

1. Scans /domains/*/*.conf for backend hostnames — server directives inside upstream {} blocks and proxy_pass targets.
2. docker inspects each → tallies the user-defined networks they share (bridge/host/none excluded — the default bridge has no name-based DNS).
3. The network shared by the most backends is the de-facto edge network (or EASY_PROXY_NETWORK when set); the rest are reported as outliers.
4. Connects the proxy to the backend networks, restarts, and runs the verify.
5. --consolidate instead attaches the backends to the edge network — the clean end state, proxy on one network.

The statistical tally is what makes it smart: it picks the network deterministically and surfaces exactly which backends are misconfigured.

Changes

• commands/proxy.sh — recover subcommand + __easy_command_proxy_recover + help entry.
• test/recover.bats — 5 tests; test_helper.bash — mock_docker_topology (per-container networks from a topology file).
• CLAUDE.md, README.md, CHANGELOG.md updated.

Test plan

TDD — 5 tests written first, watched fail, then made green.

npm run lint   # exits 0
bats test/     # 49/49 (44 + 5 new)

Closes #28

🤖 Generated with Claude Code