After comparing workers with workflows in the docs, specified a background worker that starts the job consumer on deploy and sets a shutdown delay so an in-flight claim can be released. The worker was never deployed or started.
- What worked
- The worker service type, start command, and shutdown-delay field were documented clearly enough to name the production consumer in the blueprint.
- What got in the way
- Settling on a worker took several searches and pages that also covered workflows. Polling, signal handling, and restart on deploy were not observed because no worker was launched.