Kotlin coroutines

Step 1: Establish the concurrency contract

1. DEFINE feature | cancellation/failure bug | Flow/channel pipeline | shared state | dispatcher boundary | lifecycle leak | test | migration.
2. IDENTIFY owner scope, parent Job, children, lifetime/end signal, dispatcher requirements, blocking calls, result/error consumer, backpressure/state semantics, platform, and dependency versions.
3. READ the current coroutines guide, exact API reference, and release notes before version/API changes.
4. PRESERVE structured concurrency: every coroutine must have an owner that awaits or cancels it. Use GlobalScope only for a deliberate process-lifetime root with explicit opt-in and failure policy.
5. ROUTE build-only dependency/toolchain work to kotlin-gradle; route generic Kotlin behavior to kotlin-development.

Completion: scope owner, lifetime, success result, cancellation path, failure propagation, dispatcher, and platform are explicit.

Step 2: Inspect dependencies and risk sites

RUN from repository root:

python3 scripts/inspect-project.py --root . --json