The configurable bridge subnet (#180) is validated at tier 1 (test_compose.sh asserts a custom network.subnet rebases every IP/CIDR/endpoint in the rendered compose), but no live scenario ever deploys on a moved subnet. A hardcoded 172.28.0.x lurking in an init/entrypoint, or a service that can't reach a peer on the new prefix, would pass tier 1 and only break on a real collided host.
Add: a matrix scenario (e.g. network.subnet=10.84.0.0/24) that brings the stack up on the moved subnet and runs the standard running-state battery. Tor's render-at-start entrypoint and monerod's envsubst'd proxy IP are the highest-value things to exercise live here.
The configurable bridge subnet (#180) is validated at tier 1 (test_compose.sh asserts a custom
network.subnetrebases every IP/CIDR/endpoint in the rendered compose), but no live scenario ever deploys on a moved subnet. A hardcoded 172.28.0.x lurking in an init/entrypoint, or a service that can't reach a peer on the new prefix, would pass tier 1 and only break on a real collided host.Add: a matrix scenario (e.g. network.subnet=10.84.0.0/24) that brings the stack up on the moved subnet and runs the standard running-state battery. Tor's render-at-start entrypoint and monerod's envsubst'd proxy IP are the highest-value things to exercise live here.