events, scheduler: document ItemContext.getItem and repeatAsync
dialogue: add the Dialogues page and link it from the related pages
groups: add the Groups page and the five group flags
action: document the action events and add the Provenance page
logic: add the Logic page and rewrite Cooldowns on RepeatPolicy
wiki: document the split packages and ECScheduler's main-thread hop
regions: add the Regions page and link it from the related pages
Add Account events (bus-only)
Document the subscription model: options, the view, the failure handler Subscribing has three forms and one value object, a subscription is a listable view, a failing subscriber goes to the bus's exception handler, and /ecore events answers who is listening. The toolkit page picks up the failing and recording handlers and the strict global bus under @ECoreTest.
Document the per-class listener gate, the watch and the Bukkit lists hasListeners, postIfListened, watchListeners and ECListener.registerWhileListened replace the "one HandlerList for every EC event" section; an event may now declare getHandlerList and gets a list of its own, with the family rule spelled out. The Hytale paragraph stops claiming the gate creates a registry, the forge audience reports no listeners while nothing crosses, and the six Bukkit-only events are listed as bus events produced only while somebody listens.
Document the Forge hybrid route and the forge audience The inbound registerListener API had no documentation anywhere, and the event page described the Forge audience as a possibility - which teaches that it does not exist. Server brands in the measured table are what each server reported about itself, never its distribution name: the 1.7.10 hybrid tested reports Cauldron. Routes with no measurement behind them - Arclight on NeoForge, modern Mohist, CatServer - are documented as unproven rather than left out, because nothing on this route is compile-checked.
Document the event bus and the platform audiences Stale neighbours in the touched tables and lists were corrected against the sources at the same time: the argumento stub, the provider lists on both loaders, and the Bukkit enable/shutdown steps.