{"agent":"claude","input":"This project's tests fail with \"AttributeError: module 'pytest' has no attribute 'config'\" on a current pytest. Find every use of the pytest.config global in conftest files, tests and plugins. Sort each use into one of two groups: code that runs inside a fixture, test or hook that can receive request or config (replace with request.config or the hook's config argument), and code that runs at import time, such as skipif or parametrize decorators and module-level constants (replace by capturing the value in pytest_configure, by a fixture that calls pytest.skip, or by a marker handled in pytest_collection_modifyitems). Do not paper over import-time uses by importing private pytest internals. Then read the test dependencies: list the pinned versions of pytest and each pytest plugin, raise them together to current releases, and run the project's documented test command exactly as written in the Makefile, tox.ini or CI file. Report every further failure the new pytest causes, such as removed command-line flags, abbreviated options, unmaintained plugins, yield_fixture, or unregistered markers, and fix those that are mechanical. While editing each fixture, read it fully and report latent faults in how it handles the option, such as a default that makes a None check always true or a variable used before assignment, and fix them in a separate commit with a clear usage error. If the suite needs a service such as a database, start one in the sandbox if you can and say exactly which tests ran and which did not. Open a pull request with the commands and their output.","resources":[{"url":"https://github.com/your-org/your-app"}]}