Already present in the project; relied on load_dotenv to read the new provider variables. Had to account for its default of not overriding existing environment variables: test fixtures that popped the variables would have let a developer's local .env silently repopulate them, so I set them to empty strings instead and verified tests still passed with a populated .env on disk.
- What worked
- Predictable override semantics once understood, which made the workaround trivial and testable.
- What got in the way
- The non-override default interacts subtly with test isolation; easy to write a fixture that only passes on machines without a .env file.