@sema-agent/server 7.101.1 → 7.103.0

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

@@ -46,8 +46,8 @@ export declare function createMcpRevocationLedger(onChange?: (ev: {
 }) => void): McpRevocationLedger;
 /** 一拍 EffectiveConfig 的 ENABLED MCP 服务器条目表(`resolveMcpServers` 同判据:`enabled !== false`;
  *  值=整条目的 key 排序 JSON 指纹,Map 插入序=发布序);mcp 域缺席 ⇒ `null`(台账不动)。
- *  指纹序列化器 = restart-signal 的 `stableStringify`([ref] 2026-08-31 起同源:此前本文件持一份**逐字相同**的
- *  私有复刻 `fingerprintOf`,两份在全部输入上字节恒等,合并零行为差,golden 钉 test/canonical-json-golden.test.ts)。
+ *  指纹序列化器 = `@sema-agent/settings-schema/hash` 的 `stableStringify`(S-778 起;[ref] 2026-08-31 起与 restart-signal 同源:此前本文件
+ *  持一份**逐字相同**的私有复刻 `fingerprintOf`;JSON 形输入上字节恒等,golden 钉 test/canonical-json-golden.test.ts)。
  *  两处指纹仍只在各自域内自比、不跨域比对——同源只是去掉一份多余的复刻,不引入跨域约束;也**不**改用
  *  `src/canonical-json.ts`(undefined 值键语义不同,见 restart-signal.ts 该函数顶注)。 */
 export declare function enabledMcpEntries(mcp: {

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

@@ -1,4 +1,4 @@
-import { stableStringify } from "./restart-signal.js";
+import { stableStringify } from "@sema-agent/settings-schema/hash";
 export function createMcpRevocationLedger(onChange) {
     let baseline;
     let seen;

package/dist/config-center/read-warnings.d.ts

@@ -25,7 +25,7 @@
  * 候选门整拒,而它在 1.10.0 上零告警零 domainErrors(亲验读数)。兼容臂的关窗观测归属主(settings-schema 的
  * `onWarning` 流),不借候选门这条带副作用的通道传信息。
  */
-import { type ConfigPath, type EffectiveReadWarning } from "@sema-agent/settings-schema";
+import { type EffectiveReadWarning } from "@sema-agent/settings-schema";
 /** 折叠产物:`scope` 决定消费方做什么 —— `"domain"` 进候选门(`domainErrors`),`"entry"` 进逐条丢弃面(`droppedEntries`)。 */
 export type FoldedReadWarning = {
     readonly scope: "domain";
@@ -58,72 +58,43 @@ export declare function describeSchemaIssueFields(error: unknown): string[];
 /** null = 不入诊断面(`hosts-grandfathered` / `legacy-governance-lifted`:值已被收编接受,与本地店同口径)。 */
 export declare function foldEffectiveReadWarning(w: EffectiveReadWarning): FoldedReadWarning | null;
 /**
- * 🔴 S-712 —— 一条被 schema 逐条丢掉的**启用**目录条目的身份(模型面墓碑的来源;载体 = `EffectiveConfig.models.droppedIdentities`,
+ * 🔴 S-712 —— 一条被 schema 逐条丢掉的**启用**、**有名**目录条目的身份(模型面墓碑的来源;载体 = `EffectiveConfig.models.droppedIdentities`,
  * 随 effective 走 —— 盘上 LKG 从同一个对象落盘,重启从 LKG 起服墓碑不丢)。
  *
  * 为什么要交出身份:条目被丢之后它的名字从目录里消失,而档位增广(core `expandTiers`)会把一个**空出来的**档位词 / CC 别名
  * (条目恰好叫 `sonnet` / `pro` …)重新铸到另一条条目上 —— 显式点它的请求与点名它的角色绑定就这样被静默换了目的地
  * (gpt-6 腿 F2 / F3,真复现)。身份进 `modelRefusals` 之后,不变量 `refused-names-not-minted` 才判得到它。
  *
- * 🔐 纯身份,不含值:`name` / `id` / `provider` 只取**字符串**(条目自己写的词,本就进日志与拒因句),`fields` 是坏字段的
- * **键路径**,`issues` 是 {@link describeSchemaIssues} 的一行(键名 + 类型词)—— 被丢条目的原值(可能是一段贴错位置的凭据)
- * 绝不进载体、日志、LKG 与 400 拒因句。
+ * 🔐 纯身份,不含值:`name` / `id` 取自告警的 `identity`(settings-schema 6.1.0:只取被丢条目原文里的字符串形,脱敏器会改动的串
+ * 整键扣下),`fields` 是坏字段的**键路径**,`issues` 是 {@link describeSchemaIssues} 的一行(键名 + 类型词)—— 被丢条目的原值
+ * (可能是一段贴错位置的凭据)绝不进载体、日志、LKG 与 400 拒因句。
  */
 export interface DroppedModelIdentity {
     /** 出门形坐标(`models.1`),与同一次读的 `droppedEntries[].entry` 同一串。 */
     readonly entry: string;
-    /** 条目写的 `name`。**缺席 = 身份证明不了**(只剩一形:原文档与本次解析对不上 / 坐标在原文档里不存在,见 {@link droppedEntryIdentity})
-     *  ⇒ 模型面整组拒:证明不了的名字无从证明它不被增广铸出。原文档那一格读到了却没有字符串名的行**不进**载体(没有可保留的名字,
-     *  与停用同处置 —— 7.101.0 验修轮 V-2)。 */
-    readonly name?: string;
+    /** 条目写的 `name`(读腿只为有名的行铸载体)。载体上缺了它 = 载体形不对(LKG 载体被改 / 手写 effective)⇒ 模型面整组拒,
+     *  判在 `model-entry-refusal.ts` `judgeCatalogEntries`。 */
+    readonly name: string;
     readonly id?: string;
-    readonly provider?: string;
     readonly fields: readonly string[];
     readonly issues: string;
 }
-/** 本次读的模型域**原文**与**解析产物**(两腿各自手里都有这两件:远端 = 响应体与 `readEffectiveWire` 输出;本地 = 盘上
- *  `config.d/models.json` 与 `FileConfigStore` 输出)。 */
-export interface ModelsDomainSource {
-    /** 模型域的原始文档(`{ models: [...], roles, … }`);读不到 ⇒ `undefined`(身份一律证明不了)。 */
-    readonly raw: unknown;
-    /** 同一次读解析后幸存的条目(schema 逐条丢弃之后的 `models.models`)。 */
-    readonly parsed: readonly unknown[] | undefined;
-}
-/**
- * 一条被丢行在原文档里那一格的读数 —— **三态**(7.101.0 验修轮 V-2,规则变小:「读不出」只剩一种含义):
- *  · `named`:格读到了、`name` 是字符串 ⇒ 身份已定(启用的铸墓碑,停用的不是);
- *  · `nameless`:格读到了、没有字符串 `name`(`null` / 数 / 整格不是对象)⇒ 身份**也**已定:**没有可保留的名字** —— 请求、
- *    `@`-mention、角色绑定都点不到一个非字符串名,档位增广也铸不出它 ⇒ 与 `enabled:false` 同处置(不是墓碑、不拒组);
- *  · `undefined`(由 {@link droppedEntryIdentity} 答):格读不到 —— 坐标在原文档里不存在;调用方在原文档与本次解析对不上
- *    (`sameRead` 假)时根本不来读 ⇒ 两者同是「身份证明不了」,交一条不带 `name` 的载体(模型面据此整组拒)。
- * 此前 `nameless` 被折进「读不出」⇒ 一行 `{ name: null }` 的坏行(哪怕是停用的)就让整个模型面被拒(codex 验修腿 V-2,boot 腿对
- * v7.100.0 的窄回归:那时 boot 对同一文档宽容采纳幸存条目)。
- */
-export type DroppedEntryCell = {
-    readonly kind: "named";
-    readonly name: string;
-    readonly id?: string;
-    readonly provider?: string;
-    readonly enabled: boolean;
-} | {
-    readonly kind: "nameless";
-};
-/**
- * 🔴 S-712 **唯一**的身份读法:按告警坐标(`path`,模型域文档内的段坐标 —— settings-schema 已把它回写成原文档坐标)回读
- * 原文档那一格,答 {@link DroppedEntryCell} 三态之一;坐标在原文档里走不通 ⇒ `undefined`(格读不到)。字符串才算
- * (`name` / `id` / `provider`),`enabled` 只认字面 `false` 为停用。
- * settings-schema 6.1.0 的 `entry-dropped` 自带 `name` / `id` 到货后,本函数改读告警(同一只函数,换数据源),原文档入参随之删除。
- */
-export declare function droppedEntryIdentity(rawDoc: unknown, path: ConfigPath): DroppedEntryCell | undefined;
 /**
  * 两条读腿(远端 `http-client.ts` / 本地 `config-provider.ts`)共用的**分面单点**:折叠产物按 `scope` 分进候选门
  * (`domainErrors`)与逐条丢弃面(`droppedEntries`)。`switch` 穷举 —— 加一种 scope 不补臂 = 编译红,两腿不会各分各的。
  * 文案**未脱敏**:进日志流之前各腿在自己的产出边界上过 `redactConfigError`(与 `domainErrors` 同一道)。
- * S-712:同一次折叠把被丢**模型目录条目**的身份交出(`droppedIdentities`,见 {@link DroppedModelIdentity}),按 {@link DroppedEntryCell}
- * 三态分流:有名且启用 ⇒ 墓碑;停用的、没有字符串名的 ⇒ 不进载体(停用 = 不在目录,与 7.100.0 同义;无名 = 没有可保留的名字);
- * 格读不到 / 原文档对不上 ⇒ 不带 `name` 的载体(证明不了)。坏行本身照样走 `droppedEntries`(坐标 + 字段,不带值)。
+ *
+ * 🔴 S-712 身份规则(一条,数据源 = 告警自带的 `identity`,settings-schema 6.1.0 在**同一次解析**里从被丢条目原文取 —— 本仓不再回读原文档):
+ * **`identity.name` 是字符串 ⇒ 有名;有名且 `identity.enabled !== false` ⇒ 墓碑(进载体);其余一律不进载体。**
+ *  · 有名而停用 ⇒ 停用 = 不在目录(与 7.100.0 同义);
+ *  · 没有字符串名 —— `identity` 在场而无 `name`,或 `identity` 整个缺席 ⇒ **无名可留**,与停用同处置。按 settings-schema 6.1.0 的铸点
+ *    (`config-fns.ts` `readEntryIdentity`),「没有名」有两个成因、刻意不分:原文 `name` 不是字符串(`null` / 数 / 整行不是对象),
+ *    或是字符串但脱敏器会改动它(秘密形 —— 扣下不出门)。后者对本判据同样安全:档位增广只铸闭集词(`ultra` / `max` / `pro` /
+ *    `flash` / `lite`、CC 别名、`best`),没有一个是秘密形,一个被扣下的名字无从被铸出;它的代价只是显式点它的请求拿到「未知模型」
+ *    而不是 `request.model_unavailable`(那个名字本来也不许进日志与拒因句)。
+ * 坏行本身照样走 `droppedEntries`(坐标 + 字段,不带值)。
  */
-export declare function splitFoldedReadWarnings(warnings: readonly EffectiveReadWarning[], models: ModelsDomainSource): {
+export declare function splitFoldedReadWarnings(warnings: readonly EffectiveReadWarning[]): {
     domainErrors: Array<{
         domain: string;
         error: string;

package/dist/config-center/read-warnings.js

@@ -68,38 +68,10 @@ export function foldEffectiveReadWarning(w) {
         }
     }
 }
-const isRecord = (v) => typeof v === "object" && v !== null && !Array.isArray(v);
-export function droppedEntryIdentity(rawDoc, path) {
-    let at = rawDoc;
-    for (const seg of path) {
-        if (typeof seg === "number") {
-            if (!Array.isArray(at) || !Number.isInteger(seg) || seg < 0 || seg >= at.length)
-                return undefined;
-            at = at[seg];
-        }
-        else {
-            if (!isRecord(at) || !Object.hasOwn(at, seg))
-                return undefined;
-            at = at[seg];
-        }
-    }
-    if (!isRecord(at) || typeof at.name !== "string")
-        return { kind: "nameless" };
-    return { kind: "named", name: at.name, ...(typeof at.id === "string" ? { id: at.id } : {}), ...(typeof at.provider === "string" ? { provider: at.provider } : {}), enabled: at.enabled !== false };
-}
 function isModelEntryDrop(w) {
     return w.kind === "entry-dropped" && w.domain === "models" && w.path.length === 2 && w.path[0] === "models" && typeof w.path[1] === "number";
 }
-function sameRead(source, dropped) {
-    const rawModels = isRecord(source.raw) ? source.raw.models : undefined;
-    if (!Array.isArray(rawModels) || source.parsed === undefined)
-        return false;
-    if ([...dropped].some((i) => i >= rawModels.length))
-        return false;
-    const survivors = rawModels.filter((_, i) => !dropped.has(i));
-    return survivors.length === source.parsed.length && survivors.every((s, k) => isRecord(s) && isRecord(source.parsed[k]) && s.name === source.parsed[k].name);
-}
-export function splitFoldedReadWarnings(warnings, models) {
+export function splitFoldedReadWarnings(warnings) {
     const domainErrors = [];
     const droppedEntries = [];
     for (const w of warnings) {
@@ -119,28 +91,14 @@ export function splitFoldedReadWarnings(warnings, models) {
             }
         }
     }
-    const modelDrops = warnings.filter(isModelEntryDrop);
-    const readable = sameRead(models, new Set(modelDrops.map((w) => w.path[1])));
     const droppedIdentities = [];
-    for (const w of modelDrops) {
-        const unproven = { entry: formatConfigPath(w.path), fields: describeSchemaIssueFields(w.error), issues: describeSchemaIssues(w.error) ?? "(schema issues unreadable)" };
-        const cell = readable ? droppedEntryIdentity(models.raw, w.path) : undefined;
-        if (cell === undefined) {
-            droppedIdentities.push(unproven);
+    for (const w of warnings) {
+        if (!isModelEntryDrop(w))
             continue;
-        }
-        switch (cell.kind) {
-            case "nameless":
-                break;
-            case "named":
-                if (cell.enabled)
-                    droppedIdentities.push({ ...unproven, name: cell.name, ...(cell.id !== undefined ? { id: cell.id } : {}), ...(cell.provider !== undefined ? { provider: cell.provider } : {}) });
-                break;
-            default: {
-                const never = cell;
-                throw new Error(`unhandled dropped-entry cell: ${JSON.stringify(never)}`);
-            }
-        }
+        const identity = w.identity;
+        if (identity?.name === undefined || identity.enabled === false)
+            continue;
+        droppedIdentities.push({ entry: formatConfigPath(w.path), name: identity.name, ...(identity.id !== undefined ? { id: identity.id } : {}), fields: describeSchemaIssueFields(w.error), issues: describeSchemaIssues(w.error) ?? "(schema issues unreadable)" });
     }
     return { domainErrors, droppedEntries, droppedIdentities };
 }

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

@@ -1,3 +1,4 @@
+import type { RestartSignal } from "@sema-agent/settings-schema/fleet";
 import type { EffectiveConfig } from "./types.js";
 export type RestartSlice = "skills" | "mcp" | "a2a" | "scenarios" | "degrade-route" | "read-face" | "memory-consolidation";
 /** What the CALLER must contribute about boot-baked catalog consumers that live OUTSIDE the Runner — the
@@ -31,28 +32,14 @@ export interface RestartSliceCtx {
      *  = 装载器的出厂名单 `DEFAULT_PLUGIN_ALLOW_HOSTS`。 */
     pluginsAllowHosts?: readonly string[];
 }
-/** Structured restart signal an orchestrator consumes (GET /health → `restart`). Change-detected against the
- *  process's BOOT config, NOT presence — so it stays absent when nothing baked-at-boot changed (presence would
- *  re-fire every refresh → a restart LOOP). `restartRequired` is always true when this object exists. */
-export interface RestartSignal {
-    restartRequired: true;
-    /** Which restart-to-apply slices differ from the value baked at boot. */
+/** S-741(车OG):本引擎发布的重启信号。形的唯一定义是 settings-schema 6.1.0 `RestartSignal`(`{ reasons, version, since }`,在场即信号,
+ *  不夹 `restartRequired` 布尔;本地手写的那份接口已删),这里只把 `reasons` 收窄到本文件的闭集 {@link RestartSlice} —— 写口
+ *  (`boot/config-center.ts` `publishRestart`)按它收,拼错 / 已退役的词编译红(opus 对抗腿 #2:直接用上游型时 `reasons` 是
+ *  `string[]`,闭集的编译期判据丢了)。`/health.restart` 与 fleet 心跳 `restart` 两个出口交 config-center 同一只 `restartState()`
+ *  的同一个对象,按契约形出门。 */
+export type EngineRestartSignal = RestartSignal & {
     reasons: RestartSlice[];
-    /** The config-center version that currently differs from boot (latest seen). */
-    version: number;
-    /** 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,19 +1,9 @@
 import { resolveActiveTiers } from "@sema-agent/settings-schema";
+import { stableStringify } from "@sema-agent/settings-schema/hash";
 import { DEFAULT_PLUGIN_ALLOW_HOSTS, materializablePlugins } from "../capabilities/center-plugins.js";
 import { resolveDefaultModelName } from "./apply-effective.js";
 import { CENTER_READ_FACE_LIVE_KEYS } from "./read-face.js";
 const RESTART_SLICES = ["skills", "mcp", "a2a", "scenarios", "degrade-route", "read-face", "memory-consolidation"];
-export function stableStringify(v) {
-    if (v === null || typeof v !== "object")
-        return JSON.stringify(v) ?? "null";
-    if (Array.isArray(v))
-        return `[${v.map(stableStringify).join(",")}]`;
-    const obj = v;
-    return `{${Object.keys(obj)
-        .sort()
-        .map((k) => `${JSON.stringify(k)}:${stableStringify(obj[k])}`)
-        .join(",")}}`;
-}
 function enabledOnly(rows) {
     if (!rows)
         return null;
@@ -73,7 +63,7 @@ export function restartReasons(boot, current, ctx) {
         if (stableStringify(b) === stableStringify(c))
             return false;
         if (s === "mcp" && ctx?.mcpRevocationLive === true && Array.isArray(b) && Array.isArray(c) && c.length < b.length) {
-            const bootFps = b.map(stableStringify);
+            const bootFps = b.map((row) => stableStringify(row));
             let bi = 0;
             const pureRemoval = c.every((row) => {
                 const fp = stableStringify(row);

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

@@ -265,9 +265,11 @@ export interface EffectiveConfig {
         tierGroups?: unknown;
         activeTierGroup?: string;
         /** 🔴 S-712 —— **本仓读腿铸的**载体(不是 wire 键:中心在模型域里写同名键会被 schema 当未知键剥掉并进候选门):这次读
-         *  被 schema 逐条丢掉的**启用**目录条目的身份。模型面 stage 把它们铸成 `config.model_entry_invalid` 墓碑进 `modelRefusals`,
+         *  被 schema 逐条丢掉的**启用**、**有名**目录条目的身份(取 settings-schema 6.1.0 告警自带的 `identity`,见
+         *  `read-warnings.ts` `splitFoldedReadWarnings`)。模型面 stage 把它们铸成 `config.model_entry_invalid` 墓碑进 `modelRefusals`,
          *  不变量 `refused-names-not-minted` 据此判增广有没有把它们的名字铸到别的条目上。挂在 effective 上(而不是读结果旁边)是为了
-         *  **随 effective 落 LKG**:重启从 LKG 起服时墓碑还在。形见 {@link DroppedModelIdentity}(纯身份,不含值)。 */
+         *  **随 effective 落 LKG**:重启从 LKG 起服时墓碑还在。形见 {@link DroppedModelIdentity}(纯身份,不含值);盘上形不对
+         *  (不是列表 / 行缺字符串 `name`)⇒ 模型面整组拒。 */
         droppedIdentities?: DroppedModelIdentity[];
     };
     /** registry-core 0.7 collab domain (teams' successor) — consumed by the slice-1.5 projection

package/dist/config-provider.js

@@ -1,7 +1,6 @@
 import { readMcpSourceLabel } from "./mcp-source-label.js";
 import { createHmac, randomBytes } from "node:crypto";
 import { splitFoldedReadWarnings, withDroppedIdentities } from "./config-center/read-warnings.js";
-import { readFile, stat } from "node:fs/promises";
 import { FileConfigStore } from "@sema-agent/settings-schema/node";
 import { findSkillContent, skillContentHash, refIntegrityIssues, createSiblingResolver, formatConfigPath, REF_CHECKED_DOMAINS, } from "@sema-agent/settings-schema";
 import { redactSecrets } from "./trace/redact.js";
@@ -12,24 +11,6 @@ const OPERAND_FINGERPRINT_KEY = randomBytes(16);
 function redactConfigError(text) {
     return redactSecrets(text).replace(/"[^"]*"|'[^']*'/g, (m) => `"#${createHmac("sha256", OPERAND_FINGERPRINT_KEY).update(m.slice(1, -1)).digest("hex").slice(0, 8)}"`);
 }
-async function readRawDomainDoc(path) {
-    try {
-        const doc = JSON.parse(await readFile(path, "utf8"));
-        return { ok: true, doc };
-    }
-    catch (e) {
-        return { ok: false, why: e instanceof Error ? e.message : String(e) };
-    }
-}
-async function statSignature(path) {
-    try {
-        const st = await stat(path, { bigint: true });
-        return { ok: true, sig: `${st.ino}:${st.size}:${st.mtimeNs}:${st.ctimeNs}` };
-    }
-    catch (e) {
-        return { ok: false, why: e instanceof Error ? e.message : String(e) };
-    }
-}
 export const BOOT_FETCH_DEFERRED = Symbol("boot-fetch-deferred");
 export function raceBootFetch(fetch, budgetMs) {
     if (budgetMs <= 0)
@@ -101,9 +82,7 @@ export class LocalConfigProvider {
             if (issues.length > 0)
                 refErrors.push({ domain: d, error: issues.map((i) => `${formatConfigPath(i.path)}: ${redactConfigError(i.message)}`).join("; ") });
         }
-        const modelDropped = readWarnings.some((w) => w.kind === "entry-dropped" && w.domain === "models");
-        const rawModels = modelDropped ? await this.#provenRawModelsDoc(store, eff.version) : undefined;
-        const folded = splitFoldedReadWarnings(readWarnings, { raw: rawModels, parsed: eff.models.models ?? [] });
+        const folded = splitFoldedReadWarnings(readWarnings);
         const parseErrors = folded.domainErrors.map((w) => ({ domain: w.domain, error: redactConfigError(w.error) }));
         const droppedEntries = folded.droppedEntries.map((d) => ({ ...d, error: redactConfigError(d.error) }));
         const errors = [...domainErrors.map((de) => ({ domain: de.domain, error: redactConfigError(de.error) })), ...parseErrors, ...refErrors];
@@ -115,32 +94,6 @@ export class LocalConfigProvider {
             ...(droppedEntries.length > 0 ? { droppedEntries } : {}),
         };
     }
-    async #provenRawModelsDoc(store, version) {
-        const path = store.domainPath("models");
-        const unproven = (why) => {
-            logger.warn("config_models_raw_unproven", { dir: this.root, why: redactConfigError(why), note: "the dropped model entries of this read cannot be identified from the exact snapshot that was parsed — the candidate's model plane is refused as a group (no tombstone is taken from another version of the file); the next poll re-reads" });
-            return undefined;
-        };
-        const s1 = await statSignature(path);
-        const raw = await readRawDomainDoc(path);
-        let again;
-        try {
-            again = (await (this.#injectedStore ?? new FileConfigStore(this.root)).getEffective({ tolerant: true })).effective.version;
-        }
-        catch (e) {
-            again = `re-parse failed: ${e instanceof Error ? e.message : String(e)}`;
-        }
-        const s2 = await statSignature(path);
-        if (!raw.ok)
-            return unproven(`config.d/models.json unreadable on the identity re-read: ${raw.why}`);
-        if (typeof again !== "number")
-            return unproven(again);
-        if (!s1.ok || !s2.ok || s1.sig !== s2.sig)
-            return unproven("config.d/models.json changed (or could not be stat-ed) while its identity re-read was being proven");
-        if (again !== version)
-            return unproven("config.d changed between the parse and the identity re-read (content version differs)");
-        return raw.doc;
-    }
     async fetchSkillContent(contentHash) {
         const skills = await this.store.getDomain("skills");
         if (!skills)

package/dist/config-types.d.ts

@@ -18,6 +18,7 @@ import type { InfraCostRates } from "./observability/cost-taxonomy.js";
 import type { Autonomy, CommandRule } from "./runtime-governance.js";
 import type { CenterCredentialSource } from "./center-credential.js";
 import type { GitApiKind } from "./git-api-kind.js";
+import { DRAIN_GRACE_FLOOR_MS } from "@sema-agent/settings-schema/fleet";
 /** [ref]:记忆向量面的 embedder 坐标(env `MEMORY_EMBEDDER_*` 解析结果;单一属主 = 本类型,
  *  `plugins/memory-embedder.ts` 的工厂直接消费它,不复制形状)。语义与三问见
  *  {@link ServiceConfigFlat.memoryEmbedder}。纯数据 —— 端点原文照存(拼 `/embeddings` 是 transport
@@ -62,6 +63,71 @@ export interface RetentionSweepConfig {
  * 那道拒之后它即刻生效 —— 留着是为了「那天不必有人再猜一个数」。
  */
 export declare const MEMORY_CONSOLIDATION_MIN_INTERVAL_SEC = 300;
+/**
+ * Node 的 `setTimeout` delay 上界(2^31−1 ms ≈ 24.8 天)。**超过它的 delay 被静默折成 1ms** —— 任何「一个时长
+ * 旋钮的值最终会变成一次 `setTimeout` 的 delay」的键都必须在上界处拒启,不能夹取([ref] + codex r1-[high]:夹取
+ * 只是把一句谎换成另一句)。S-757 起从 `config.ts` 的模块私有常量提到本纯叶:解析器与配置目录的合法域句读
+ * 同一个数([ref]:边界不手抄)。
+ */
+export declare const MAX_TIMER_DELAY_MS = 2147483647;
+/**
+ * S-757(test [ref] / core #1125)—— `AUTO_MODE_CLASSIFIER_TIMEOUT_MS`(→ core `RunnerDeps.autoMode.timeoutMs`)
+ * 的**合法域**,闭区间、整数 ms。解析器(`config.ts`)与目录行(`config-catalog.ts`)共读这一处。
+ *
+ *  · **下界 1000**:亚秒值是「秒写成毫秒」的手滑形(`180` 想说三分钟,落地 180 ms ⇒ 每一级立即判「没裁」⇒ 门控
+ *    调用整条拒)。`0` 同拒:core 对这一座**没有**「关」的语义(d.ts 未写 0 的含义;分类器不判就走下一级 / 拒),
+ *    写 0 表达不出任何可执行的意图。
+ *  · **上界 = {@link MAX_TIMER_DELAY_MS}**:core 拿这个数直接武装 `setTimeout`(7.32.1 `dist/core/auto-mode.js`
+ *    `withDeadline`,座上不做值校验),更大的值被 Node 折成 1 ms —— 「抬上限」变成「立即超时」,方向正好反了。
+ *    **不另设更紧的政策上界**:这是**一级**梯子的等待上限(不是整次分类;`classifierFallback=main` 时最坏 =
+ *    两级 × 上限 + 一次装配),而本级调用同时收到 run 的中止信号(`withDeadline` 把外层 signal 接进本级),
+ *    run 被取消 / 硬 abort 时不靠这个数收尾。
+ */
+export declare const AUTO_MODE_CLASSIFIER_TIMEOUT_BOUNDS: {
+    readonly minMs: 1000;
+    readonly maxMs: 2147483647;
+};
+/**
+ * `DRAIN_GRACE_MS` 的**地板**(10s)—— 夹取(env,[ref] B 档)与中心 stage 校验(`stage-limits.ts` 的 `atLeast`)两条写入腿
+ * 都以它为下界,于是「排空窗」在任何写入通道上都不会短于它。**属主在 settings-schema**(`@sema-agent/settings-schema/fleet` 的
+ * `DRAIN_GRACE_FLOOR_MS`,drain 协议合同值;S-778 起本叶只转出口,不再本地铸同一个数)。S-752 起它从 `config.ts` 的
+ * `LIMITS_HTTP_FLOORS` 字面提到本叶:{@link DRAIN_SECOND_SIGNAL_MIN_GAP_BOUNDS} 的上界与配置目录的合法域句共读这一个数([ref]:
+ * 边界不手抄;目录模块不能值引 `config.ts` —— `config → server-secret-env → config-catalog` 已成链)。
+ */
+export { DRAIN_GRACE_FLOOR_MS };
+/**
+ * S-752(test [ref])—— `DRAIN_SECOND_SIGNAL_MIN_GAP_MS` 的**合法域**(闭区间、整数 ms)与缺省。解析器(`config.ts`)
+ * 与目录行(`config-catalog.ts`)共读这一处。
+ *
+ *  · **语义**:排空期里一发停止信号(SIGTERM / SIGINT)只有在与**排空起点**相隔 ≥ 本值时才算硬停意图;更近的是同一拍的
+ *    重复投递(壳心跳误判 / 编排器重试),记一行就忽略。
+ *  · **缺省 250**:人手连按两次的最短间隔量级 —— 同一毫秒的重复投递(事故形)远在其内,有意的第二发远在其外。
+ *  · **下界 0 = 关**:恒按「第二发 = 硬停」,即 7.101.x 行为逐字。0 在这里有真含义(不同于 `AUTO_MODE_CLASSIFIER_TIMEOUT_MS`
+ *    的 0),所以放行。
+ *  · **上界 = {@link DRAIN_GRACE_FLOOR_MS}**:本闸不能比**最短**可能的排空窗还宽 —— 更宽的值会让「排空期的第二发」在整个窗
+ *    里都不算数(信号面的硬梯子被静默摘掉,只剩 SIGKILL)。取地板而不是「≤ 本进程的 `DRAIN_GRACE_MS`」:后者是中心热改键,
+ *    boot 期跨键校验会被一次热改在运行期推翻;地板则在所有写入腿上都成立,无需第二处校验。
+ */
+export declare const DRAIN_SECOND_SIGNAL_MIN_GAP_BOUNDS: {
+    readonly minMs: 0;
+    readonly maxMs: 10000;
+};
+export declare const DRAIN_SECOND_SIGNAL_MIN_GAP_DEFAULT_MS = 250;
+/**
+ * S-753(core 7.33.0 #1121)—— `MODEL_FIRST_BYTE_TIMEOUT_MS`(→ core `BrainTimeoutConfig.firstByteTimeoutMs`,`fetch()` → 响应头
+ * 的等待)的**合法域**,闭区间、整数 ms。解析器(`config.ts`)与目录行(`config-catalog.ts`)共读这一处。
+ *
+ *  · **下界 0**:`0` 在这一座有真含义 —— 该段**不设引擎钟,传输层的响应头 / 响应体钟也关**(TCP + TLS 建连仍归传输层自己的钟;core 7.33.0 起每请求带引擎 dispatcher,把传输层的
+ *    headers / body 钟置 0;在此之前 `0` 只关引擎的钟,传输层 300 s 仍在)。亚秒正值不拒:它是合法的「很快就切」表态
+ *    (failover 拓扑真会这么配;窗上还有 core 按 body 大小加的上传宽限)。
+ *  · **上界 = {@link MAX_TIMER_DELAY_MS}**:core 对超过它的值构造期拒(`config.stall_timeout_invalid`);本仓在 boot 就拒,
+ *    拒句点名 env 键,而不是等到 brain 装配时报一个运维没写过的 config 键名。
+ *  · **没有缺省常量**:缺席 = 不铸键,core 自缺省当家([ref];本仓不复制上游数字 —— S-753 的病根正是本仓自带的 30 000)。
+ */
+export declare const FIRST_BYTE_TIMEOUT_BOUNDS: {
+    readonly minMs: 0;
+    readonly maxMs: 2147483647;
+};
 /**
  * S-220 —— **`resilience` 块缺省的唯一属主**(S-202 的单源从一根扩到整族)。
  *
@@ -81,7 +147,9 @@ export declare const MEMORY_CONSOLIDATION_MIN_INTERVAL_SEC = 300;
  * `satisfies Readonly<Record<keyof ServiceConfigFlat["resilience"], …>>` 双向咬:块上加字段而表里没行
  * ⇒ tsc 红(加字段的人被迫当场回答「它的出厂缺省是多少、归哪个 env」);表里多一行块上没有的键同样红。
  *
- * ⚠️ 语义面**一个数字都没动**:`0 = 关`(三个看门狗)与「熔断默认关」照旧,env 恒赢。
+ * ⚠️ 语义面**一个数字都没动**:「熔断默认关」照旧,env 恒赢。看门狗的 `0` 自 core 7.33.0 起 = 该段**不设引擎钟,传输层的响应头 / 响应体钟
+ * 也关**(TCP + TLS 建连仍归传输层自己的钟;此前 = 只关引擎的钟)。S-753 起本表**不再有首字节那一行**:`MODEL_CONNECT_TIMEOUT_MS`(自带 30 000)退役,替代键
+ * `MODEL_FIRST_BYTE_TIMEOUT_MS` 缺席 = 不铸键(见 {@link ServerDefaultedResilienceKey})。
  * 首 token 那一行的 600_000 由来(S-202 clay 裁 A):自托管后端在长 prefill(大上下文 / 冷缓存 /
  * 排队)下首字合理地要等几分钟,120s 会把一次**正常**的慢启动判成 `[network]` 失败去重试,而重试
  * 再交同一份 prompt 给同一个排队中的后端只会更慢更贵;依赖旧姿态的部署显式写回
@@ -92,10 +160,6 @@ export declare const MEMORY_CONSOLIDATION_MIN_INTERVAL_SEC = 300;
  * 判「字面量」这一类写法为红(下一份镜像出生即红)。
  */
 export declare const RESILIENCE_DEFAULTS: {
-    readonly connectTimeoutMs: {
-        readonly env: "MODEL_CONNECT_TIMEOUT_MS";
-        readonly value: 30000;
-    };
     readonly firstTokenTimeoutMs: {
         readonly env: "MODEL_FIRST_TOKEN_TIMEOUT_MS";
         readonly value: 600000;
@@ -417,16 +481,20 @@ export interface ServiceConfigFlat {
      *  immediately instead of waiting out timeouts). BreakerState is core's in-process Map for now —
      *  cross-replica shared state (TiDB adapter) is a documented follow-up. */
     resilience: {
-        /** Abort fetch if response headers don't arrive within this many ms → retryable [network].
-         *  Default 30s ([ref] fleet audit). 0 = off. */
-        connectTimeoutMs: number;
+        /** S-753(core 7.33.0 #1121)—— `fetch()` → 响应头的等待上限(ms;env `MODEL_FIRST_BYTE_TIMEOUT_MS`,合法域
+         *  {@link FIRST_BYTE_TIMEOUT_BOUNDS})。**缺席 = 不铸键** ⇒ core 自缺省当家(另加 core 按 body 大小给的上传宽限,
+         *  到点后 core 自有一次加宽重试,不吃 `maxRetries`)—— 本仓不复制上游数字([ref])。`0` = 该段不设引擎钟,传输层的响应头 / 响应体钟
+         *  也关(TCP + TLS 建连仍归传输层自己的钟)。取代退役的 `connectTimeoutMs`(名义建连、实际就是计到响应头;本仓自带的 30 000 缺省正是 S-753 的病根)。 */
+        firstByteTimeoutMs?: number;
         /** Cancel an open SSE stream if no content/thinking delta arrives within this many ms.
-         *  Default 120s ([ref] fleet audit — core's idle timer only arms after the first token,
-         *  so this is the only guard for a stream that opens and never emits). 0 = off. */
+         *  Default 600s (S-202; core's idle timer only arms after the first token,
+         *  so this is the only guard for a stream that opens and never emits). 0 = no engine clock on this
+         *  segment and the transport's body clock off too (core ≥7.33.0). */
         firstTokenTimeoutMs: number;
         /** Mid-stream stall watchdog (1.40.1): after output starts, re-armed on every delta; silence for
-         *  this many ms → cancel + retryable [network]. Catches a gateway that hangs AFTER the first token
-         *  (firstTokenTimeoutMs only covers the first). 0 = off. */
+         *  this many ms → cancel + retryable. Catches a gateway that hangs AFTER the first token
+         *  (firstTokenTimeoutMs only covers the first). 0 = no engine clock on this segment and the transport's
+         *  body clock off too (core ≥7.33.0). */
         idleTimeoutMs: number;
         /** Wrap the primary gateway route(s) in a circuit breaker (in-process state, per model+provider). */
         circuitBreaker: boolean;
@@ -1556,6 +1624,15 @@ export interface ServiceConfigFlat {
      *  真源。所以缺席时这台机器跟随 core 的 `main`,运维面由 DEPLOY-PREREQS 的升级段点名(「默认变了」
      *  是升级须知,不是一个可以静默过去的实现细节)。 */
     autoModeClassifierFallback?: "main" | "none";
+    /** 7.102.0 S-757(test [ref] / core #1125)—— **分类器单级判决上限**(`AUTO_MODE_CLASSIFIER_TIMEOUT_MS`,
+     *  部署级数值旋钮,整数 ms,合法域 {@link AUTO_MODE_CLASSIFIER_TIMEOUT_BOUNDS})→ core `RunnerDeps.autoMode.timeoutMs`。
+     *
+     *  为什么要一根旋钮:这一级到点没裁 = 梯子往下走,走完仍没裁 ⇒ 这次门控调用**整条拒**、不出卡。自建慢网关
+     *  (排队 + prefill 以分钟计)在 core 缺省上限内答不出 ⇒ auto 模式在这类部署上等于「工具一律拒」。
+     *
+     *  🔴 **缺席 = 不铸键**(与 {@link autoModeClassifierFallback} 同律):本仓不复制上游缺省数字,core 改缺省之日
+     *  本仓不会成为第二份真源。旋钮**无条件**:不挂任何客户端 / 请求面派生腿。坏值(非十进制整数 / 越界)boot 拒启。 */
+    autoModeClassifierTimeoutMs?: number;
     /** S-111([ref] §4.4)—— CC `settings.crossSessionInbound` 的**部署/组织层**(引擎层形的 `managed` 层,
      *  CC `policySettings` 对位):本部署对入站跨会话消息的治理三态。`accept` 投递 / `hold` 停在收件会话的待审
      *  队列 / `refuse` 整体退出车道。**未设 = 本层不设**(不是 accept):引擎读作「managed 层未表态」,由其余层
@@ -1607,8 +1684,14 @@ export interface ServiceConfigFlat {
      *  instance) to finish before the hard shutdown. During drain, new billable submissions get 503+Retry-After and
      *  /health carries `draining:true`. Default 10min (an interactive turn is minutes, not seconds — a
      *  10s hard-cut would kill long turns); floor 10s. Env: DRAIN_GRACE_MS. SIGINT (Ctrl-C dev
-     *  ergonomics) and a SECOND SIGTERM skip the drain and hard-stop immediately. */
+     *  ergonomics) hard-stops immediately; DURING a drain, a second SIGTERM / SIGINT hard-stops only when it arrives
+     *  at least {@link drainSecondSignalMinGapMs} after the drain began (S-752). */
     drainGraceMs: number;
+    /** S-752(test [ref]):排空期「第二发信号 = 硬停」的最小间隔(ms,锚 = 排空起点)。不足 ⇒ 同一拍的重复投递,一行
+     *  info `drain_duplicate_signal_ignored` 后忽略、排空继续;`0` = 关(7.101.x 行为)。合法域
+     *  {@link DRAIN_SECOND_SIGNAL_MIN_GAP_BOUNDS},缺省 {@link DRAIN_SECOND_SIGNAL_MIN_GAP_DEFAULT_MS};坏值拒启([ref] A 档)。
+     *  部署级旋钮,**无条件**解析。 Env: `DRAIN_SECOND_SIGNAL_MIN_GAP_MS`。 */
+    drainSecondSignalMinGapMs: number;
     /** B3 (shell [ref]②): SIGHUP idle window. SIGHUP means "the process-group owner's terminal went away" — but
      *  under the shared-engine shape (several shell sessions on one config, engine rides the FIRST shell's process
      *  group per the T11 anti-orphan call) other live sessions may still be using this engine, so an unconditional
@@ -1955,13 +2038,20 @@ export interface ServiceConfigFlat {
      *  that worker's roster via `/effective?worker=<name>`. Unset → the global roster (backward compatible).
      *  `credential`(S-651,BREAKING:取代 7.98.0 及以前的 `token: string` 启动快照):凭证来源活对象
      *  (`center-credential.ts`),每条出站请求经它取一次值 —— `SEMA_REGISTRY_TOKEN`(值)或
-     *  `SEMA_REGISTRY_TOKEN_FILE`(每次读文件,轮换 / 换账号不重启)二选一。 */
+     *  `SEMA_REGISTRY_TOKEN_FILE`(每次读文件,轮换 / 换账号不重启)二选一(两键名与判官的属主 = settings-schema
+     *  `CENTER_CREDENTIAL_ENV` / `judgeCenterCredentialDeclaration`,S-742)。 */
     configCenter?: {
         baseUrl: string;
         credential: CenterCredentialSource;
         dryRun: boolean;
         worker?: string;
     };
+    /** S-698(design-325 §2):中心凭证**续签提前量**(ms)—— `SEMA_REGISTRY_TOKEN_FILE` 指向人的登录会话信封
+     *  (`kind:"user-session"`)时,访问令牌离到期 ≤ 本值即由引擎续签并原子改写同一文件(`center-credential-renewer.ts`)。
+     *  缺省 5 min;`0` = 关续签、只读信封(壳负责续);其余必须是整数毫秒且落在 `CENTER_CREDENTIAL_RENEW_LEAD_MIN_MS`(一次续签请求的
+     *  传输上界)与 `CENTER_CREDENTIAL_RENEW_LEAD_MAX_MS`(访问令牌寿命之半)之间,坏值拒启(解析口 `parseCenterCredentialRenewLeadMs`)。
+     *  裸行文件 / `SEMA_REGISTRY_TOKEN` 值形不受它影响(不续签)。`CENTER_CREDENTIAL_RENEW_LEAD_MS`。 */
+    centerCredentialRenewLeadMs: number;
     /** Dual-mode config SOURCE (DUAL-MODE-DESIGN §4): "remote" (sema-registry HTTP) | "local" (.env + config.d
      *  via @sema-agent/settings-schema FileConfigStore) | unset → remote if SEMA_REGISTRY_URL (legacy CONFIG_CENTER_URL now boot-rejects, no dual-read) is set, else pure-env.
      *  Env: CONFIG_PROVIDER. The same resolver/EffectiveConfig either way (can't drift). */
@@ -1975,7 +2065,7 @@ export type ServiceStoreConfig = Pick<ServiceConfigFlat, "sessionBackend" | "ses
 export type ServiceModelPlaneConfig = Pick<ServiceConfigFlat, "gatewayBaseUrl" | "gatewayApiKey" | "gatewayFallbackUrls" | "gatewayMaxRetries" | "anthropic" | "resilience" | "model" | "envModel" | "models" | "modelApiKeyEnv" | "modelApiKeys" | "modelRefusals" | "modelQuotaWeights" | "tiers" | "projects" | "roles" | "atModelAllowlist" | "cascadeLadder" | "degrade">;
 /** 组:approval(审批 / HITL 门)。`directDoorActive` 无 env 解析腿(装配层三域合取的产物),但语义上
  *  就是本组的门状态,故进组;`parseApprovalDomain` 的返回类型相应是 `Omit<…, "directDoorActive">`。 */
-export type ServiceApprovalConfig = Pick<ServiceConfigFlat, "approvalRequire" | "approvalDeny" | "approvalTimeoutSec" | "approvalAutoBudget" | "approvalNeverAuto" | "approvalHmacKeys" | "durableApproval" | "durableApprovalSource" | "streamAskWindowMsSource" | "directApprovalDoor" | "directDoorActive" | "resourceSuspend" | "resourceSuspendTtlSec" | "resourceSuspendTotalTokens" | "resourceSuspendTotalBudgetUsd" | "resourceSuspendMaxSlices" | "askQuestionEnabled" | "questionThrottle" | "toolApprovalEnabled" | "permissionRulesEnabled" | "permissionRulesEnabledExplicit" | "streamAskWindowMarginMs" | "streamApproval" | "unattendedApprovalPolicy" | "mcpElicitation" | "sensitiveWritePatterns" | "writeProtectedPaths" | "manualModeShellGate" | "permissionsDisableAutoMode" | "autoModeClassifierFallback" | "crossSessionInbound" | "crossSessionDialogExpiry">;
+export type ServiceApprovalConfig = Pick<ServiceConfigFlat, "approvalRequire" | "approvalDeny" | "approvalTimeoutSec" | "approvalAutoBudget" | "approvalNeverAuto" | "approvalHmacKeys" | "durableApproval" | "durableApprovalSource" | "streamAskWindowMsSource" | "directApprovalDoor" | "directDoorActive" | "resourceSuspend" | "resourceSuspendTtlSec" | "resourceSuspendTotalTokens" | "resourceSuspendTotalBudgetUsd" | "resourceSuspendMaxSlices" | "askQuestionEnabled" | "questionThrottle" | "toolApprovalEnabled" | "permissionRulesEnabled" | "permissionRulesEnabledExplicit" | "streamAskWindowMarginMs" | "streamApproval" | "unattendedApprovalPolicy" | "mcpElicitation" | "sensitiveWritePatterns" | "writeProtectedPaths" | "manualModeShellGate" | "permissionsDisableAutoMode" | "autoModeClassifierFallback" | "autoModeClassifierTimeoutMs" | "crossSessionInbound" | "crossSessionDialogExpiry">;
 /** 组:memory(记忆面 + TOC 同步腿)。 */
 export type ServiceMemoryConfig = Pick<ServiceConfigFlat, "memoryEngineEnabled" | "memoryEngineDir" | "memoryEngineRemoteLaneAllowed" | "memoryEngineBackend" | "memoryScope" | "memoryPersistenceCapable" | "memorySync" | "memoryEmbedder" | "memoryOrgAdmissionMode" | "memoryDelegationEvidence" | "memoryProvenance" | "memoryCapturePolicy" | "memoryConsolidationDriver" | "memoryOrgDirectoryJson" | "memoryOrgGrantTtlMs" | "memoryOrgUnavailableBackoffMs" | "projectMemoryEnabled" | "syncImportLeaseStaleSec">;
 /** 组:auth(鉴权 / 身份 / 治理棒)。`commandPolicy` 只有 sema-registry 腿(无 env 标量形),故 env 解析
@@ -1988,11 +2078,11 @@ export type ServiceAuthConfig = Pick<ServiceConfigFlat, "authToken" | "authToken
 /** 组:orchestration(编排 + 执行车道 + 沙箱面 + workflow/后台 agent 存留)。 */
 export type ServiceOrchestrationConfig = Pick<ServiceConfigFlat, "remoteExec" | "remoteExecHomeDir" | "requireExecutionLane" | "worktreeIsolation" | "leaderEnabled" | "leaderFanoutEnabled" | "routerEnabled" | "selfOrchestrationEnabled" | "selfOrchestrationModels" | "selfOrchestrationWorkerIsolation" | "forkEnabled" | "experimentalObserverAgents" | "schedulerEnabled" | "schedulerSessionWakeup" | "schedulerSessionLifetime" | "schedulerStorePath" | "planModeEnabled" | "hooksTimeoutMs" | "workflowRunStoreBackend" | "workflowOrphanGraceMs" | "workflowJournalRetentionMs" | "workflowRunRetentionMs" | "usageWindows" | "workflowAgentsReadOnly" | "workflowSizeGuideline" | "backgroundAgentRetentionMs" | "backgroundAgentStaleRunningMs" | "backgroundAgentParkClaimStaleMs" | "delegationEntryCaps" | "rosterRetentionMs" | "leaderRunStaleMs" | "scratchpadSweepTtlMs" | "sandboxPkgSource" | "sessionAutoTitle" | "sessionAutoTitleSource" | "selectEnvironmentTool" | "envFactsEnabled" | "toolDeferLongtail" | "lspEnabled" | "lspHostEnabled" | "lspEnvAllow" | "imageBakes" | "readFace" | "readFaceSource" | "taskWriteFaceEscalation" | "readDenyPatterns" | "readDenyBuiltinTiers" | "readDenyBuiltinExclude">;
 /** 组:limitsHttp(HTTP 面 + 各类上限/配额/回收窗)。 */
-export type ServiceLimitsHttpConfig = Pick<ServiceConfigFlat, "port" | "attachmentOrphanGraceMs" | "workspaceFileMaxBytes" | "attachmentMaxBytes" | "attachmentMimeAllowlist" | "attachmentUnboundTtlMs" | "infraCostRates" | "drainGraceMs" | "sighupIdleGraceMs" | "parentPid" | "engineAutoExit" | "engineLingerMs" | "engineOrphanLingerMs" | "rateLimitPerMin" | "maxTaskCostUsd" | "maxTaskTokens" | "maxPrincipalCostUsd" | "costQuotaWindowSec" | "reapIntervalSec" | "runStaleSec" | "toolResultTtlSec">;
+export type ServiceLimitsHttpConfig = Pick<ServiceConfigFlat, "port" | "attachmentOrphanGraceMs" | "workspaceFileMaxBytes" | "attachmentMaxBytes" | "attachmentMimeAllowlist" | "attachmentUnboundTtlMs" | "infraCostRates" | "drainGraceMs" | "drainSecondSignalMinGapMs" | "sighupIdleGraceMs" | "parentPid" | "engineAutoExit" | "engineLingerMs" | "engineOrphanLingerMs" | "rateLimitPerMin" | "maxTaskCostUsd" | "maxTaskTokens" | "maxPrincipalCostUsd" | "costQuotaWindowSec" | "reapIntervalSec" | "runStaleSec" | "toolResultTtlSec">;
 /** 组:observability(可观测)。 */
 export type ServiceObservabilityConfig = Pick<ServiceConfigFlat, "metricsToken" | "traceToken" | "toolTrace" | "traceThinking" | "logLevel" | "otel">;
 /** 组:integrations(外部集成)。`mcpServers` / `a2aPeers` 由 sema-registry 适配器填(无 env 腿),归本组。 */
-export type ServiceIntegrationsConfig = Pick<ServiceConfigFlat, "pluginsAllowHosts" | "mcpServers" | "a2aPeers" | "a2aServe" | "configBootFetchBudgetMs" | "gitApiBaseUrl" | "gitApiToken" | "gitApiKind" | "defaultScenario" | "skillsDir" | "configCenter" | "configProvider" | "configLocalDir">;
+export type ServiceIntegrationsConfig = Pick<ServiceConfigFlat, "pluginsAllowHosts" | "mcpServers" | "a2aPeers" | "a2aServe" | "configBootFetchBudgetMs" | "gitApiBaseUrl" | "gitApiToken" | "gitApiKind" | "defaultScenario" | "skillsDir" | "centerCredentialRenewLeadMs" | "configCenter" | "configProvider" | "configLocalDir">;
 /** 九个组槽。每组恒在场(`loadConfig` / `attachConfigGroups` 装好才交出配置),故不可选——新代码写
  *  `config.modelPlane.model` 不需要 `?.`(可选组会把 `Model` 污染成 `Model | undefined`)。 */
 export interface ServiceConfigGroups {

package/dist/config-types.js

@@ -1,8 +1,14 @@
+import { DRAIN_GRACE_FLOOR_MS } from "@sema-agent/settings-schema/fleet";
 export const TASK_WRITE_FACE_ESCALATIONS = ["allow", "refuse"];
 export const RETENTION_MODES = ["audit-only", "enforce"];
 export const MEMORY_CONSOLIDATION_MIN_INTERVAL_SEC = 300;
+export const MAX_TIMER_DELAY_MS = 2_147_483_647;
+export const AUTO_MODE_CLASSIFIER_TIMEOUT_BOUNDS = { minMs: 1_000, maxMs: MAX_TIMER_DELAY_MS };
+export { DRAIN_GRACE_FLOOR_MS };
+export const DRAIN_SECOND_SIGNAL_MIN_GAP_BOUNDS = { minMs: 0, maxMs: DRAIN_GRACE_FLOOR_MS };
+export const DRAIN_SECOND_SIGNAL_MIN_GAP_DEFAULT_MS = 250;
+export const FIRST_BYTE_TIMEOUT_BOUNDS = { minMs: 0, maxMs: MAX_TIMER_DELAY_MS };
 export const RESILIENCE_DEFAULTS = {
-    connectTimeoutMs: { env: "MODEL_CONNECT_TIMEOUT_MS", value: 30_000 },
     firstTokenTimeoutMs: { env: "MODEL_FIRST_TOKEN_TIMEOUT_MS", value: 600_000 },
     idleTimeoutMs: { env: "MODEL_IDLE_TIMEOUT_MS", value: 300_000 },
     circuitBreaker: { env: "MODEL_CIRCUIT_BREAKER", value: false },
@@ -12,7 +18,6 @@ export const RESILIENCE_DEFAULTS = {
 export function buildDefaultResilience() {
     const d = RESILIENCE_DEFAULTS;
     return {
-        connectTimeoutMs: d.connectTimeoutMs.value,
         firstTokenTimeoutMs: d.firstTokenTimeoutMs.value,
         idleTimeoutMs: d.idleTimeoutMs.value,
         circuitBreaker: d.circuitBreaker.value,