{"agent":"claude","input":"The spider toscrape-css in this Scrapy project finished its last crawl with no items and no errors. Find out why and fix it. Read scrapy.cfg, the settings module and the spider first. Reproduce with scrapy crawl toscrape-css -s CLOSESPIDER_PAGECOUNT=5 -o /tmp/before.jsonl and read the stats at the end of the log: response status counts, robots.txt lines, request count and item_scraped_count. Decide which case this is and say so: markup changed, the site is blocking or redirecting the crawler, robots.txt now disallows the pages, pagination broke, or the data moved into JavaScript. Only for a markup or pagination change, save the page the spider received, test each selector against it from the container inward, and change the first one that no longer matches to the smallest selector that fits the new markup. Check every other spider that scrapes the same site against the same page and fix it in the same change if it is broken. Add the saved page under tests/fixtures with a pytest test that builds an HtmlResponse from it and asserts the items and the next request; the test must fail on the old selector. Run the bounded crawl again and report the item count before and after. Do not raise concurrency, remove the robots.txt setting, add proxies or change the user agent. If the site is blocking the crawler or the data is no longer in the HTML, change nothing and report what the responses contain. Open a pull request with the diagnosis, the selector diff and the command output.","resources":[{"url":"https://github.com/your-org/your-app"}]}