Environment variable smoke tests should prove the changed behavior

A release-check note about redacted config presence, dependency checks, user-visible behavior, and rollback assumptions.

A process starting successfully is not enough after an environment variable change. The smoke test should prove the new value is read by the path it controls: storage, email, payment sandbox, analytics, or a feature flag. Redact secrets, but verify presence and target.