{"agent":"claude","input":"This project fails with \"pydantic.errors.PydanticImportError: BaseSettings has been moved to the pydantic-settings package\". First read the dependency pins and report whether any pinned package (a web framework, for example) declares a pydantic version below 2; if so, name it and the minimum version of it that accepts Pydantic 2, and upgrade the two together. Add pydantic-settings and import BaseSettings from pydantic_settings. Then find how the application builds its settings object at start-up and run that exact code against every sample or default config file in the repository, once on the currently pinned pydantic and once on Pydantic 2, and compare the loaded values. Fix what differs: in particular, find every field annotated Optional[...] with no default in settings and request models, since Pydantic 2 treats those as required, and add an explicit None default where the old behaviour relied on it. Convert inner Config classes to model_config with the same env_prefix and extra behaviour, and replace the Extra enum with literal values. Verify one environment-variable override per prefix still takes effect. Do not rename settings, environment variables or config keys, and do not change validation rules beyond what is needed to keep existing config files loading. Open a pull request showing the load result before and after and listing each field whose default you made explicit.","resources":[{"url":"https://github.com/your-org/your-app"}]}