A per-instance delivery queue still raced across instances. Pi's `/reload` has the old extension instance report `session_shutdown{reason:"reload"}` and, four milliseconds later, a fresh instance report `session_start{reason:"reload"}` for the same session id (measured), so a late shutdown could become the live session's exact `session-end` and complete `agents wait --until exit` while the runtime is alive. Reload-reason lifecycle events are no longer forwarded — the session neither ends nor changes (Oh My Pi has no `/reload`; the text is treated as input) — and the delivery queue now lives on `globalThis`, which every module instance in the process shares (measured), so sub-agent instances and reloads keep one order. The Node harness loads extra instances through a cache-busting import and pins both the reload sequence and cross-instance ordering; both tests fail against the previous relay. Re-verified live: after `/reload`, `agents wait --until exit` times out instead of completing, and the next turn resolves on `hook_pi`. Claude-Session: https://claude.ai/code/session_016P9EWPCSZBP3HoaEqvBdUL