feat(161): phase-2 bridge — coolify network at create time; dead postgres removed #5526

161 clean-rebuild groundwork ("let's go big")

1. The 502-on-recreate class dies. When the coolify network exists on the host, auto-update.sh layers an override declaring it on the gluecron service — attachment happens at container create time, not via the post-up reconnect (which left a 502 window and made hand-run compose up a trap; bitten 2026-08-24). Dedicated hosts skip the override via a network-exists gate, so the external-network declaration can never fail them. The reconnect stays as belt-and-braces; the whole bridge is deleted with Phase 2 (Coolify eviction).
2. The dead postgres container finally goes. The unused local postgres service is removed from the standalone compose — it ran for months solely as a thing CLAUDE.md warned everyone not to touch. Deploys now pass --remove-orphans, so the stray container is cleaned up automatically on the first deploy after this lands. The pgdata volume stays untouched as a safety net.
3. Deploy-harness source pin updated for --remove-orphans; the stub's network inspect → exit 1 keeps every existing scenario on the no-coolify path, unchanged.

bash -n clean, typecheck clean. Next in the plan: read-only tenant inventory off 161 → portfolio compose + Caddyfile vhosts + the Phase-2 flip runbook.

🤖 Generated with Claude Code