Tasks are scheduled on the interactive threadpool

julia> ThreadsX.map(_ -> (@info Threads.threadpool()), 1:2);
[ Info: interactive
[ Info: default

julia> foreach(wait, map(_ -> Threads.@spawn(@info Threads.threadpool()), 1:2))
[ Info: default
[ Info: default

julia> versioninfo()
Julia Version 1.12.5
Commit 5fe89b8ddc1 (2026-02-09 16:05 UTC)
Build Info:
  Official https://julialang.org release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 8 × Intel(R) Core(TM) i5-10310U CPU @ 1.70GHz
  WORD_SIZE: 64
  LLVM: libLLVM-18.1.7 (ORCJIT, skylake)
  GC: Built with stock GC
Threads: 8 default, 1 interactive, 8 GC (on 8 virtual cores)
Environment:
  LD_LIBRARY_PATH = /usr/local/lib:
  JULIA_PKG_SERVER = https://eu-central.pkg.julialang.org
  JULIA_EDITOR = code

(jl_jnlyDn) pkg> st
Status `/tmp/jl_jnlyDn/Project.toml`
  [ac1d9e8a] ThreadsX v0.1.12

This may be a Transducers issue, so please move it to that repo if appropriate.

Start by reproducing the Julia 1.12.5 examples using ThreadsX.map and Threads.@spawn, then inspect the ThreadsX and Transducers scheduling entry points. Determine whether the behavior belongs in ThreadsX or Transducers; the issue is complete only when the responsible repository and expected threadpool behavior are established.