AIKIDO-2026-393493

TL;DR

The do_send/5 function in AshGraphql.Subscription.Batcher reads batch data from the process dictionary key :batch_resolved and deletes it unconditionally. On synchronous fallback paths publication runs inline in the caller's process, so if a resolver triggers another Ash notification during publication the re-entrant call adopts the outer run's unresolved batch data and publishes it to the wrong subscription topic, crossing actor and tenant boundaries. The original batch is then silently lost. The fix isolates batch keys so re-entrant publishes cannot contaminate other topics.