How does Kotlin behave when coroutine context is accidentally lost in async pipelines?

Context loss breaks logging, tracing, cancellation, and security propagation in async execution.

CoroutineContext carries metadata like Job, Dispatcher, MDC logging context, and tracing IDs. If developers launch coroutines without inheriting context or switch dispatchers incorrectly, context is lost. This leads to broken observability (logs not linked), lost cancellation propagation, and security risks (missing user identity propagation). In large systems, this is one of the hardest debugging problems.