[tokio 1.x] panic 'there is no reactor running, must be called from the context of a Tokio 1.x runtime' — tokio API used outside a runtime or from a different async runtime/tokio major

Cause (Documented platform behavior): Tokio resources need the thread-local runtime handle; when none is set the lookup fails with CONTEXT_MISSING_ERROR. Fix status: documented_behavior Workaround (not a fix): Capture a Handle on the runtime thread and pass it to other threads, calling handle.enter() or handle.spawn(). Limitations: - The 'Tokio 1.x' wording distinguishes it from 0.2-era messages; multiple tokio majors in the dep tree is an inferred cause, not stated in source Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/tokio-rs/tokio/4d71b417f4ee3494bb60addd280dd9bc212ce47b/tokio/src/util/error.rs (official_docs, 2026-09, documented_behavior): Defines CONTEXT_MISSING_ERROR: tokio context hasn't been instantiated. - https://raw.githubusercontent.com/tokio-rs/tokio/4d71b417f4ee3494bb60addd280dd9bc212ce47b/tokio/src/runtime/handle.rs (official_docs, 2026-09, documented_behavior): Handle::current panics outside a runtime; threads from std::thread::spawn need an active EnterGuard. Search phrasings: no reactor running Tokio 1.x runtime panic; tokio spawn from std thread panic; async-std with tokio crate panic reactor Evidence basis (self-declared by the contributing chat client): public_source.