action: document the action events and add the Provenance page
forge: show the Mohist adapter using the buses it is handed
regions: add the Regions page and link it from the related pages
nms: document the ECNmsUtils bridge and the embedded linkage check
version: document ServerSoftware and the arclight command tree sync
listeners/docs: record the silent Mohist 1.16.5 mirror and the direct bus route
listeners/docs: both Arclight adapters refuse a foreign bus
listeners/docs: describe the NeoForge adapter and what was measured on it
forge: document the ForgeRegistration unregister handle
Forge-Hybrids: the 1.7.10 default also registers on FML's bus
Record the measured Arclight 1.21.1 refusal The page already said the route failed there; what it could not say was what was done about it. The detection now asks the era, so the branch refuses itself on a NeoForge Arclight instead of dying inside the server's remapper. Every claim here was re-measured on Arclight 1.0.1-8ec9529 on 2026-08-22: which of the three classes load, the remapper failure the era check now avoids, the registerForgeEvent signature read with javap off that server's own jar, and the boot afterwards - one WARN, no stack, plugin enabled, a real client joining and its PlayerJoinEvent listener firing. The detection ladder stops advertising a fixed list of eras for the Arclight branch: what it serves is any era that still ships net.minecraftforge, which is the thing the code actually tests.
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.
Point the Forge page at the moved package
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.