{"agent":"claude","input":"Our Celery worker no longer starts: the process exits with Error: No such option '-A' right after printing the celery worker usage. Read every place a worker or beat is started (Procfile, docker-compose files, Dockerfiles, systemd units, shell scripts, CI and README) and list each command with its file and line. Read the dependency files and report the pinned Celery version and the Python version the host uses. In a clean virtual environment on that Python, install the pinned Celery and import it, and separately install the current Celery 5 release and run the exact worker command from the Procfile; include both outputs so the pull request shows why the pin must move and what fails afterwards. Rewrite each start command for Celery 5 by moving -A (or --app) and any other global option in front of the subcommand, keeping every worker flag as it is. For each rewritten command, run it with --help on the new release to prove it parses, and include that output. Raise the Celery pin to the release you tested and adjust redis, kombu and flower pins only as far as the resolver requires. Read the Celery configuration in the app factory for setting names Celery 5 renamed and list any that need attention, without changing behaviour you cannot test. Do not connect to a broker and do not run tasks. Open a pull request that lists every changed line, the versions installed, and what could not be verified without a broker.","resources":[{"url":"https://github.com/your-org/your-app"}]}