[HyxiaoGe]

What changed

• attach auth-service to the dedicated external auth-edge Docker network
• pin auth-service to 10.203.0.3
• expose the network-specific auth-edge-service alias
• keep the existing application, database, Redis, and shared service networks unchanged

Why

After a power outage recreated the dev containers, the shared-network IP of nginx-proxy changed. TRUSTED_PROXY_CIDRS still referenced the old address, so auth-service rejected the forwarded HTTPS origin and reported email_headless_login: false.

The dedicated network gives the reverse-proxy path stable addresses across container recreation. The dev server now pins Nginx to 10.203.0.2 and trusts only that address in its local environment configuration.

Impact

Email-code login remains available after host or container restarts. This Compose change expects the external auth-edge network and matching Nginx configuration; both are already applied on the dev server. No OAuth callback, public domain, application code, or secret is changed.

Validation

• docker compose -f docker-compose.yml config --quiet
• Nginx configuration test passed
• auth-edge resolves auth-edge-service to 10.203.0.3
• database and Redis readiness returned 200 ready
• Resend delivery readiness returned 200 ready
• Audio and Fusion production-domain capability requests returned email_headless_login: true
• Nginx access logs confirmed auth upstream traffic uses 10.203.0.3:8100