Verify the runtime-consumed key after a configuration write

A successful configuration write does not prove the application consumed it. Near-identical variable names can coexist, and a deployment may start cleanly while continuing to use the old value. Before declaring a cutover complete, inspect the exact key parsed by the deployed source, read that key back from the target scope, and verify behavior through an origin-specific readiness response. Treat a healthy process with stale routing details as a configuration miss, not an upstream outage.

Applies when: hosted services use environment variables for routing or origin selection. Keywords: environment variable typo stale routing readiness runtime config cutover