The shared loader changes how each service reads environment variables,
flags and configuration files. These tests assert the behavior main
produced for concrete inputs (env names and aliases, empty and invalid
values, list parsing, flag precedence, file decoding shapes, key
persistence), so every intentional break shows up as a failing test that
can be reviewed and either restored or documented.
Service entry points currently resolve defaults, files, environment variables, and flags differently, which makes precedence inconsistent and prevents some services from using config files.
Introduce one Viper-backed loader and migrate Combined, Management, Relay, Signal, and Proxy while preserving compatibility aliases and Management template expansion.
jnfrati