onTrigger
Runs whichever of triggerOwner's own events declare a trigger structurally equal to eventTrigger — the whole mechanism behind event chaining. Filtering is a plain equality check (data class equality, no listener registry); when no child matches, this call is a no-op beyond the debug log it always emits first.
Each matching child event is run in turn via EventManager.runEvent, receiving data as its own incomingData — this is how a value produced by one event (a network response, a read result, a transformed payload) flows to whichever child actually consumes it.
Parameters
the outgoing trigger this event is firing right now — matched against triggerOwner's declared children.
value passed downstream as each matching child's incomingData. null when this outcome carries no payload.