feat: add the module configuration and secrets contract

Modules had no way to be told anything. Announcements — the first real
product Ekklesia will absorb — has zero environment variables and compiles
a LAN IP address into its source, so this is the contract standing between
it and the module system.

- A module declares what it needs in its manifest, using six bounded types
  (string, integer, boolean, enum, url, secret) with no nesting and no
  regular expressions. Static declaration is what lets the platform validate
  configuration *before* deciding whether a module may start: an enabled
  module missing a required value is reported `blocked ·
  configuration_missing · <key>` rather than taking startup down from inside
  its own `start` hook, and Doctor reports the same while still importing no
  module code. That forces `manifestVersion: 5`, a hard cutover.
- Ordinary values persist in one Core table (migration 0005), one row per
  (module_id, key), stored as text until validated against the declaring
  module's current manifest. Nothing is coerced; an invalid stored value
  blocks the module rather than falling back to the default. A key the
  manifest no longer declares is retained and ignored.
- Secrets are never persisted. There is no encryption at rest in this
  repository, so a `secret` key is deployment-supplied and mapped in by the
  host under a name the module never sees. A secret declaration has no
  `default` field, the write API refuses secret material, and the HTTP view
  has no `value` field for one — absent by construction, not filtered.
- Modules receive a frozen `context.config` on the registration, runtime,
  and HTTP handler contexts: the same object identity, per module, beside
  `services` rather than inside it (services is deliberately one shared
  instance). No environment access, no database reference, no way to reach
  another module's values.
- Configuration decides eligibility through ADR 0028's existing resolver:
  three new blocked reasons, each with a distinct operator fix, propagating
  to required dependents through the same mechanism as a disabled module.
- Changes take effect at the next restart; both resources report
  restartRequired. New restricted permission
  `core.modules.configuration.manage`, separate from lifecycle, at the
  sibling prefix `/api/v1/module-configuration`.
- Migration participation stays independent of configuration validity.
  Endpoints and credentials for shared infrastructure stay platform
  concerns; a module declares which bucket it needs, not an S3 endpoint.

See ADR 0029.

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

apps/api/tests/api-http.integration.ts

@@ -196,6 +196,7 @@ async function applyCoreMigrations(url: string): Promise<void> {
       "core:0002_authorization_integrity",
       "core:0003_dashboard_navigation_tables",
       "core:0004_module_lifecycle_state",
+      "core:0005_module_configuration",
     ]);
     expect(aggregate.migrations[0]?.checksum).toBe(
       "f8f2086ef06f7a6943e8ffc4350bb010b37aed04c0a72030d2b153c986b1325f",
@@ -301,7 +302,7 @@ async function createGatedRouteModule(
         compatibility: { moduleSdk: "^0.1.0", platform: "^0.1.0" },
         entrypoints: { server: "./dist/server/index.js" },
         id,
-        manifestVersion: 4,
+        manifestVersion: 5,
         name: `${id} module`,
         permissions: [{ baseline: "public", description: "Gated drain probe.", id: permissionId }],
         version: "0.1.0",
@@ -342,7 +343,7 @@ async function createFixtureModule(
 ): Promise<void> {
   const moduleDirectory = path.join(modulesDirectory, id);
   const manifest = {
-    manifestVersion: 4,
+    manifestVersion: 5,
     id,
     name: `${id} module`,
     version: "0.1.0",
@@ -434,7 +435,7 @@ async function createUiModule(
         compatibility: { moduleSdk: "^0.1.0", platform: "^0.1.0" },
         entrypoints: { server: "./dist/server/index.js", ui: "./dist/ui/index.js" },
         id,
-        manifestVersion: 4,
+        manifestVersion: 5,
         name: `${id} module`,
         version,
       }),
@@ -1102,12 +1103,14 @@ describe.sequential("live API — startup and migration guarantees", () => {
         { environment: "development" },
       );
 
-      // Startup reads the stored module enablement configuration before importing any module
-      // entrypoint (ADR 0028). Against an unmigrated database that read cannot succeed, and the
-      // platform fails closed rather than starting every discovered module: it cannot know what an
-      // administrator decided, and starting a module they disabled is worse than not starting.
-      // The failure is Core's own sanitized store error — no connection string, host, SQL, driver
-      // message, or stack.
+      // Startup reads the stored module enablement configuration and then the stored module
+      // configuration, both before importing any module entrypoint (ADR 0028, ADR 0029). Against an
+      // unmigrated database neither read can succeed, and the platform fails closed rather than
+      // starting every discovered module: it cannot know what an administrator decided, and starting
+      // a module they disabled — or one whose required configuration is absent — is worse than not
+      // starting. The two reads are sequential rather than raced precisely so this error code is
+      // deterministic; the failure is Core's own sanitized store error, with no connection string,
+      // host, SQL, driver message, or stack.
       let captured: unknown;
       try {
         await startApi(config, { rateLimitOverride: { max: 1000, window: 1 } });
@@ -2189,10 +2192,10 @@ describe.sequential("live API — installed module permission end-to-end", () =>
     expect(moduleCheck).toMatchObject({ status: "pass" });
     expect(moduleCheck?.details).toEqual(["calendar 0.1.0"]);
     expect(permissionsCheck).toMatchObject({
-      // Core's own four (`core.authorization.grants.manage`, `core.modules.ui.read`,
-      // `core.dashboard.navigation.manage`, `core.modules.lifecycle.manage`) plus the fixture
-      // module's one.
-      details: ["5 permissions registered"],
+      // Core's own five (`core.authorization.grants.manage`, `core.modules.ui.read`,
+      // `core.dashboard.navigation.manage`, `core.modules.lifecycle.manage`,
+      // `core.modules.configuration.manage`) plus the fixture module's one.
+      details: ["6 permissions registered"],
       status: "pass",
     });
     // Doctor and permission composition read only the manifest — the fixture's register/start