feat: add the minimal operational module lifecycle

Ekklesia had no notion of a module being on or off: the accepted module set
was exactly "whatever discovery found on disk", and `ModuleLifecycleStage`
named nine states nothing produced or consumed. This replaces that vocabulary
with two axes that real code produces — persistent, administrator-owned
configuration (`enabled`/`disabled`) and per-boot runtime observation
(`running`/`disabled`/`blocked`) — and wires them through startup.

- One Core table (`ekklesia_core_module_state`, migration 0004) holding only
  `module_id` and `enabled`. A module with no record is enabled by default, so
  deploying a module is still sufficient to run it and discovery never needs an
  initialization write. A record for an undeployed module is retained and
  ignored, so redeploying restores the decision.
- `resolveModuleEligibility` is pure: a disabled module transitively blocks
  every module that *requires* it (module and capability edges alike) with a
  structured reason naming the provider; optional dependencies never block; and
  a missing, incompatible, or cyclic dependency stays discovery's concern.
- `startApi` starts only the eligible set and builds the UI publication
  registry from that same list, so routes, artifacts, browser inventory, and
  Dashboard navigation all follow one authoritative set. A disabled module is
  never imported, so there is no per-request enablement check anywhere.
- Startup stays all-or-nothing, deliberately; there is consequently no `failed`
  runtime state. `pnpm modules:enable`/`modules:disable` is the out-of-band
  recovery path for a module that breaks startup.
- Changes take effect at the next start, and the read model reports
  configuration, runtime, and `restartRequired` separately rather than claiming
  a module stopped when it has not.
- Migration participation and permission composition still span the deployed
  and discovered inventories respectively, unchanged.
- New restricted platform permission `core.modules.lifecycle.manage` gates both
  reading and changing enablement, at a sibling prefix (`/api/v1/module-lifecycle`)
  that cannot collide with the module route namespace.
- `pnpm doctor` gains a `modules.lifecycle` check so "why is this module
  unavailable?" is answerable without reading logs.

See ADR 0028.

Co-Authored-By: Claude Opus 5 <[email protected]>

docs/architecture/decisions/0025-trusted-module-ui-asset-publication.md

@@ -30,6 +30,15 @@ names nine stages, but nothing implements a state machine over them: there is no
 enable/disable, no trust store, and no per-module status record. What exists is one accepted set —
 the modules `discoverModules` validated at startup and `startDiscoveredModuleRuntime` then started.
 
+> **Cross-reference — see [ADR 0028](0028-module-operational-lifecycle.md).**
+> The paragraph above described the platform accurately at the time. There is now a persistent
+> enable/disable state and a resolved eligibility model, and `ModuleLifecycleStage` has been replaced
+> by the two axes ADR 0028 records. "Publishable" consequently derives from the **eligible** module
+> set rather than the discovered one, so a disabled or dependency-blocked module publishes no
+> artifact. Everything else in this ADR — lookup by validated identity, the sibling prefix, exact
+> version matching, the anonymous artifact route, and the caching contract — is unchanged and still
+> accepted. There is still no installer.
+
 ## Decision
 
 ### Publication is derived from validated module identity, never from a request path