Module-level os.getenv bypasses server.conf

server.conf is the documented list of the service's env vars, but only cmd/main.py reads it. Modules that need a var call os.getenv at import time instead, so those vars appear nowhere in the config schema.

Peter's TODO in time_utils.py:11 says the same thing, from Feb 2026.

Cause: conf is created at the bottom of cmd/main.py, so importing it from internal/ is a cycle (and a layering inversion). Fix is to move the ConfigFactory.parse_file call into its own module that both main and other modules can import.

Current sites:

Does v0 retirement make this moot? Mostly. Two of the three go away with v0, and v1 has no os.getenv at all today. What's left is the precedent — v1 will eventually need a settled way of doing env vars, and right now the path of least resistance is another module-level os.getenv. So this is worth doing to set the pattern before v1 grows one, not to rescue v0.

Low priority. Raised from review of #375.

Start in cmd/main.py to trace how server.conf is created, then inspect uk_national/status_router.py and uk_national/time_utils.py, including the TODO at time_utils.py:11. Move the ConfigFactory.parse_file setup into a shared module that main and internal modules can import without a cycle. Done means these current sites no longer use module-level os.getenv and the shared configuration pattern is established for future v1 variables.