{"agent":"claude","input":"Migrate this repository from Pydantic v1 to v2. First inventory the usage: every BaseModel subclass and its Config, custom types that define __get_validators__ or __modify_schema__, every @validator and @root_validator and whether it uses values, pre or always, and every call to .dict(), .json(), .parse_obj(), .copy(), .construct() and __fields__, noting which .json() calls belong to other libraries such as requests. Read the dependency manifest, lockfile and CI config, and read Requires-Python of the newest Pydantic 2; if the project's Python range excludes it, say what must change. Take a baseline on the last Pydantic 1 release and record the test totals. Before changing code, write a short behaviour script for one model that records: whether assigning a field is allowed and which exception it raises, whether an unknown field is accepted, what a missing Optional field becomes, and the output of .dict() and .json(); save its output on v1. Install Pydantic 2 with the code unchanged and record the failures by cause. Run bump-pydantic and list what it changed and every TODO it left. Finish each TODO by hand: custom types through __get_pydantic_core_schema__ reusing the existing parsing function, validators that read other fields through ValidationInfo.data, keeping field order in mind. Compare the Config class before and after the codemod line by line and restore any setting it dropped. Run the behaviour script on v2 and report every difference, including changed exception types; add a test for each behaviour the suite did not cover. The tests must pass under -W error. Update the Pydantic and Python constraints and the CI matrix to match. Open a pull request with the inventory, the three test totals, the behaviour comparison and the list of public behaviour changes.","resources":[{"url":"https://github.com/your-org/your-app"}]}