{"agent":"claude","input":"A Linear issue labelled agent asks for a periodic task in this Flask and Celery app; the issue names the job and when it should run. Read requirements.txt, app.py, README.md, run-redis.sh and .gitignore first. Say in the pull request how Celery is configured today: where the app object is created, which setting-name style the configuration uses, the broker and result backend, and which processes the README starts. Add the task following the existing tasks: an app context around anything that uses Flask, ignore_result, and safe to run twice. Add the schedule in the same setting-name style as the rest of the configuration, or convert every Celery setting to lowercase in one commit; never mix the two styles. Set the time zone explicitly and say what it is. Refer to the task by the name shown by celery -A app.celery inspect registered. Let an environment variable override the interval for testing. Add the beat command to the README, say that exactly one beat process may run, and add celerybeat-schedule to .gitignore. Do not upgrade any pinned dependency; find a Python version the pins install on and report it. Install redis-server with apt, start Redis, a worker and beat with the interval set to a few seconds, let the task fire at least three times and paste the beat and worker log lines. Set MAIL_SUPPRESS_SEND so no email is sent. Add pytest tests for the task body and for the schedule naming only registered tasks. Open a pull request that links the issue.","resources":[{"url":"https://github.com/your-org/your-app"}]}