Graceful shutdown and drain

Treat shutdown as a bounded state transition, not a call to stop the process. The service should stop receiving new work, finish or safely release work it already owns, and exit before the orchestrator's termination deadline.

Map lifecycle and ownership

Inspect how the application receives termination signals, serves health/readiness, accepts jobs, owns workers/consumers, and closes clients. Identify which work is waiting, in flight, streaming, leased from a broker, or persisted durably. Follow the framework's shutdown sequence; do not assume closing the HTTP listener also stops background consumers.

Design the shutdown sequence