After deploying Omni/Dev/Beryllium.nix for t-615, Caddy still has dynamic routes for /news/* -> localhost:8071 and /files/* -> localhost:8070 (plus redirects). This appears to come from deployer-managed HTTP routes in the manifest, so external traffic for those paths does not traverse Omni.Web on :8079. Need to reconcile manifest/service HTTP routing so all web traffic is truly proxied to Omni.Web.
Root cause was stale NixOS system profile, not deployer-added Caddy routes. push.sh for .nix targets uses existing _/nix symlink; it does not build. After running 'bild Omni/Dev/Beryllium.nix' and redeploying with 'Omni/Ide/push.sh Omni/Dev/Beryllium.nix', Caddy config switched to single upstream only. Verified via Caddy admin API: srv0/routes now has only reverse_proxy localhost:8079.