A FynApp shut down or failed bootstrap. Drop what is held for it.
A FynApp's config, setup and main are loaded; it is not yet in the registry.
Bootstrap holds the lock and is about to run the main FynUnit.
An expose module was loaded and recorded on the FynApp.
initRunTime was called with new runtime data.
A FynUnit runtime was created. Add fields to it.
Run the main FynUnit. Return true when the handler ran it. The kernel runs the unit itself (initialize, then execute) when no handler does.
Root kernel telemetry. Scope it per add-on.
Look up a loaded FynApp by "name" or "name@version".
Record that a FynApp provides or consumes something, for bootstrap ordering.
The kernel's runtime data.
A FynUnit runtime for a FynApp, with the runtime hooks applied.
Swap where telemetry goes. Scopes taken earlier follow the swap.
What the kernel hands an add-on at install time. Add-ons reach the kernel only through this and the public kernel API, never through its internals: each bundle mangles property names on its own, so a name only survives the trip between bundles when it is declared here.
The array members are hook lists. Add-ons push handlers; the kernel calls them in install order.