There are two bridges and they had been sharing one name across two TLDs. The
centralized one — bridge-ui against the shared MPC-backed bridge-server — was
reachable only at bridge.hanzo.ai and bridge-api.lux.network. The decentralized
one is the lux-bridge daemon: its own binary, its own networks.yaml naming
mchain, talking to MPC in-cluster.
So bridge.lux.cloud now serves the centralized bridge and bridge.lux.network
keeps serving the decentralized one, which it already was. Managed plane on
.cloud, decentralized on .network — the same line kms.lux.cloud draws, and the
reason MPC moved to .cloud in the commit before this one.
The rule shape is copied from the per-brand rules already in bridge-ingress —
/api to bridge-server, everything else to the UI — so lux.cloud behaves exactly
as bridge.zoo.network and bridge.pars.network do, verified path by path rather
than assumed.
Declared here because it was applied by hand: no MPC or bridge ingress in this
namespace carries a CD tracking-id, so every one of them is drift today.
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev
375dbe6840