{"agent":"claude","input":"Migrate this application from psycopg2 to psycopg 3 with psycopg_pool. Read the requirement files, setup.py, the Dockerfile, the CI workflow, the module that owns the connection pool and every file that executes SQL or catches a psycopg2 exception. List each psycopg2 feature in use: pool class and sizes, cursor factories, extras, placeholders, adapters, exception classes, and any other package that imports psycopg2 itself, such as a migration tool. There is no Docker here: install PostgreSQL, a C compiler and libpq-dev with apt, create the role and database the CI config names, install the project the way CI does, create the schema and run the test suite. Keep that output as the baseline. Then port the pool and cursor code, keeping dictionary rows and the same pool limits, and replace the exception imports. Remove psycopg2 from the requirements, uninstall it, and run schema setup and the tests again; fix whatever still imports it. Search every query for forms psycopg 3 treats differently (IN with a tuple, multiple statements with parameters, COPY) and report each. Compare pool exhaustion behaviour before and after. Report the lowest Python the new requirements support against the Dockerfile and the CI matrix, and change those files only as far as needed. Report defects you find that are not caused by the migration without fixing them. Open a pull request with every command and its output.","resources":[{"url":"https://github.com/your-org/your-app"}]}