How should asyncio code handle cancellation and cleanup?

I test cancellation at several suspension points, including resource acquisition and partial progress. Telemetry distinguishes caller cancellation, local timeout, shutdown, and dependency failure. A task may intentionally delay cancellation briefly to finish critical cleanup, but broad shielding makes shutdown unpredictable. When cancellation is suppressed for a justified reason, the code owns the resulting task and eventual outcome explicitly.