@camstack/system 1.2.316 → 1.2.317

package/dist/kernel/system-settings-policy.d.ts

@@ -0,0 +1,47 @@
+/**
+ * Which `system-settings` keys the STORE may answer, and which the kernel
+ * loads from the door into memory at boot — D675.
+ *
+ * ## The store never outranks env + config.yaml for a bootstrap section
+ *
+ * `system-settings` holds, among other things, `auth.jwtSecret`,
+ * `auth.adminUsername` and `auth.adminPassword` — written there by
+ * `local-auth` (and by older builds) next to `auth.tokenExpiry`. The live
+ * container supplies the same three from env (`CAMSTACK_JWT_SECRET`,
+ * `CAMSTACK_ADMIN_USER`, `CAMSTACK_ADMIN_PASS`). While the store layer was
+ * skipped (every read since D231) env won by accident. Merging the store back
+ * in "highest priority" would let a stale DB copy replace the JWT secret —
+ * invalidating every token — and change the login password.
+ *
+ * So a bootstrap-owned section is answered from env + config.yaml ONLY, and
+ * the store may add exactly the keys in {@link STORE_READABLE_BOOTSTRAP_KEYS}:
+ * today `auth.tokenExpiry`, the one value the operator edits in the UI
+ * (System → Authentication). Widening this list is a security decision, not a
+ * convenience.
+ */
+/** The only keys under a bootstrap-owned section the store may answer. */
+export declare const STORE_READABLE_BOOTSTRAP_KEYS: ReadonlySet<string>;
+/** May the settings store answer `key`, or is it env + config.yaml only? */
+export declare function storeMayAnswer(key: string): boolean;
+/**
+ * Key prefixes loaded from the door into memory ONCE at boot, so the
+ * synchronous readers that need them (the capability registry's preference
+ * readers, `capabilities.getPreference`) answer the persisted value after a
+ * reboot. Capability preferences are the only prefix: every other synchronous
+ * caller of `ConfigManager.get` either reads a bootstrap key or runs before the
+ * door exists.
+ */
+export declare const PRELOADED_SYSTEM_PREFIXES: readonly string[];
+/**
+ * Single keys loaded the same way. `auth.tokenExpiry` is read synchronously on
+ * every mint by the hub's `AuthService` (`AuthManager.signToken`).
+ */
+export declare const PRELOADED_SYSTEM_KEYS: readonly string[];
+/** Is `key` served from the boot-time mirror when the engine is isolated? */
+export declare function isPreloadedSystemKey(key: string): boolean;
+/**
+ * The stored keys of `section` the store may answer (`storeMayAnswer`,
+ * D675): everything for an ordinary section, only the allow-listed keys for a
+ * bootstrap-owned one.
+ */
+export declare function filterStoreSection(section: string, stored: Record<string, unknown>): Record<string, unknown>;

package/dist/{retired-settings-keys-D3rGTGq5.js → retired-settings-keys-DC1uHWPZ.js}

@@ -1,4 +1,4 @@
-const require_dist = require("./dist-RAl10EfG.js");
+const require_dist = require("./dist-a6p0V-IL.js");
 //#region src/builtins/sqlite-storage/retired-settings-keys.ts
 /**
 * Is THIS node the one whose settings store is the cluster's authority?

package/dist/{retired-settings-keys-DqVWSrVw.mjs → retired-settings-keys-DVcKRgzm.mjs}

@@ -1,4 +1,4 @@
-import { Qn as asJsonObject } from "./dist-BPvku43i.mjs";
+import { Qn as asJsonObject } from "./dist-Dori4pf3.mjs";
 //#region src/builtins/sqlite-storage/retired-settings-keys.ts
 /**
 * Is THIS node the one whose settings store is the cluster's authority?

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/system",
-  "version": "1.2.316",
+  "version": "1.2.317",
   "description": "Core addon for CamStack — builtins, pipeline, process management, auth, logging, events",
   "keywords": [
     "camstack",