@capybara-hq/kernel 0.1.0-rc.0 → 0.1.0-rc.10

package/dist/extensions/deployment-config-store.d.ts

@@ -0,0 +1,55 @@
+import type { core } from "zod";
+import { type Keyring } from "../ctx/secrets.js";
+import type { KernelSchemaDb } from "../db/kernel-schema.js";
+import type { JsonSchema } from "./config-json-schema.js";
+type Obj = Record<string, unknown>;
+/**
+ * The stored half of the deployment-level extension config (C10): where PG keeps it, how it is read
+ * back and merged under the startup config. Pure helpers shared by the extension installs (the
+ * desired state the host loads with), the admin service and the CLI.
+ */
+/** 部署级插件配置的密钥存在 `capybara.secrets` 的这个 org_id 下（不是真实组织；namespace `kernel`）。 */
+export declare const DEPLOYMENT_SECRETS_ORG = "_deployment";
+/** 内核自己的 secrets 命名空间（`kernel` 是保留插件名）。 */
+export declare const SECRETS_NAMESPACE = "kernel";
+export declare const secretKey: (plugin: string, path: string) => string;
+/** 一个插件的部署级配置描述：真实模块的 zod schema（有的话）与字段清单。 */
+export interface DeploymentSchemaInfo {
+    version: string;
+    schema?: core.$ZodType | undefined;
+    /**
+     * Without `schema` (no module on this replica): the package's static form schema
+     * (`extension.configSchemas.deployment`), shown but never used to validate.
+     */
+    jsonSchema?: JsonSchema | undefined;
+    fields: {
+        path: string;
+        secret: boolean;
+        hot: boolean;
+    }[];
+}
+/** 由 zod schema 得出字段清单（`configFields`：对象路径上的叶子，secret 向下继承）。 */
+export declare function schemaFields(schema: core.$ZodType | undefined): DeploymentSchemaInfo["fields"];
+export declare const isObj: (v: unknown) => v is Obj;
+/** 按点路径设值，缺失的中间对象自动创建；中间节点不是对象时放弃。 */
+export declare function setDeep(obj: Obj, path: string, value: unknown): void;
+/** 按点路径删除键；删完变空的中间对象一并删掉。 */
+export declare function deleteDeep(obj: Obj, path: string): void;
+/**
+ * 合并一个插件的部署配置（C10 的优先级：环境变量 > 文件 / Nacos > PG > schema 默认值）：以启动配置
+ * （`fileValue`，已含环境变量）为底，逐字段补上 PG 里保存、而启动配置没有覆盖的值。按字段合并：启动配置给了的字段
+ * 整个以它为准（不与 PG 的值深合并）。`fields` 为字段点路径（没有 schema 时用 PG 值的叶子路径）。默认值由校验补上。
+ */
+export declare function mergeDeploymentConfig(stored: Obj, fileValue: unknown, fields?: string[]): unknown;
+/**
+ * PG 里一个插件保存的部署配置（非密钥字段 + 解密的密钥字段，按点路径放回对象）。只并入 `secretPaths`（当前
+ * schema 里是密钥的字段）的密钥：旧版本留下、现在已不是密钥或已删掉的字段不解密、不并入（否则会被当成明文回显
+ * 或保存）。
+ */
+export declare function readStoredDeploymentConfig(db: KernelSchemaDb, keyring: Keyring, plugin: string, opts: {
+    forUpdate?: boolean;
+    secretPaths: readonly string[];
+}): Promise<Obj>;
+/** 字段清单里的密钥字段路径。 */
+export declare const secretPathsOf: (fields: DeploymentSchemaInfo["fields"]) => string[];
+export {};

package/dist/extensions/deployment-config-store.js

@@ -0,0 +1,133 @@
+import { configFields, getPath } from "../config/fields.js";
+import { createSecrets } from "../ctx/secrets.js";
+/**
+ * The stored half of the deployment-level extension config (C10): where PG keeps it, how it is read
+ * back and merged under the startup config. Pure helpers shared by the extension installs (the
+ * desired state the host loads with), the admin service and the CLI.
+ */
+/** 部署级插件配置的密钥存在 `capybara.secrets` 的这个 org_id 下（不是真实组织；namespace `kernel`）。 */
+export const DEPLOYMENT_SECRETS_ORG = "_deployment";
+/** 内核自己的 secrets 命名空间（`kernel` 是保留插件名）。 */
+export const SECRETS_NAMESPACE = "kernel";
+const SECRET_KEY_PREFIX = "plugin-deployment-config:";
+export const secretKey = (plugin, path) => `${SECRET_KEY_PREFIX}${plugin}:${path}`;
+/** 由 zod schema 得出字段清单（`configFields`：对象路径上的叶子，secret 向下继承）。 */
+export function schemaFields(schema) {
+    if (!schema)
+        return [];
+    return configFields(schema).map((f) => ({
+        path: f.path,
+        secret: f.meta?.secret === true,
+        hot: f.meta?.hot === true,
+    }));
+}
+export const isObj = (v) => typeof v === "object" && v !== null && !Array.isArray(v);
+/** 按点路径设值，缺失的中间对象自动创建；中间节点不是对象时放弃。 */
+export function setDeep(obj, path, value) {
+    const segs = path.split(".");
+    let node = obj;
+    for (const seg of segs.slice(0, -1)) {
+        const next = node[seg];
+        if (next === undefined)
+            node[seg] = {};
+        else if (!isObj(next))
+            return;
+        node = node[seg];
+    }
+    node[segs[segs.length - 1]] = value;
+}
+/** 按点路径删除键；删完变空的中间对象一并删掉。 */
+export function deleteDeep(obj, path) {
+    const segs = path.split(".");
+    const chain = [obj];
+    let node = obj;
+    for (const seg of segs.slice(0, -1)) {
+        if (!isObj(node))
+            return;
+        node = node[seg];
+        if (!isObj(node))
+            return;
+        chain.push(node);
+    }
+    delete chain[chain.length - 1][segs[segs.length - 1]];
+    for (let i = chain.length - 1; i > 0; i--) {
+        if (Object.keys(chain[i]).length > 0)
+            break;
+        delete chain[i - 1][segs[i - 1]];
+    }
+}
+/** 叶子点路径（对象递归；其余都是叶子）。 */
+function leafPaths(value, prefix = "", out = []) {
+    if (isObj(value)) {
+        for (const [k, v] of Object.entries(value))
+            leafPaths(v, prefix ? `${prefix}.${k}` : k, out);
+    }
+    else if (prefix !== "")
+        out.push(prefix);
+    return out;
+}
+/** 启动配置（文件 / 环境变量合并后的值）是否覆盖了这个字段：给了它、它下面的值，或在祖先上给了非对象值。 */
+function coveredBy(fileValue, path) {
+    let node = fileValue;
+    for (const seg of path.split(".")) {
+        if (node === undefined)
+            return false;
+        if (!isObj(node))
+            return true;
+        node = node[seg];
+    }
+    return node !== undefined;
+}
+/**
+ * 合并一个插件的部署配置（C10 的优先级：环境变量 > 文件 / Nacos > PG > schema 默认值）：以启动配置
+ * （`fileValue`，已含环境变量）为底，逐字段补上 PG 里保存、而启动配置没有覆盖的值。按字段合并：启动配置给了的字段
+ * 整个以它为准（不与 PG 的值深合并）。`fields` 为字段点路径（没有 schema 时用 PG 值的叶子路径）。默认值由校验补上。
+ */
+export function mergeDeploymentConfig(stored, fileValue, fields = leafPaths(stored)) {
+    if (fileValue !== undefined && !isObj(fileValue))
+        return fileValue;
+    const out = structuredClone(fileValue ?? {});
+    for (const path of fields) {
+        const v = getPath(stored, path);
+        if (v === undefined || coveredBy(fileValue, path))
+            continue;
+        setDeep(out, path, structuredClone(v));
+    }
+    return out;
+}
+/**
+ * PG 里一个插件保存的部署配置（非密钥字段 + 解密的密钥字段，按点路径放回对象）。只并入 `secretPaths`（当前
+ * schema 里是密钥的字段）的密钥：旧版本留下、现在已不是密钥或已删掉的字段不解密、不并入（否则会被当成明文回显
+ * 或保存）。
+ */
+export async function readStoredDeploymentConfig(db, keyring, plugin, opts) {
+    let q = db
+        .selectFrom("extension_deployment_configs")
+        .select("config")
+        .where("plugin", "=", plugin);
+    if (opts.forUpdate)
+        q = q.forUpdate();
+    const row = await q.executeTakeFirst();
+    const out = structuredClone(row?.config ?? {});
+    const prefix = secretKey(plugin, "");
+    const wanted = new Set(opts.secretPaths);
+    if (wanted.size === 0)
+        return out;
+    const keys = await db
+        .selectFrom("secrets")
+        .select("key")
+        .where("namespace", "=", SECRETS_NAMESPACE)
+        .where("org_id", "=", DEPLOYMENT_SECRETS_ORG)
+        .execute();
+    const secrets = createSecrets(db, keyring, SECRETS_NAMESPACE);
+    for (const { key } of keys) {
+        if (!key.startsWith(prefix) || !wanted.has(key.slice(prefix.length)))
+            continue;
+        const v = await secrets.get(DEPLOYMENT_SECRETS_ORG, key);
+        if (v !== null)
+            setDeep(out, key.slice(prefix.length), JSON.parse(v));
+    }
+    return out;
+}
+/** 字段清单里的密钥字段路径。 */
+export const secretPathsOf = (fields) => fields.filter((f) => f.secret).map((f) => f.path);

package/dist/extensions/deployment-config.d.ts

@@ -1,21 +1,28 @@
-import { type Transaction } from "kysely";
+import type { LocalizedName } from "@capybara-hq/plugin-sdk";
 import type { core } from "zod";
+import type { KernelAppOptions } from "../app.js";
 import { type ConfigSourceKind } from "../config/sources.js";
 import { type Keyring } from "../ctx/secrets.js";
-import type { KernelDatabase, KernelDb } from "../db/kernel-schema.js";
+import type { KernelSchemaDb } from "../db/kernel-schema.js";
+import { SuperAdminLock } from "../identity/super-admin.js";
+import { KernelConfigService } from "../infra/config/kernel-config.service.js";
+import { KernelDb } from "../infra/database/kernel-db.js";
+import { TransactionHost } from "../infra/database/transaction-host.js";
+import type { KernelLogger } from "../log.js";
+import type { PublishBus } from "./admin-view.js";
+import { type ConfigIssue } from "./config-issues.js";
 import { type JsonSchema } from "./config-json-schema.js";
-import { type ConfigIssue } from "./org-config.js";
-type Trx = Transaction<KernelDatabase>;
+import { DEPLOYMENT_SECRETS_ORG, type DeploymentSchemaInfo, mergeDeploymentConfig, readStoredDeploymentConfig, schemaFields, secretPathsOf } from "./deployment-config-store.js";
+import { ExtensionDisplayNames } from "./display-name.js";
+import { ExtensionHost } from "./host.js";
+import { ExtensionInstalls } from "./installs.js";
+import { ExtensionLifecycle } from "./lifecycle.js";
+import { PLUGIN_DEPLOYMENT_CONFIG_TOPIC } from "./lifecycle-topics.js";
+import { PluginDeploymentConfigLock } from "./locks.js";
+export { DEPLOYMENT_SECRETS_ORG, type DeploymentSchemaInfo, mergeDeploymentConfig, readStoredDeploymentConfig, schemaFields, secretPathsOf, };
 type Obj = Record<string, unknown>;
-/** 部署级插件配置的密钥存在 `capybara.secrets` 的这个 org_id 下（不是真实组织；namespace `kernel`）。 */
-export declare const DEPLOYMENT_SECRETS_ORG = "_deployment";
-/**
- * 部署配置保存之后（kernel bus 主题，频道 `cap:kernel:plugin-deployment-config`，payload `{ plugin }`）：
- * 各副本重读并校验——只改了 hot 字段就地替换，改了非 hot 字段重新加载实例，不合法保持当前值并告警；
- * 插件此刻待配置时，下一次 reconcile 加载它。
- */
-export declare const PLUGIN_DEPLOYMENT_CONFIG_TOPIC = "plugin-deployment-config";
 export type { ConfigIssue };
+export { PLUGIN_DEPLOYMENT_CONFIG_TOPIC };
 /** 后台一个部署配置字段：来源、是否只读；非密钥字段给出生效值，密钥字段只给 `set`。 */
 export interface DeploymentConfigField {
     path: string;
@@ -30,15 +37,41 @@ export interface DeploymentConfigField {
     value?: unknown;
     /** 密钥字段是否已设置（任何来源）；值永不回显。 */
     set?: boolean;
+    /**
+     * Only on a secret record some `x-ui.secrets[].path` names: the record's keys that are set, sorted
+     * (item names, not secret values; spec §4.3). Other secret fields report only `set`.
+     */
+    keys?: string[];
+    /**
+     * What orgs may do with the field (spec A §5.1, the level of its top-level key): `readonly` (they
+     * see it) or `override` (they may bring their own value); absent = hidden from orgs.
+     */
+    org?: "readonly" | "override";
 }
-/** The response of `GET / PUT /api/v1/admin/extensions/:name/config`. */
+/**
+ * One operation on a secret record drawn per item (spec §4.3), only for a path some
+ * `x-ui.secrets[].path` names: `renameFrom` moves an existing value to `key` (nothing when it has
+ * none, replacing a value already at `key`), then `value` sets it (a string) or removes it (`null`).
+ */
+export interface SecretEntry {
+    path: string;
+    key: string;
+    value?: string | null | undefined;
+    renameFrom?: string | undefined;
+}
+/** The response of `GET / PUT / DELETE /api/v1/admin/extensions/:name/config`. */
 export interface DeploymentConfigView {
     plugin: string;
+    /** The plugin's display name (`ExtensionDisplayNames`); null when it has none. */
+    displayName: LocalizedName | null;
     version: string;
     /** 插件声明了部署级配置。 */
     configurable: boolean;
     fields: DeploymentConfigField[];
-    /** 部署级 schema 的 JSON Schema（密钥字段带 `x-secret`）；本副本拿不到模块（未加载的安装记录）时为 null。 */
+    /**
+     * 部署级 schema 的 JSON Schema（密钥字段带 `x-secret`，提示 `x-ui` / `x-hot`）。本副本拿不到模块（未加载的
+     * 安装记录）时取包内的 `extension.configSchemas.deployment`（`validated` 为 false）；旧包没有它时为 null。
+     */
     schema: JsonSchema | null;
     /** 生效配置按 schema 校验通过（`validated` 为 false 时没有校验，恒为 true，界面不要据此显示「合法」）。 */
     valid: boolean;
@@ -49,57 +82,11 @@ export interface DeploymentConfigView {
     validated: boolean;
     /** 校验失败的原因（只有路径与说明，不含值）。 */
     issues: ConfigIssue[];
-}
-/** 一个插件的部署级配置描述：真实模块的 zod schema（有的话）与字段清单。 */
-export interface DeploymentSchemaInfo {
-    version: string;
-    schema?: core.$ZodType | undefined;
-    fields: {
-        path: string;
-        secret: boolean;
-        hot: boolean;
-    }[];
-}
-/** 由 zod schema 得出字段清单（`configFields`：对象路径上的叶子，secret 向下继承）。 */
-export declare function schemaFields(schema: core.$ZodType | undefined): DeploymentSchemaInfo["fields"];
-/**
- * 合并一个插件的部署配置（C10 的优先级：环境变量 > 文件 / Nacos > PG > schema 默认值）：以启动配置
- * （`fileValue`，已含环境变量）为底，逐字段补上 PG 里保存、而启动配置没有覆盖的值。按字段合并：启动配置给了的字段
- * 整个以它为准（不与 PG 的值深合并）。`fields` 为字段点路径（没有 schema 时用 PG 值的叶子路径）。默认值由校验补上。
- */
-export declare function mergeDeploymentConfig(stored: Obj, fileValue: unknown, fields?: string[]): unknown;
-/**
- * PG 里一个插件保存的部署配置（非密钥字段 + 解密的密钥字段，按点路径放回对象）。只并入 `secretPaths`（当前
- * schema 里是密钥的字段）的密钥：旧版本留下、现在已不是密钥或已删掉的字段不解密、不并入（否则会被当成明文回显
- * 或保存）。
- */
-export declare function readStoredDeploymentConfig(db: KernelDb | Trx, keyring: Keyring, plugin: string, opts: {
-    forUpdate?: boolean;
-    secretPaths: readonly string[];
-}): Promise<Obj>;
-/** 字段清单里的密钥字段路径。 */
-export declare const secretPathsOf: (fields: DeploymentSchemaInfo["fields"]) => string[];
-export interface ExtensionDeploymentConfigDeps {
-    db: KernelDb;
-    keyring: Keyring;
-    /** 启动配置里的 `extensionConfig`（文件 / Nacos 与环境变量合并后）。 */
-    fileConfig: () => Record<string, unknown>;
-    /** 启动配置各字段的来源（见 `extensionConfigSources`）；这些字段只读。 */
-    sources: Record<string, Record<string, ConfigSourceKind>>;
-    /** The extension's deployment config description; undefined when the deployment does not know the extension (`extension.not_found`). */
-    schemaOf: (plugin: string) => Promise<DeploymentSchemaInfo | undefined>;
-    /** 保存提交后发布 {@link PLUGIN_DEPLOYMENT_CONFIG_TOPIC}；失败只告警（各副本的周期 reconcile 会重读生效插件的部署配置兜底）。 */
-    bus?: {
-        publish(topic: string, payload: unknown): Promise<void>;
-    };
-    /** 本副本立即应用（不等 bus 消息回到自己；其他副本经 bus）。失败只记 error。 */
-    applyLocal?: (plugin: string) => Promise<unknown>;
-    /** 经手的密钥值（提交后），内核传 `log.addSecrets`。 */
-    onSecrets?: (values: string[]) => void;
-    log: {
-        warn(msg: string, fields?: Record<string, unknown>): void;
-        error(msg: string, fields?: Record<string, unknown>): void;
-    };
+    /**
+     * The required `override` fields the platform left empty (spec A §5.4a): the extension still
+     * loads, and every org that follows the platform must configure them itself.
+     */
+    orgMustConfigure: string[];
 }
 /**
  * Deployment-level extension config (D8 / C10): non-secret fields are stored in
@@ -110,12 +97,50 @@ export interface ExtensionDeploymentConfigDeps {
  * Secret values are never echoed: responses only say "set", audits only record which paths changed.
  */
 export declare class ExtensionDeploymentConfigService {
-    private readonly d;
-    constructor(d: ExtensionDeploymentConfigDeps);
+    private readonly kdb;
+    readonly txHost: TransactionHost;
+    /** The super admin lock (identity/super-admin.ts): joins the transaction. */
+    private readonly adminLock;
+    private readonly configLock;
+    private readonly keyring;
+    private readonly config;
+    /** This replica's extension schemas (loaded, config-declared or prepared install records). */
+    private readonly host;
+    /** The effective (stored plus startup) deployment config. */
+    private readonly installs;
+    /** Applies a saved config on this replica at once (other replicas through the bus). */
+    private readonly lifecycle;
+    /** Publishes {@link PLUGIN_DEPLOYMENT_CONFIG_TOPIC} after a save (a failure only warns). */
+    private readonly bus;
+    private readonly log;
+    private readonly displayNames;
+    /** Where each startup-config field comes from (see `extensionConfigSources`); those fields are read-only. */
+    private readonly sources;
+    constructor(kdb: KernelDb, txHost: TransactionHost, 
+    /** The super admin lock (identity/super-admin.ts): joins the transaction. */
+    adminLock: SuperAdminLock, configLock: PluginDeploymentConfigLock, keyring: Keyring, config: KernelConfigService, 
+    /** This replica's extension schemas (loaded, config-declared or prepared install records). */
+    host: ExtensionHost, 
+    /** The effective (stored plus startup) deployment config. */
+    installs: ExtensionInstalls, 
+    /** Applies a saved config on this replica at once (other replicas through the bus). */
+    lifecycle: ExtensionLifecycle, 
+    /** Publishes {@link PLUGIN_DEPLOYMENT_CONFIG_TOPIC} after a save (a failure only warns). */
+    bus: PublishBus, log: KernelLogger, options: Pick<KernelAppOptions, "env" | "extensionConfigSources">, displayNames: ExtensionDisplayNames);
+    private get db();
+    /** The startup config's `extensionConfig` (file / Nacos merged with env). */
+    private fileConfig;
+    /**
+     * The extension's deployment config description; undefined when the deployment does not know
+     * the extension (`extension.not_found`). Public for tests only.
+     */
+    schemaOf(plugin: string): Promise<DeploymentSchemaInfo | undefined>;
     /** 插件的生效部署配置（未校验）：启动配置为底，补上 PG 里保存的字段。`schema` 给出时按它的字段合并。 */
     effective(plugin: string, fileValue: unknown, schema?: core.$ZodType): Promise<unknown>;
     /** Admin view; an extension unknown to the deployment -> `extension.not_found`. */
     view(plugin: string): Promise<DeploymentConfigView>;
+    /** `REPEATABLE READ` read-only: every stored field from one snapshot. */
+    private readStored;
     /**
      * Saves some fields: `values` keyed by field dot path, `null` = clear (back to the default),
      * omitted = unchanged.
@@ -123,16 +148,67 @@ export declare class ExtensionDeploymentConfigService {
      *   invalid after merging (except a problem in a read-only startup-config field itself) ->
      *   `extension.config_invalid` (details carry only paths and messages);
      * - a field present in the startup config (file / Nacos / env) -> 409 `extension.config_readonly`.
-     * In a transaction, first `lockEnterpriseAdminsAndAuthorize` (re-checks the enterprise admin under
+     * `secretEntries` change single keys of secret records some `x-ui.secrets[].path` names
+     * ({@link SecretEntry}; spec §4.3): applied under the same locks to the decrypted record, which
+     * is re-encrypted whole, then validated with `values`; the audit lists the record's path, no keys.
+     * A path no hint names -> 400 `validation_failed`; one in the startup config -> 409
+     * `extension.config_readonly`.
+     * In a transaction, first `lockSuperAdminsAndAuthorize` (re-checks the super admin under
      * the lock), then an advisory lock per extension; audit `extension.deployment_config_updated`
      * (detail only `changedPaths`). After the commit publishes {@link PLUGIN_DEPLOYMENT_CONFIG_TOPIC} and
      * applies it on this replica right away.
      */
-    put(plugin: string, values: Record<string, unknown>, actor: string, actorTokenId?: string): Promise<DeploymentConfigView>;
+    put(plugin: string, values: Record<string, unknown>, actor: string, actorTokenId?: string, secretEntries?: readonly SecretEntry[]): Promise<DeploymentConfigView>;
+    /**
+     * Clears the deployment config stored in PG: the `extension_deployment_configs` row and every
+     * secret stored for the extension (any path, also ones an older version declared). Fields from
+     * the startup config (file / Nacos / env) are untouched and stay in effect (they stay
+     * `readonly` in the view; only the startup config changes them). Unknown to the deployment ->
+     * `extension.not_found`.
+     * In a transaction: `lockAndAuthorize` (re-checks the super admin under the lock), the advisory
+     * lock per extension, audit `extension.config_cleared` (detail `clearedPaths`: the stored field
+     * paths, never values; nothing stored -> no audit, no publish). After the commit publishes
+     * {@link PLUGIN_DEPLOYMENT_CONFIG_TOPIC} and applies it on this replica: every replica re-reads,
+     * and the extension loads from what remains, or is unloaded and becomes pending configuration
+     * when that is missing or invalid (`ExtensionHost.applyDeploymentConfig`), without a restart.
+     */
+    clear(plugin: string, actor: string, actorTokenId?: string): Promise<DeploymentConfigView>;
+    private clearStored;
+    /**
+     * Secret entries name a secret record field some hint names (else 400 `validation_failed`, also
+     * for a path given in `values` too, an entry with neither `value` nor `renameFrom`, or a key
+     * `__proto__`). Messages carry paths and keys only, never values.
+     */
+    private checkSecretEntries;
+    private write;
     private info;
     private render;
+    /**
+     * The required `override` fields the platform left empty ({@link DeploymentConfigView}
+     * `orgMustConfigure`); reads nothing when the extension has no `override` field. Unknown to the
+     * deployment -> `extension.not_found`.
+     */
+    orgMustConfigure(plugin: string): Promise<string[]>;
+    /**
+     * The form JSON Schema of the description: the zod schema's, else the package's static one. A
+     * hint conversion that throws (a hand-made package) drops the hints: the plain schema, or none
+     * when even the conversion fails; one warning per schema. Never throws.
+     */
+    private formSchemaOf;
+    private messagesOf;
+    /** The secret record paths some hint of the form schema names. */
+    private hintedPaths;
 }
+/**
+ * Applies secret entries in order to the decrypted config `next` (in place): each record is read
+ * from `next` at its path, renamed, set or removed, and put back; an empty record is removed (the
+ * field falls back to its default).
+ */
+export declare function applySecretEntries(next: Obj, entries: readonly SecretEntry[]): void;
 /**
  * 本副本拿不到模块时（未加载的安装记录）按包内审阅过的静态清单给出字段（没有 zod schema：不校验，加载时再校验）。
+ * The package's `extension.configSchemas.deployment` (written by the packer) is the form schema;
+ * its hints are checked like a loaded schema's (stripped when invalid, silently: a hand-made
+ * package). It is not compared with the module (not part of `manifest_mismatch`, spec §4.5).
  */
-export declare function staticDeploymentSchema(db: KernelDb, plugin: string): Promise<DeploymentSchemaInfo | undefined>;
+export declare function staticDeploymentSchema(db: KernelSchemaDb, plugin: string): Promise<DeploymentSchemaInfo | undefined>;