AdminEvents

Every event this package dispatches, declared — the panel's one answer to «what events exist?» (greenhouse decisions/0228). The declarations are not written here: each surface that calls `dispatch()` builds its own from the constants those calls use ({@see AdminShell::events()}), and this class only gathers them, so the list a dispatcher learns at boot is the list the code fires. {@see \Milpa\Admin\AdminPlugin::boot()} hands them to the dispatcher it is given when that dispatcher implements {@see \Milpa\Interfaces\Event\DeclaredEvents}; a dispatcher that does not is told nothing, and dispatching keeps working either way — declaring is a description, never a gate. Booting is not the only way in. This package's manifest names this class under `extra.milpa.events`, the way a capability already names its operation provider, so a host reading `vendor/composer/installed.json` can resolve the list WITHOUT constructing anything — a CLI process that never renders a panel still knows these four names exist (greenhouse decisions/0228, second slice).

public static function declarations(): array

One declaration per event name this package dispatches, in the order a render fires them.