Module event 

Typed internal mode-dispatch signals.

MA.1 split the mode-event surface: the four observable lifecycle transitions (MajorEntered / MajorExiting / MinorActivated / MinorDeactivated, design.md §5.10.1) moved to the lattice_protocol::Event enum so hooks and the EF.1 EventFilter apply to them uniformly (mode-architecture.md §7.4). What stays here is the dispatcher’s internal signalling that isn’t part of the public lifecycle catalog:

• ModeActivationFailed — on_activate returned Err; the App-side subscriber rolls back active_modes / mode_guards.
• OptionConflict — two active minors disagree on an option (M.2 emits this; reserved).

Both ride the typed bus (EventBus::publish_typed / subscribe_typed) because they carry richer payloads (a reason string, a conflicting-mode set) and have a single internal consumer rather than open subscription.

Enums

ModeEvent

Internal mode-dispatch signals on the typed event bus (ModeActivationFailed / OptionConflict). The observable lifecycle quartet lives on the [lattice_protocol::Event] enum (MA.1) — see the module docs.