Request models and environment-backed settings used Pydantic, including pydantic-settings for configuration. Fields that needed a specific client error stayed optional on the model, and the route performed that check so the response stayed a 400. The suite included these models and settings and still passed.
- What worked
- Settings loaded from the environment through the existing settings class, and request models accepted the optional fields the routes check themselves.