@sema-agent/server 7.52.1 → 7.54.0

package/dist/config-center/mcp-revocation.js

@@ -1,3 +1,4 @@
+import { stableStringify } from "./restart-signal.js";
 export function createMcpRevocationLedger(onChange) {
     let baseline;
     let seen;
@@ -40,19 +41,8 @@ export function enabledMcpEntries(mcp) {
     const out = new Map();
     for (const s of mcp.servers) {
         if (s.enabled !== false)
-            out.set(s.name, fingerprintOf(s));
+            out.set(s.name, stableStringify(s));
     }
     return out;
 }
-function fingerprintOf(v) {
-    if (v === null || typeof v !== "object")
-        return JSON.stringify(v) ?? "null";
-    if (Array.isArray(v))
-        return `[${v.map(fingerprintOf).join(",")}]`;
-    const obj = v;
-    return `{${Object.keys(obj)
-        .sort()
-        .map((k) => `${JSON.stringify(k)}:${fingerprintOf(obj[k])}`)
-        .join(",")}}`;
-}
 //# sourceMappingURL=mcp-revocation.js.map

package/dist/config-center/restart-signal.d.ts

@@ -12,7 +12,7 @@ export interface RestartSliceCtx {
      *  所以它们的变化不该产生 restart 理由 —— 否则 center 改一个本机用不上的键,整片 fleet 会为一次
      *  对自己毫无影响的发布滚动重启一遍。缺席 = 没有 env 覆盖 ⇒ 整域都算数(与旧行为一致)。 */
     readFaceEnvHeld?: readonly ("face" | "denyPatterns" | "denyBuiltinTiers" | "denyBuiltinExclude")[];
-    /** #324(core 5.50 design/338):撤销台账腿已接线(`RunnerDeps.mcpRevocations` 席在场且 refresh 拍在喂)。
+    /** [ref](core 5.50 [ref]):撤销台账腿已接线(`RunnerDeps.mcpRevocations` 席在场且 refresh 拍在喂)。
      *  true ⇒ mcp 片的**纯删除向**(current 的 enabled 集是 boot 集的逐字子集)不再签 restart —— 删除已被
      *  台账即时承接(core 每次 dispatch 前探 isRevoked),再签就是为一个已生效的变更滚动重启 fleet。
      *  新增/改址/域整体出现或消失仍签(新 mount / 改址只能 restart 才生效)。缺席/false = 旧语义照签
@@ -31,6 +31,16 @@ export interface RestartSignal {
     /** Epoch ms when this restart first became required (stable across refreshes while `reasons` is unchanged). */
     since: number;
 }
+/** Canonical, key-sorted JSON (array order preserved) so two semantically-equal effective slices fingerprint
+ *  identically regardless of object key order from the center serializer.
+ *
+ *  ⚠️ [ref](2026-08-31)如实登记:这**不是** `src/canonical-json.ts#canonicalJson`(core 逐字港,全仓单源)——
+ *  两者在 JSON 形输入上逐字节相同(golden 交叉读数已证),但本函数把 `undefined` 值键**保留为 `"k":null`**,
+ *  共享件按 `JSON.stringify` 语义**省略**。restart 指纹的输入是进程内构造的切片对象(zod 解析产物 + rest 展开/
+ *  挑字段),`{k: undefined}` 形原则上可达,而它与 `{}` 是否同指纹 = 本轴上的**行为**(多签/少签一次 fleet 滚动
+ *  重启),不是序列化器的私事 ⇒ 语义不恒等不合并;字节钉 test/canonical-json-golden.test.ts,K→O 统一另立件
+ *  走三问。导出只为 mcp-revocation 同源改调(两处此前各持一份逐字相同的复刻)与 golden 直钉,不是公共 API。 */
+export declare function stableStringify(v: unknown): string;
 /** Restart-to-apply slices that DIFFER between this process's BOOT config and a freshly-pulled one. Empty =
  *  nothing baked-at-boot changed (only hot-apply slices moved, or nothing) → no restart needed. An orchestrator
  *  can auto rolling-restart on a non-empty result WITHOUT a restart loop, because the comparison is always

package/dist/config-center/restart-signal.js

@@ -1,7 +1,7 @@
 import { resolveActiveTiers } from "@sema-agent/settings-schema";
-import { RUNTIME_GATE_KEYS, HOT_RUNTIME_GATE_KEYS, runtimeGatePresent, resolveDefaultModelName } from "./apply-effective.js";
+import { resolveDefaultModelName } from "./apply-effective.js";
 const RESTART_SLICES = ["skills", "mcp", "a2a", "scenarios", "runtime-gates", "models-tiers", "degrade-route", "read-face"];
-function stableStringify(v) {
+export function stableStringify(v) {
     if (v === null || typeof v !== "object")
         return JSON.stringify(v) ?? "null";
     if (Array.isArray(v))
@@ -38,14 +38,8 @@ function restartSliceValue(eff, slice, ctx) {
         case "scenarios":
             return enabledOnly(eff.scenarios?.scenarios);
         case "runtime-gates": {
-            const rt = eff.runtime;
-            if (!rt)
-                return null;
-            const present = {};
-            for (const k of RUNTIME_GATE_KEYS)
-                if (!HOT_RUNTIME_GATE_KEYS.has(k) && runtimeGatePresent(rt, k))
-                    present[k] = rt[k];
-            return Object.keys(present).length ? present : null;
+            const ar = eff.governance?.approvalRequire;
+            return Array.isArray(ar) ? { approvalRequire: ar } : null;
         }
         case "models-tiers": {
             const active = eff.models ? resolveActiveTiers(eff.models) : undefined;

package/dist/config-center/skills-mcp.d.ts

@@ -4,7 +4,7 @@ import type { Logger } from "../observability/logger.js";
 import type { LoadedSkill } from "../capabilities/skills.js";
 import type { CenterA2aPeer, CenterMcpServer, CenterSkillManifest } from "./types.js";
 /**
- * Merge center skills OVER the image baseline (design/41-sibling B1; `sema-registry docs/MCP-SKILLS.md`). Load order =
+ * Merge center skills OVER the image baseline ([ref]-sibling B1; `sema-registry docs/MCP-SKILLS.md`). Load order =
  * `loadSkills(SKILLS_DIR)` baseline → center skills lazily fetched by hash and overlaid BY NAME (center
  * wins on a clash → can override a built-in; guarded center-side by publisher RBAC + the publish gate).
  * `enabled:false` is skipped. Content is verified + cached by hash (same hash fetched once). A skill whose
@@ -28,7 +28,7 @@ export declare function resolveMcpServers(mcp: {
     servers: CenterMcpServer[];
 }, logger?: Logger): ScopedMcpServer[];
 /** The MCP servers applicable to a scenario: tagged with it, or untagged (global). undefined when none.
- *  #342:alias 窗撤销,单键命中(同 `skillsForScenario`)。 */
+ *  [ref]:alias 窗撤销,单键命中(同 `skillsForScenario`)。 */
 export declare function mcpForScenario(servers: ScopedMcpServer[] | undefined, scenario: string): McpServerSpec[] | undefined;
 /**
  * DESIGN-269 §2.1 —— resolve center A2A peers (`/effective.a2a`) into core `A2aServerSpec`s + the scenarios

package/dist/config-center/stage-limits.d.ts

@@ -1,12 +1,12 @@
 /**
- * #322 批1 —— limitsHttp 组的 **stage 半场**(design/322 手法 A′ + B 簇1)。
+ * [ref] 批1 —— limitsHttp 组的 **stage 半场**([ref] 手法 A′ + B 簇1)。
  *
  * 形与 `stageApprovalRequire` 同族:一切可抛/可判的事在 stage 做,commit 段只剩纯赋值。三条本域纪律:
  *
  *  1. **非粘**(applyRuntimeHot 的 NON-STICKY 同源):每次 apply 都从 **env 基线**重算 `present ? center : baseline`
  *     ——center 撤键 ⇒ 回 env 底。「缺席=保上一个 center 值」会把一次已经撤回的限额永久冻在进程里。
- *  2. **整批原子**(design/322 §0③ + §4 混批零变异):本域任一键坏值/任一跨键不变量不过 ⇒ **整批拒**,
- *     合法键也不落地,旧值继续服务,拒因响亮点名键(#123 法)。半应用一个限额面 = 运营看到的数字与真门
+ *  2. **整批原子**([ref] §0③ + §4 混批零变异):本域任一键坏值/任一跨键不变量不过 ⇒ **整批拒**,
+ *     合法键也不落地,旧值继续服务,拒因响亮点名键([ref] 法)。半应用一个限额面 = 运营看到的数字与真门
  *     不是同一代,比整批拒糟得多。
  *  3. **判据单源**:跨键不变量走 `config-invariants.ts` 的同一张表(boot 与 stage 同表);数值下限走
  *     config.ts 导出的同一组 floor 常量(env 腿夹取、center 腿拒——**判据阈值同源,处置刻意不同**:

package/dist/config-center/types.d.ts

@@ -1,8 +1,8 @@
 /**
  * config-center wire types — the config-center `/api/config/effective` payload shapes (`CenterModel`,
- * `CenterTeam`, `CenterSkillManifest`, `CenterMcpServer`, `EffectiveConfig`) plus the per-principal
+ * `CenterSkillManifest`, `CenterMcpServer`, `CenterA2aPeer`, `EffectiveConfig`) plus the per-principal
  * execution/session-mirror ruling shapes riding the caps view (`ExecutionRuling`/`SessionMirrorRuling`).
- * Pure type/interface declarations — no runtime logic. Split out of `facade.ts` (design/158 A13,
+ * Pure type/interface declarations — no runtime logic. Split out of `facade.ts` ([ref] A13,
  * internal-lossless: the facade re-exports every symbol below unchanged).
  */
 import type { ToolContentOrigin } from "@sema-agent/core";
@@ -30,11 +30,11 @@ export interface CenterModel {
     vision?: boolean;
     contextWindow?: number;
     maxTokens?: number;
-    /** [818]① 1M dual-window (core 1.289 `Model.autoCompactTokens`): an EXPLICIT roster value wins the
+    /** [ref]① 1M dual-window (core 1.289 `Model.autoCompactTokens`): an EXPLICIT roster value wins the
      *  contextWindow derivation in toModel (applyAutoCompactWindow). Declared on the type face (codex F5) so the
      *  config-provider local-lane projection carries it — toModel keeps its structural read for older shapes. */
     autoCompactTokens?: number;
-    /** design/123 D2 (core 1.226): chars ≈ 1 token for this model's tokenizer, feeding every structural
+    /** [ref] D2 (core 1.226): chars ≈ 1 token for this model's tokenizer, feeding every structural
      *  (non-usage-anchored) token estimate. CJK-heavy models should declare 2–3; absent → env default → core 4. */
     charsPerToken?: number;
     cost?: {
@@ -47,7 +47,7 @@ export interface CenterModel {
      *  记账时固化进 UsageEntry.{weightedTokens,quotaWeightAtUse} 与 lease weightedTokens 轴;改倍率只影响
      *  此后记账,不回算窗口内历史(registry types.d.ts 同句契约)。 */
     quotaWeight?: number;
-    /** design/111 L2②: per-model declarative thinking config (center roster). defaultThinking = this model's DEFAULT
+    /** [ref] L2②: per-model declarative thinking config (center roster). defaultThinking = this model's DEFAULT
      *  tier (resolution chain spec.thinking ?? role.thinking ?? model.defaultThinking); reasoningEffortLevels (openai
      *  endpoints) = tiers the endpoint accepts. Validated against core's ThinkingLevel in toModel; "off" is dropped. */
     defaultThinking?: string;
@@ -58,10 +58,10 @@ export interface CenterModel {
      *  the ONLY way to keep per-model tuning that lived in env (`MODEL_FREQUENCY_PENALTY` etc.) — see the
      *  review-gw heterogeneous-roster migration. MUST be static per published version (prompt-cache prefix). */
     extraBody?: Record<string, unknown>;
-    /** registry-core 0.10.13 ([1002]/[998]⑤c): per-model behavior-slot mitigation sentences, mirrors core
+    /** registry-core 0.10.13 ([ref]/[ref]⑤c): per-model behavior-slot mitigation sentences, mirrors core
      *  `Model.promptGuidance` (core 1.303+ assembles them into the volatile tail's per-model position).
      *  Same category as `extraBody`: logical model metadata, carried verbatim — without this projection the
-     *  configured sentences parse fine in registry-core but never reach the assembly face ([1028]① 排雷:
+     *  configured sentences parse fine in registry-core but never reach the assembly face ([ref]① 排雷:
      *  the missing leg made every promptGuidance pilot a false control). */
     promptGuidance?: string[];
     enabled?: boolean;
@@ -71,24 +71,6 @@ export type CenterRoleTarget = {
 } | {
     select: unknown;
 };
-export interface CenterTeam {
-    name: string;
-    members: {
-        role: string;
-        modelRole?: string;
-        model?: string;
-        systemPrompt?: string;
-    }[];
-    rounds: number;
-    synthesizer?: {
-        role: string;
-        modelRole?: string;
-        systemPrompt?: string;
-    };
-    scenario?: string;
-    maxTranscriptTokens?: number;
-    enabled?: boolean;
-}
 /** Skill MANIFEST entry (content is NOT inline — fetched by hash; see `fetchSkillContent`). */
 export interface CenterSkillManifest {
     name: string;
@@ -109,7 +91,7 @@ export interface CenterMcpServer {
      *  loop unless an operator explicitly opts it in. */
     elicitation?: boolean;
     /**
-     * design/378(core 5.60.0)—— 声明**这台 server 的整套工具**带回来的内容属于哪一类,映射到
+     * [ref](core 5.60.0)—— 声明**这台 server 的整套工具**带回来的内容属于哪一类,映射到
      * `McpServerSpec.contentOrigin`。`"local"` / `"execution"` ⇒ 这台 server 的调用不再给本会话记忆打
      * 「已接触外来内容」标(`execution` 仍留在 `execIsExternalContent` 那只旋钮的射程内);`"external"` 是
      * 显式 PIN,而**PIN 不是空操作** —— 它会取消 `trustedTools` 对这台 server 的按名豁免。
@@ -121,9 +103,13 @@ export interface CenterMcpServer {
      * 所以它的家在 center 下发这条腿;请求腿那半场的门与结构性兑现见 `task-mcp.ts`
      * 的 `assertRequestMcpContentOrigin` 顶注。
      *
-     * ⚠️ **本地 `config.d` 腿今天到不了这里**(如实登记,别读成「两条腿都通」):那条腿的原料形是
-     * registry-core 的 zod schema,未知键被 strip;等 registry-core 补上同名可选键,
-     * `config-provider.ts` 的映射再加一行即可(远端 `/effective.mcp` 腿是直读 JSON,今天就通)。
+     * ⚠️ **两条腿今天都到不了这里**([ref]③ / [ref]③ / [ref],2026-08-31 双绊线实测更正 —— 本注旧版那句
+     * 「远端 /effective.mcp 腿是直读 JSON,今天就通」**不成立**,doc-rot):settings-schema(原 registry-core)
+     * 的 `McpServerSpec` 是默认 strip 的 zod object 且没有 `contentOrigin` 可选键,本地腿在 FileConfigStore 的
+     * `parseDomainLoud(DOMAIN_SCHEMAS.mcp)`、远端腿在消费端边界 `readEffectiveWire`([ref] 裁B)**各被剥一次**。
+     * 修在 sema-settings-schema(补同名可选枚举键 + 发包),本仓提货后 `config-provider.ts` 的映射加一行即通;
+     * 两条 `it.fails` 绊线(test/config-center-wire-read.test.ts + test/config-provider.test.ts)在上游到货时
+     * 自动翻红逼销账。
      */
     contentOrigin?: ToolContentOrigin;
     transport: {
@@ -132,7 +118,7 @@ export interface CenterMcpServer {
         args?: string[];
         envRefs?: Record<string, string>;
     }
-    /** `principalHeader` (design/62): the header name into which the runner injects the task's authenticated
+    /** `principalHeader` ([ref]): the header name into which the runner injects the task's authenticated
      *  end-user principal per-task, so a consumer MCP (e.g. oa-mcp) can enforce per-user RBAC. Not a ref — a
      *  literal header name. The runner fills the value (never the model). */
      | {
@@ -159,14 +145,14 @@ export interface CenterA2aPeer {
     /** env-NAME refs (header-name → ENV_NAME) resolved from THIS service's env at boot. A peer with ANY
      *  unset ref is SKIPPED wholesale (fail-safe — never dial a peer half-credentialed). */
     headerRefs?: Record<string, string>;
-    /** design/62, same contract as the MCP side: the header name the runner injects the task's authenticated
+    /** [ref], same contract as the MCP side: the header name the runner injects the task's authenticated
      *  end-user principal into. Not a ref — a literal header NAME (the runner fills the value, never the model). */
     principalHeader?: string;
     /** Optional allowlist of the peer's skill ids to mount (others are not mounted). */
     allowSkills?: string[];
 }
 /**
- * #A4([4147] 窗三件批 件1;[4073]/[4083] 承诺件)—— READ 容纳面的 center 下发形(`CenterA2aPeer` 的
+ * #A4([ref] 窗三件批 件1;[ref]/[ref] 承诺件)—— READ 容纳面的 center 下发形(`CenterA2aPeer` 的
  * 同族:一个 additive 顶层域,server 声明它才不会被静默丢弃)。四个成员逐一对应部署 env 的四键
  * (`READ_FACE` / `READ_DENY_PATTERNS` / `READ_DENY_BUILTIN_TIERS` / `READ_DENY_BUILTIN_EXCLUDE`),
  * 消费半场 = `config-center/read-face.ts` `applyCenterReadFace`。
@@ -192,11 +178,11 @@ export interface CenterReadFace {
     denyBuiltinExclude?: string[];
 }
 /**
- * #322 批1 的 wire 面(`EffectiveConfig.limits`)。**全 optional**:缺席 = 本域不管这一键 ⇒ 该键回 env
+ * [ref] 批1 的 wire 面(`EffectiveConfig.limits`)。**全 optional**:缺席 = 本域不管这一键 ⇒ 该键回 env
  * 基线(非粘,applyRuntimeHot 的 NON-STICKY 同族纪律 —— 「缺席=保上一个 center 值」会把撤回的治理永久冻住)。
  *
  * 🔴 类型是**到货 JSON 的声明**,不是运行时保证(local 腿的 eff 来自原始 JSON):每个键在 stage 侧都
- * 逐个验型验域,坏值 ⇒ 整批拒 + 旧值继续服务(#123 响亮拒)。
+ * 逐个验型验域,坏值 ⇒ 整批拒 + 旧值继续服务([ref] 响亮拒)。
  */
 export interface EffectiveLimits {
     /** 每 principal 每分钟请求上限;**0 = 关**(关断哨兵,不是缺席)。 */
@@ -234,7 +220,7 @@ export interface EffectiveLimits {
 export interface EffectiveConfig {
     version: number;
     updatedAt: string;
-    /** [2373]B-6:default/tierGroups/activeTierGroup 收进类型面(registry-core 0.13.0 已声明,
+    /** [ref]B-6:default/tierGroups/activeTierGroup 收进类型面(registry-core 0.13.0 已声明,
      *  types.d.ts:641/679/724)——此前 wire 面靠「JSON verbatim + 消费方结构读」逃逸,投影/消费两侧
      *  各自 as 宽铸。tierGroups 上游是 ZodDefault(合规 center 恒发),但本类型描述的是**到货 JSON**
      *  (含非合规/旧存量 center),故仍标 optional——消费方 resolveActiveTiers 自身容缺。 */
@@ -246,14 +232,8 @@ export interface EffectiveConfig {
         tierGroups?: unknown;
         activeTierGroup?: string;
     };
-    /** OPTIONAL since registry-core 0.7 deleted the teams domain: a 0.7+ center /effective payload
-     *  has NO teams key (collab is its successor). Absent/empty ⇒ registerTeams resets to BUILTIN_TEAMS (the
-     *  permanent builtin base). */
-    teams?: {
-        teams: CenterTeam[];
-    };
-    /** registry-core 0.7 collab domain (teams' successor) — consumed by the slice-① read-only
-     *  projection (projectCollabToTeams → registerTeams). Both lanes carry it: the remote worker /effective view
+    /** registry-core 0.7 collab domain (teams' successor) — consumed by the slice-1.5 projection
+     *  (projectCollabToWorkflows → registerCollabWorkflows). Both lanes carry it: the remote worker /effective view
      *  ships collab, and local FileConfigStore reads config.d/collab.json (PORTABLE_DOMAINS includes collab). */
     collab?: {
         templates: CollabTemplateWire[];
@@ -281,25 +261,26 @@ export interface EffectiveConfig {
             enabled?: boolean;
         }>;
     };
-    /** Fleet governance/limit gates (phase-2, center SERVICE-INTEGRATION「Runtime 治理/限额闸」). All restart-to-apply,
-     *  non-secret, all center `.optional()` (center `f95438a`): absent = unmanaged → keep env; present (incl. an
-     *  explicit 0/[] = "publish OFF") = override. Consumption precedence is in `applyRuntimeGates`. */
+    /** `runtime` 域 = **限额残余五键**,与 settings-schema `RuntimeConfig` 的键集逐字相等([ref] 件3 对账门
+     *  test/settings-schema-consumption-gates.test.ts 读 dist `RuntimeConfig.shape` 钉集合等式)。全部 center
+     *  `.optional()`(center `f95438a`):缺席 = 不管 → 保 env;在场(含显式 0 = "publish OFF")= 覆盖。
+     *  [ref] 批1 起五键全是**热**键(属主 stage-limits,boot+refresh 双腿);`limits` 域是它们的继任发布位
+     *  (两处同现 ⇒ limits 赢,见 {@link EffectiveConfig.limits})。
+     *
+     *  🔴 治理三件(autonomy / commandPolicy / approvalRequire)**不在这里**([ref] 件3 退役键清除):它们自
+     *  settings-schema 0.6 起住 `governance` 域,0.7.1 撤了 runtime 位的双写镜像;此后 `RuntimeConfig` 是 strip
+     *  的 zod object,两条腿(远端 `readEffectiveWire` / 本地 FileConfigStore→`buildEffective`)都把旧位 strip
+     *  掉、由 `legacyGovernanceFromRuntime` 抬进 governance ⇒ 本仓在 runtime 位上读它们的每一行都是死码。
+     *  旧类型面上留着这三键,让 `runtime-gates` 重启片一直读着一个生产上恒缺席的位(审批闸收紧静默不生效)。 */
     runtime?: {
         rateLimitPerMin?: number;
-        approvalRequire?: string[];
         maxTaskCostUsd?: number;
         maxTaskTokens?: number;
         maxPrincipalCostUsd?: number;
         costQuotaWindowSec?: number;
-        /** Runtime governance second baton (center §10): autonomy mode + per-command rules. UNLIKE the 6 gates above,
-         *  these are per-request HOT (read live in resolveSpec, not baked into boot middleware) → applied on boot AND
-         *  refresh by `applyRuntimeHot` (NOT in RUNTIME_GATE_KEYS / restart-to-apply). Same presence rule (undefined =
-         *  unmanaged → keep). */
-        autonomy?: Autonomy;
-        commandPolicy?: CommandRule[];
     };
     /**
-     * #322 批1 —— **limitsHttp 组的热更新发布域**(design/322 §6 批1)。
+     * [ref] 批1 —— **limitsHttp 组的热更新发布域**([ref] §6 批1)。
      *
      * 🔴 为什么是**新顶层域**而不是往 `runtime` 里加键(亲验,不是推测):registry-core 的 `RuntimeConfig`
      * 是 zod `"strip"` 对象,`runtime` 里的未知键在**两条腿上都会被静默剥掉**(local 腿实测
@@ -320,21 +301,23 @@ export interface EffectiveConfig {
     limits?: EffectiveLimits;
     /** 142-S4(registry-core 0.10.0 第 15 域):center 项目登记簿。wire 面 verbatim JSON —
      *  registry-core `ProjectsConfig` 的形状是 `{projects: Record<projectId, ProjectRegistration>}`(skills/mcp
-     *  同款域包裹)。[2373]B-8:裸 Record 联合臂随 apply-effective 的宽读一起删(0.13.0 只有包裹形,
+     *  同款域包裹)。[ref]B-8:裸 Record 联合臂随 apply-effective 的宽读一起删(0.13.0 只有包裹形,
      *  裸形无 producer)。消费=applyEffective → config.projects(displayName/gitRemotes/defaultScopes
      *  三个 runtime 字段;审计字段不进 ServiceConfig)。 */
     projects?: {
         projects?: Record<string, unknown>;
     };
-    /** registry-core 0.6:治理三件(autonomy/commandPolicy/approvalRequire)拆新 governance 域=真值;
-     *  过渡期 effective 在 runtime 位双写镜像。读取优先 governance 新位、runtime 旧位 fallback(顺序契约:
-     *  消费端先切换、确认后 center 才撤双写,治理闸零 fail-open 窗口)。 */
+    /** settings-schema 0.6 起治理三件(autonomy/commandPolicy/approvalRequire)的**唯一**承运域(0.7.1 撤
+     *  runtime 位双写镜像;顺序契约当年已走完:消费端先切、center 再撤)。键集与 schema `GovernanceConfig.shape`
+     *  逐字相等([ref] 件3 对账门钉)。消费:autonomy/commandPolicy 逐请求热(`stageRuntimeHot`,boot+refresh);
+     *  approvalRequire boot-baked(`stageApprovalGate`,refresh 不写)⇒ 变更由 `runtime-gates` 重启片通告。
+     *  同一 presence 规则(undefined = 不管 → 保 env / 回基线)。 */
     governance?: {
         autonomy?: Autonomy;
         commandPolicy?: CommandRule[];
         approvalRequire?: string[];
     };
-    /** plugins 域(registry-core 0.5 additive;契约冻结 [1361]②/[1362]/[1366]①,消费半场 2026-07-28
+    /** plugins 域(registry-core 0.5 additive;契约冻结 [ref]②/[ref]/[ref]①,消费半场 2026-07-28
      *  开工车):center 只存"插件从哪来"(PluginSpec 引用,永不承载可执行字节);worker 半场在
      *  capabilities/center-plugins.ts `applyCenterPlugins`(https-only+ALLOW_HOSTS 纵深复验/sha 钉扎/
      *  隔离 clone/LKG/撞名让位)。此前本 interface 无此键 ⇒ wire 上的 plugins 被 server 静默丢弃。 */

package/dist/config-invariants.d.ts

@@ -1,5 +1,5 @@
 /**
- * #322 —— **跨键不变量的单源表**(design/322 §2 A′,codex 设计审 F2)。
+ * [ref] —— **跨键不变量的单源表**([ref] §2 A′,codex 设计审 F2)。
  *
  * 病灶:boot 期的跨域不变量(拒启 throw)散在 `config.ts` 的装配尾与 `main.ts` 的开头。把配置改热之后,
  * 每一条都变成一个**热路径上的漏检**:一次发布可以在运行期造出 boot 期会当场拒启的姿态(无鉴权写面被

package/dist/config-lkg.js

@@ -47,7 +47,7 @@ export async function loadLkg(path, worker) {
     const eff = p.effective;
     if (typeof eff.version !== "number")
         return { reason: "bad effective.version" };
-    for (const [domain, arrayKey] of [["models", "models"], ["teams", "teams"], ["skills", "skills"], ["mcp", "servers"], ["scenarios", "scenarios"], ["runtime", null]]) {
+    for (const [domain, arrayKey] of [["models", "models"], ["skills", "skills"], ["mcp", "servers"], ["scenarios", "scenarios"], ["runtime", null]]) {
         const v = eff[domain];
         if (v === undefined)
             continue;
@@ -59,6 +59,12 @@ export async function loadLkg(path, worker) {
                 return { reason: `bad effective.${domain}.${arrayKey}` };
         }
     }
+    {
+        const rt = eff.runtime;
+        if (rt && (rt.autonomy !== undefined || rt.commandPolicy !== undefined || rt.approvalRequire !== undefined)) {
+            return { reason: "legacy runtime governance keys (pre-0.7.1 mirror shape; no contract producer since LKG shipped) — refusing rather than silently dropping governance" };
+        }
+    }
     const promptsRaw = p.effective.prompts;
     if (promptsRaw !== undefined && !validatePromptsDomain(promptsRaw).ok)
         return { reason: "prompts face fails re-validation" };

package/dist/config-provider.d.ts

@@ -3,7 +3,7 @@ import { type EffectiveConfig as AgentConfigEffective } from "@sema-agent/settin
 import { fetchEffective as remoteFetchEffective, fetchSkillContent as remoteFetchSkillContent, type EffectiveConfig } from "./config-center/facade.js";
 /** Result of a `fetchEffective` — EXACTLY the config-center's return: the effective config + its etag, or
  *  `null` for "unchanged" (remote 304; local: the version matched the caller's prior etag).
- *  `domainErrors`([898] registry-core 0.10.12 tolerant seam,local lane only):catalog 域坏文件不再
+ *  `domainErrors`([ref] registry-core 0.10.12 tolerant seam,local lane only):catalog 域坏文件不再
  *  连坐全包回落 env——坏域按该域 schema default 落+错误单列,好域照常生效;caller(main.ts)对每条打
  *  per-domain warn 点名坏域。gate 域(governance/rosters/…)坏文件 tolerant 仍 throw(READ 容错不放宽
  *  gate fail-loud,registry-core 半场精化)——那条路走既有的整包 catch。 */
@@ -101,7 +101,7 @@ export declare class LocalConfigProvider implements ConfigProvider {
     #private;
     readonly kind: "local";
     private readonly store;
-    /** [875]b 可观测性:config_loaded 日志要能回答「到底读的哪个目录」——复验实录:只设 LOCAL_DATA_ROOT 时
+    /** [ref]b 可观测性:config_loaded 日志要能回答「到底读的哪个目录」——复验实录:只设 LOCAL_DATA_ROOT 时
      *  config.d 静默读不到且 0 模型无告警(CONFIG_LOCAL_DIR 才是本 lane 的选目录旋钮)。 */
     readonly root: string;
     constructor(root: string, store?: FileConfigStore);

package/dist/config-provider.js

@@ -126,8 +126,8 @@ export function mapToServiceEffective(eff, version) {
             ...(eff.models.tierGroups !== undefined ? { tierGroups: eff.models.tierGroups } : {}),
             ...(eff.models.activeTierGroup !== undefined ? { activeTierGroup: eff.models.activeTierGroup } : {}),
         },
-        teams: { teams: [] },
         ...(eff.collab?.templates?.length ? { collab: { templates: eff.collab.templates } } : {}),
+        ...(eff.plugins?.plugins?.length ? { plugins: { plugins: eff.plugins.plugins } } : {}),
         skills: {
             skills: (eff.skills.skills ?? []).map((s) => ({
                 name: s.name,