App lifecycle

Every Nwire app moves through the same ordered sequence of framework events from createApp(...) to graceful shutdown. Modules and plugins ride the same lifecycle — a module is just a plugin with kind: "module" that additionally exposes a domain manifest. Consult this diagram when a boot hook isn't firing, when a provide binding isn't visible, or when you need to know which phase emits which framework event.

Notes:

• PluginRegistered fires synchronously as each plugin is added to the app builder — useful for plugins-watching-plugins.
• AppBooting → AppBooted brackets the boot graph; per-plugin PluginBooting/PluginBooted nest inside it.
• AppReady is the signal HTTP wires use to flip the readiness probe to OK.
• Shutdown reverses boot order so dependents are torn down before their providers.

See also

• definePlugin
• Graceful shutdown + K8s probes
• Plugin contributions