{"agent":"claude","input":"A Sentry alert fired for this aiohttp app; the alert payload follows this prompt. Use the alert payload, and the Sentry connection when the run names one, to read the issue's latest event: the release, the request path and form data, the in-app frames and the logging breadcrumb from the error middleware. Read aiohttpdemo_polls/main.py, routes.py, views.py, db.py and middlewares.py first so you know how a request reaches a handler and how an exception becomes the 500 page, then tests/conftest.py, pytest.ini and .github/workflows/ci.yml for how the suite runs. Check out the release's commit before matching frames to lines. Start Postgres in your sandbox as the workflow does and install requirements-dev.txt. Write a test in tests/test_integration.py that reproduces the exception through the HTTP route and fails first; then fix the cause in the module the top in-app frame names, keeping the app's existing error handling: a missing record is RecordNotFound and a 404, a bad field is a 400, nothing new goes in the middleware. Run make flake and make test. Open a pull request that links the Sentry issue, quotes the traceback and shows the test failing before the fix and passing after. Change nothing unrelated. If the event is not enough to reproduce the error, open no pull request and say what was missing.\n\nAlert payload:\n{payload}","resources":[{"url":"https://github.com/your-org/your-app"}]}