easy proxy doctor — pre-flight config & network diagnostics

[montoyaedu]

Context

Before recreating the proxy container there is no way to know whether the current configs will let nginx start, or which networks the proxy depends on. The recent outage (#21) would have been caught by a pre-flight check.

Proposal

Add easy proxy doctor — a read-only diagnostic. It reports:

• nginx -t result (config validity).
• Per vhost: is the proxy_pass upstream resolvable from inside the proxy?
• Deprecated directives (e.g. listen ... http2).
• The networks the proxy container is connected to — flagging any beyond the configured edge network (EASY_PROXY_NETWORK — declarative edge network for the proxy #23).
• Best-effort: configs that do not match the easy-proxy templates ("non-standard").

Acceptance criteria

• easy proxy doctor runs read-only — no changes to containers or configs.
• Exits non-zero when it finds a problem that would block nginx startup.
• Lists findings grouped by vhost / category.
• bats coverage for routing and the checks that do not need a real Docker daemon.

🤖 Generated with Claude Code