@sema-agent/settings-schema 1.4.0 → 1.5.0

package/CHANGELOG.md

@@ -6,6 +6,33 @@
 > `@sema-agent/registry-core`(更早还曾是 `@sema-ai/registry-core`)。本档 `0.19.0` 以下各节里的
 > 包名是**历史记录**,如实保留不追改。
 
+## 1.5.0 — 2026-09-04 — 扩展命名空间 + 剥键告警截断标志(sema-server S-118 源头修;新键/新导出=minor)
+
+成案:sema-server 修 cli 用户 P1「`/model` 热加载被装饰键整拒」时在下游连打四层补丁(按 kind 放宽→按域→按键路径闭集→
+64 满额特判),每层都被下一轮复审打穿;clay 裁「源头修完再发」+ 抽象优先四原则(sema-comms [6351])。根因在本包:
+「未知键」一个信号被要求同时回答「已知键拼错」(该拒)与「别的写者有意放的扩展键」(该放),按键名扫描分不出意图——
+意图只能在**声明处**说清。
+
+**① `EXTENSION_NAMESPACES`(新导出)+ `isReservedExtensionKey(domain, parentPath, key)`(新导出,分段匹配:父路径 + 键名前缀,不在点号路径上猜——对抗复审 [medium] 采:`semaX-v2`/`semaX.foo` 这类合法前缀成员此前会被后缀文法误报)**:域文档里由别的写者按契约
+放置、本包刻意不认的键。登记的键照旧被 zod strip(行为零变,写者自己回读文件),但 {@link droppedKeys} / `parseDomainLoud`
+**不点名、不计数**。首条登记:`models` 条目级 `sema[A-Z]…`(壳 cli 的自留字段族,cli [5273] design/cli-190c 实键清单
+六键 `semaChannel`/`semaLabel`/`semaProbe`/`semaProbeAt`/`semaEffortDefault`/`semaVision`,全条目级、顶层零装饰键 ⇒ 顶层
+`sema*` 仍是未知键)。消费方从此一条规则:**未登记的未知键 = 拼错 = 错误,零特例**。新写者/新层级加行 = minor。
+
+**② `unknown-keys-dropped` / `unknown-keys-carried` 告警加可选 `truncatedFrom?: number`**(与 `hosts-grandfathered.truncatedFrom`
+同形):`keys` 仍有界(`DROP_SCAN_MAX_KEYS`=64),超界时带真实总数——扫描本就 O(文档键数),上限只界告警载荷不界扫描。
+把有界列表当穷举决策输入正是 S-118 第四层被打穿的形(13 模型 × 6 装饰键填满 64 后拼错键不在列表里);①之后扩展键不计数,
+②让剩下的截断在消费方看得见。
+
+钉 `test/extension-namespace-1.5.test.ts` 七格(六装饰键零告警且仍 strip / 顶层 sema* 照报 / 前缀契约即前缀(`semaGPT_5`/`semaX-v2`/`semaX.foo` 成员,`semax`/`Sema` 不是)/ S-118 真案
+78 扩展键 + 1 拼错恰点名 1 / 表门:锚定正则+真实域名 / dropped 与 carried 各自 64+truncatedFrom)。`droppedKeys` /
+`carriedUnknownKeys` 导出签名不变(仍返回有界 `string[]`,是同一次扫描的投影)。消费方:sema-server(提货后删下游四层
+特判与 `domainNotices` 机制)、cli(不消费告警面,零改;实键面若变请改表)。
+
+## 1.4.1 — 2026-09-02 — 文案 patch(cli [6037]/[6038] 请件)
+
+- 复审出处注词族全清:src 12 处+d.ts 同族(`codex …`→`对抗复审 …`,语义零损)——1.4.0 件⑦「52→1」的三族 regex 未含此词族=漏计根因;npm 包注释=对外文案面,壳 bundle hygiene 禁表命中即发布腿红。
+
 ## 1.4.0 — 2026-09-02 — settings-schema 批八件(DEBTS-server S-59;新键=minor 按本批成文政策)
 
 七件 = 两把新可选键(①⑥,additive)+ 三件文案/论证面(②③④)+ 一件文档重写(⑤)+ 一件发布物中性化(⑦)。

package/dist/config-fns.d.ts

@@ -175,11 +175,15 @@ export type EffectiveReadWarning = {
 }
 /** 域文档里那些**不属于该域 schema** 的键:行为照旧(zod 非 strict = 剥掉,前向兼容不动),但点名
  *  说出来。`keys` = 点号路径(`infraCostRates.toolCalMicroUsd` / `commandPolicy.0.typo`),见
- *  {@link droppedKeys} 的扫描边界。 */
+ *  {@link droppedKeys} 的扫描边界。**1.5.0**:①{@link EXTENSION_NAMESPACES} 登记的扩展键(别的写者按契约
+ *  放在文档里、本包刻意不认的键,如壳写在 models 条目上的 `sema*`)**不算未知键**——既不点名也不计数;
+ *  ②`keys` 有界(`DROP_SCAN_MAX_KEYS`),超界时带 `truncatedFrom`(= 真实未知键总数,与 `hosts-grandfathered`
+ *  同形),消费方据此知道列表**不是穷举**——把有界诊断当穷举决策输入,是服务端消费方在配置门上三次被复审打穿的根因。 */
  | {
     domain: DomainName;
     kind: "unknown-keys-dropped";
     keys: string[];
+    truncatedFrom?: number;
 }
 /** open-world 域(`.passthrough()`)里**已送达但本包不认识**的键:值原样到了消费方手里(承运),
  *  但拼错的键名同样该有人说 —— 认不认归持有键表的消费方,`keys` 是点号路径。 */
@@ -187,6 +191,7 @@ export type EffectiveReadWarning = {
     domain: DomainName;
     kind: "unknown-keys-carried";
     keys: string[];
+    truncatedFrom?: number;
 }
 /** `config.d/` 里存在、但本地读取集**永远不会读**的文件(名字不是域,或是域但不便携)。 */
  | {
@@ -195,6 +200,31 @@ export type EffectiveReadWarning = {
     domain?: DomainName;
     why: "not-a-domain" | "non-portable-domain";
 };
+/**
+ * **扩展命名空间**(1.5.0):域文档里**由别的写者按契约放置、本包刻意不认**的键。它们照旧被 zod strip
+ * (本包与引擎消费方看不见——这正是契约:壳自己回读文件取值),但 {@link droppedKeys} **不点名、不计数**。
+ * 没有这张表,「未知键」一个信号要同时回答「已知键拼错了」(该拒)与「别的写者有意放的扩展键」(该放)
+ * 两个问题——按键名扫描永远分不出意图,消费方只能在下游猜(服务端消费方的真案:按 kind→按域→按键路径闭集→
+ * 满额特判,四层各被下一轮复审打穿)。意图只能在**声明处**说清:写者在这里登记自己的命名空间,之后
+ * 所有未被登记的未知键都是拼错,消费方一条规则:未知键 = 错误,零特例。
+ *
+ * 登记形(分段):`at` = 父路径正则(点号形含尾点,顶层 `""`,首尾锚定,test 有门)+ `key` = 键名前缀正则;`owner` = 写者;
+ * `since` = 契约出处。新写者/新层级来这里加行,并在 CHANGELOG 点名——这是 additive(minor)。
+ *
+ *  · `models` 条目级 `sema[A-Z]…`:壳(cli)的自留字段族(`semaChannel`/`semaLabel`/`semaProbe`/`semaProbeAt`/
+ *    `semaEffortDefault`/`semaVision`,壳侧 models.json 实键清单 design/cli-190c:「`sema` 前缀是壳侧自留字段的既定
+ *    约定」,**全条目级、顶层零装饰键**)。顶层 `sema*` 不在此列 ⇒ 仍是未知键(拼错或越界)。
+ */
+export declare const EXTENSION_NAMESPACES: Partial<Record<DomainName, ReadonlyArray<{
+    readonly at: RegExp;
+    readonly key: RegExp;
+    readonly owner: string;
+    readonly since: string;
+}>>>;
+/** 该键是否落在 {@link EXTENSION_NAMESPACES} 登记的扩展命名空间里(⇒ 不是未知键)。**分段匹配**:`at` 对父路径(点号形,含尾点;
+ *  顶层 = `""`),`key` 对键名本身——不在拼好的点号路径上猜(键名里可以含 `.`,`semaX.foo` 是一个键不是两层),前缀契约就是
+ *  前缀契约(`semaGPT_5` / `semaX-v2` 都是成员,后缀不设未声明的文法)。 */
+export declare function isReservedExtensionKey(domain: DomainName, parentPath: string, key: string): boolean;
 /**
  * 一份域文档里被域 schema **丢掉的键**(zod 对象默认 `"strip"`),点号路径形。
  *
@@ -203,7 +233,7 @@ export type EffectiveReadWarning = {
  * (新 center 的新键不该炸老消费方),所以修法不是收紧成 `.strict()`,而是让它**响亮**:
  * {@link buildEffective} 每域解析成功后调用本函数,非空即发 `"unknown-keys-dropped"` 警告。
  *
- * **嵌套也扫**(codex 复审 F2 真 finding):`{infraCostRates:{toolCalMicroUsd:10}}` 这种**拼错的嵌套
+ * **嵌套也扫**(对抗复审 复审 F2 真 finding):`{infraCostRates:{toolCalMicroUsd:10}}` 这种**拼错的嵌套
  * 键**在顶层看不见(`infraCostRates` 键还在),只看顶层等于对计费面的错键完全失明。故按 raw↔parsed
  * 的键集逐层对比(对象逐键、数组同长时逐下标),不依赖任何 zod 内省。
  *
@@ -227,7 +257,7 @@ export declare function carriedUnknownKeys(domain: DomainName, parsed: unknown):
 /**
  * 一域的 parse + **静默剥键/静默承运两条告警**(0.19.0)。`buildEffective` 与 `FileConfigStore.getDomain`
  * 共用这一个判据 —— 此前只有 effective 那条路径有门,而 `getDomain` 是 `exportBundle` 的读法
- * (codex 复审 round2 F3:导出一份被剥了键的域再导入 = 持久的配置丢失,而且全程无声)。
+ * (对抗复审 复审 round2 F3:导出一份被剥了键的域再导入 = 持久的配置丢失,而且全程无声)。
  */
 export declare function parseDomainLoud<K extends DomainName>(domain: K, raw: unknown, onWarning?: (w: EffectiveReadWarning) => void): DomainConfig[K];
 /** Per-domain READ-corruption policy (0.8.1) — what buildEffective does when a stored domain no longer parses.

package/dist/config-fns.js

@@ -140,8 +140,33 @@ export function legacyGovernanceFromRuntime(rawRuntime) {
 }
 /** 扫描深度上限(嵌套再深的配置文档不存在;有上限才不会被恶意深链拖住)。 */
 const DROP_SCAN_MAX_DEPTH = 8;
-/** 一条警告最多点名多少个键(告警载荷有界;截断即说明,见 {@link droppedKeys})。 */
+/** 一条警告最多点名多少个键(告警载荷有界;超界时警告带 `truncatedFrom` = 真实总数,见 {@link droppedKeys})。 */
 const DROP_SCAN_MAX_KEYS = 64;
+/**
+ * **扩展命名空间**(1.5.0):域文档里**由别的写者按契约放置、本包刻意不认**的键。它们照旧被 zod strip
+ * (本包与引擎消费方看不见——这正是契约:壳自己回读文件取值),但 {@link droppedKeys} **不点名、不计数**。
+ * 没有这张表,「未知键」一个信号要同时回答「已知键拼错了」(该拒)与「别的写者有意放的扩展键」(该放)
+ * 两个问题——按键名扫描永远分不出意图,消费方只能在下游猜(服务端消费方的真案:按 kind→按域→按键路径闭集→
+ * 满额特判,四层各被下一轮复审打穿)。意图只能在**声明处**说清:写者在这里登记自己的命名空间,之后
+ * 所有未被登记的未知键都是拼错,消费方一条规则:未知键 = 错误,零特例。
+ *
+ * 登记形(分段):`at` = 父路径正则(点号形含尾点,顶层 `""`,首尾锚定,test 有门)+ `key` = 键名前缀正则;`owner` = 写者;
+ * `since` = 契约出处。新写者/新层级来这里加行,并在 CHANGELOG 点名——这是 additive(minor)。
+ *
+ *  · `models` 条目级 `sema[A-Z]…`:壳(cli)的自留字段族(`semaChannel`/`semaLabel`/`semaProbe`/`semaProbeAt`/
+ *    `semaEffortDefault`/`semaVision`,壳侧 models.json 实键清单 design/cli-190c:「`sema` 前缀是壳侧自留字段的既定
+ *    约定」,**全条目级、顶层零装饰键**)。顶层 `sema*` 不在此列 ⇒ 仍是未知键(拼错或越界)。
+ */
+export const EXTENSION_NAMESPACES = {
+    models: [{ at: /^models\.\d+\.$/, key: /^sema[A-Z]/, owner: "cli", since: "shell key census design/cli-190c (2026-08-26)" }],
+};
+/** 该键是否落在 {@link EXTENSION_NAMESPACES} 登记的扩展命名空间里(⇒ 不是未知键)。**分段匹配**:`at` 对父路径(点号形,含尾点;
+ *  顶层 = `""`),`key` 对键名本身——不在拼好的点号路径上猜(键名里可以含 `.`,`semaX.foo` 是一个键不是两层),前缀契约就是
+ *  前缀契约(`semaGPT_5` / `semaX-v2` 都是成员,后缀不设未声明的文法)。 */
+export function isReservedExtensionKey(domain, parentPath, key) {
+    const rules = EXTENSION_NAMESPACES[domain];
+    return rules !== undefined && rules.some((r) => r.at.test(parentPath) && r.key.test(key));
+}
 /** 纯 JSON 对象(不是数组、不是类实例/带原型的东西)——只对这种做键集对比,别的形状交给 parse 判。 */
 function isPlainJsonObject(v) {
     if (v === null || typeof v !== "object" || Array.isArray(v))
@@ -149,30 +174,42 @@ function isPlainJsonObject(v) {
     const proto = Object.getPrototypeOf(v);
     return proto === Object.prototype || proto === null;
 }
-function collectDropped(raw, parsed, prefix, depth, spared, out) {
-    if (depth > DROP_SCAN_MAX_DEPTH || out.length >= DROP_SCAN_MAX_KEYS)
+function collectDropped(domain, raw, parsed, prefix, depth, spared, acc) {
+    if (depth > DROP_SCAN_MAX_DEPTH)
         return;
     if (Array.isArray(raw) && Array.isArray(parsed)) {
         // 长度不同 = 整条元素被丢/被裁(hosts 的 grandfather clamp 有自己的警告),不在本判据内,别造重复噪声。
         if (raw.length !== parsed.length)
             return;
         for (let i = 0; i < raw.length; i++)
-            collectDropped(raw[i], parsed[i], `${prefix}${i}.`, depth + 1, [], out);
+            collectDropped(domain, raw[i], parsed[i], `${prefix}${i}.`, depth + 1, [], acc);
         return;
     }
     if (!isPlainJsonObject(raw) || !isPlainJsonObject(parsed))
         return;
     for (const k of Object.keys(raw)) {
-        if (out.length >= DROP_SCAN_MAX_KEYS)
-            return;
         if (depth === 0 && spared.includes(k))
             continue;
         if (!Object.prototype.hasOwnProperty.call(parsed, k)) {
-            out.push(prefix + k);
+            if (isReservedExtensionKey(domain, prefix, k))
+                continue; // 扩展命名空间:按契约放的键,不是未知键
+            acc.total += 1;
+            if (acc.keys.length < DROP_SCAN_MAX_KEYS)
+                acc.keys.push(prefix + k);
             continue;
         }
-        collectDropped(raw[k], parsed[k], `${prefix}${k}.`, depth + 1, spared, out);
+        collectDropped(domain, raw[k], parsed[k], `${prefix}${k}.`, depth + 1, spared, acc);
+    }
+}
+function scanDropped(domain, raw, parsed) {
+    const acc = { keys: [], total: 0 };
+    try {
+        collectDropped(domain, raw, parsed, "", 0, domain === "runtime" ? GOVERNANCE_MIRROR_KEYS : [], acc);
+    }
+    catch {
+        return { keys: [], total: 0 }; // 反射/访问器抛错:告警是尽力而为的审计线,绝不能把解析拖下水,更不能回显其错误文案
     }
+    return acc;
 }
 /**
  * 一份域文档里被域 schema **丢掉的键**(zod 对象默认 `"strip"`),点号路径形。
@@ -182,7 +219,7 @@ function collectDropped(raw, parsed, prefix, depth, spared, out) {
  * (新 center 的新键不该炸老消费方),所以修法不是收紧成 `.strict()`,而是让它**响亮**:
  * {@link buildEffective} 每域解析成功后调用本函数,非空即发 `"unknown-keys-dropped"` 警告。
  *
- * **嵌套也扫**(codex 复审 F2 真 finding):`{infraCostRates:{toolCalMicroUsd:10}}` 这种**拼错的嵌套
+ * **嵌套也扫**(对抗复审 复审 F2 真 finding):`{infraCostRates:{toolCalMicroUsd:10}}` 这种**拼错的嵌套
  * 键**在顶层看不见(`infraCostRates` 键还在),只看顶层等于对计费面的错键完全失明。故按 raw↔parsed
  * 的键集逐层对比(对象逐键、数组同长时逐下标),不依赖任何 zod 内省。
  *
@@ -195,20 +232,13 @@ function collectDropped(raw, parsed, prefix, depth, spared, out) {
  * 让其错误外泄(错误文案可能带 secret,与 parseDomain 的 R13 同纪律),扫描失败即当作"没看见",不影响解析。
  */
 export function droppedKeys(domain, raw, parsed) {
-    const out = [];
-    try {
-        collectDropped(raw, parsed, "", 0, domain === "runtime" ? GOVERNANCE_MIRROR_KEYS : [], out);
-    }
-    catch {
-        return []; // 反射/访问器抛错:告警是尽力而为的审计线,绝不能把解析拖下水,更不能回显其错误文案
-    }
-    return out;
+    return scanDropped(domain, raw, parsed).keys;
 }
 /**
  * open-world 域(`.passthrough()`)的**已知键表**:路径 → 该层已知键(`""` = 顶层)。键集从 schema 的
  * `shape` **单源派生**(手抄一份必然漂),路径表本身是显式的——嵌套只在真有 open-world 子对象的地方登记。
  *
- * 为什么需要它(codex 复审 round2 F2):承运解决了「值到不了」,但没解决「键名拼错了没人说」——
+ * 为什么需要它(对抗复审 复审 round2 F2):承运解决了「值到不了」,但没解决「键名拼错了没人说」——
  * `toolResultsTtlSec`(多一个 s)会完好穿过本包,而消费方只遍历自己的键表,于是那条天花板悄悄没生效。
  * 承运 + 点名两件一起做:值照送(消费方有权认新键),名照报(拼错的有人说)。
  *
@@ -226,38 +256,44 @@ const OPEN_WORLD_KNOWN_KEYS = {
  * 子树)不再下探,那本就是消费方自定义的内容,逐层猜没有意义。
  */
 export function carriedUnknownKeys(domain, parsed) {
+    return scanCarried(domain, parsed).keys;
+}
+function scanCarried(domain, parsed) {
     const table = OPEN_WORLD_KNOWN_KEYS[domain];
+    const acc = { keys: [], total: 0 };
     if (!table || !isPlainJsonObject(parsed))
-        return [];
-    const out = [];
+        return acc;
     for (const [path, known] of Object.entries(table)) {
         const node = path === "" ? parsed : parsed[path];
         if (!isPlainJsonObject(node))
             continue;
         const prefix = path === "" ? "" : `${path}.`;
         for (const k of Object.keys(node)) {
-            if (out.length >= DROP_SCAN_MAX_KEYS)
-                return out;
-            if (!known.includes(k))
-                out.push(prefix + k);
+            if (known.includes(k))
+                continue;
+            if (isReservedExtensionKey(domain, prefix, k))
+                continue;
+            acc.total += 1;
+            if (acc.keys.length < DROP_SCAN_MAX_KEYS)
+                acc.keys.push(prefix + k);
         }
     }
-    return out;
+    return acc;
 }
 /**
  * 一域的 parse + **静默剥键/静默承运两条告警**(0.19.0)。`buildEffective` 与 `FileConfigStore.getDomain`
  * 共用这一个判据 —— 此前只有 effective 那条路径有门,而 `getDomain` 是 `exportBundle` 的读法
- * (codex 复审 round2 F3:导出一份被剥了键的域再导入 = 持久的配置丢失,而且全程无声)。
+ * (对抗复审 复审 round2 F3:导出一份被剥了键的域再导入 = 持久的配置丢失,而且全程无声)。
  */
 export function parseDomainLoud(domain, raw, onWarning) {
     const parsed = parseDomain(domain, raw);
     if (onWarning) {
-        const dropped = droppedKeys(domain, raw, parsed);
-        if (dropped.length > 0)
-            onWarning({ domain, kind: "unknown-keys-dropped", keys: dropped });
-        const carried = carriedUnknownKeys(domain, parsed);
-        if (carried.length > 0)
-            onWarning({ domain, kind: "unknown-keys-carried", keys: carried });
+        const dropped = scanDropped(domain, raw, parsed);
+        if (dropped.keys.length > 0)
+            onWarning({ domain, kind: "unknown-keys-dropped", keys: dropped.keys, ...(dropped.total > dropped.keys.length ? { truncatedFrom: dropped.total } : {}) });
+        const carried = scanCarried(domain, parsed);
+        if (carried.keys.length > 0)
+            onWarning({ domain, kind: "unknown-keys-carried", keys: carried.keys, ...(carried.total > carried.keys.length ? { truncatedFrom: carried.total } : {}) });
     }
     return parsed;
 }

package/dist/file-store.d.ts

@@ -5,7 +5,7 @@ import { type DomainConfig, type DomainName, type EffectiveConfig } from "./type
  *  **default**域集 of the bundle helpers (`exportBundle`/`readBundle`). 每个被排除的域必须在
  *  {@link NON_PORTABLE_DOMAIN_REASONS} 里有一条成文理由(禁裸排除,#282 件5 附带裁定)。
  *
- *  ⚠️ 口径诚实(codex 复审 round1 F4):这是**默认集与本地读取集,不是 API 级硬边界** —— `exportBundle`
+ *  ⚠️ 口径诚实(对抗复审 复审 round1 F4):这是**默认集与本地读取集,不是 API 级硬边界** —— `exportBundle`
  *  / `readBundle` 的 `domains` 参数可显式传任意 `DomainName`(bundle.ts 不拒非便携域)。把非便携域搬进
  *  bundle 的那条口子归调用方纪律(以及各自域的导出面),不是本常量能挡住的;要不要把 bundle API 收窄到
  *  `PortableDomain` 是一个独立的行为面裁定(#282 未决项,需三问),本批不擅自改。
@@ -22,7 +22,7 @@ export type PortableDomain = (typeof PORTABLE_DOMAINS)[number];
  *
  * `satisfies Record<Exclude<DomainName, PortableDomain>, string>` 让键集在**编译期**双向咬死:新开一个
  * 域却不放进 PORTABLE_DOMAINS ⇒ 这里缺行 ⇒ 编译错;把某域改成便携却忘了删行 ⇒ 多余键 ⇒ 编译错。
- * (此前是「理由写在注释里」,机器只能做子串匹配——域名出现在文件任何角落都算数,等于没门;codex
+ * (此前是「理由写在注释里」,机器只能做子串匹配——域名出现在文件任何角落都算数,等于没门;对抗复审
  * 复审 round1 F3。)理由要写**为什么它不该被单机/跨部署搬运**,带出处。
  */
 export declare const NON_PORTABLE_DOMAIN_REASONS: {

package/dist/file-store.js

@@ -7,7 +7,7 @@
  * LOCAL FILE LAYOUT (the TOC owns the root, e.g. `~/.ai-agent/` or a project-local `.ai-agent/`):
  *   <root>/config.d/<domain>.json   for every domain in {@link PORTABLE_DOMAINS} — that constant is the
  *                    AUTHORITY; do NOT hand-copy the list here (the hand-written enumeration that used to sit
- *                    on this line silently missed `prompts` for three releases — codex 复审 round2 F5).
+ *                    on this line silently missed `prompts` for three releases — 对抗复审 复审 round2 F5).
  *   <root>/.env        secret VALUES (KEY=value) — the ONLY file holding secrets; gitignored, never read here.
  *
  * Rules:
@@ -30,7 +30,7 @@ import { isDomainName } from "./types.js";
  *  **default**域集 of the bundle helpers (`exportBundle`/`readBundle`). 每个被排除的域必须在
  *  {@link NON_PORTABLE_DOMAIN_REASONS} 里有一条成文理由(禁裸排除,#282 件5 附带裁定)。
  *
- *  ⚠️ 口径诚实(codex 复审 round1 F4):这是**默认集与本地读取集,不是 API 级硬边界** —— `exportBundle`
+ *  ⚠️ 口径诚实(对抗复审 复审 round1 F4):这是**默认集与本地读取集,不是 API 级硬边界** —— `exportBundle`
  *  / `readBundle` 的 `domains` 参数可显式传任意 `DomainName`(bundle.ts 不拒非便携域)。把非便携域搬进
  *  bundle 的那条口子归调用方纪律(以及各自域的导出面),不是本常量能挡住的;要不要把 bundle API 收窄到
  *  `PortableDomain` 是一个独立的行为面裁定(#282 未决项,需三问),本批不擅自改。
@@ -49,7 +49,7 @@ const NON_DOMAIN_CONFIG_FILES = new Set(["remote-exec.json"]);
  *
  * `satisfies Record<Exclude<DomainName, PortableDomain>, string>` 让键集在**编译期**双向咬死:新开一个
  * 域却不放进 PORTABLE_DOMAINS ⇒ 这里缺行 ⇒ 编译错;把某域改成便携却忘了删行 ⇒ 多余键 ⇒ 编译错。
- * (此前是「理由写在注释里」,机器只能做子串匹配——域名出现在文件任何角落都算数,等于没门;codex
+ * (此前是「理由写在注释里」,机器只能做子串匹配——域名出现在文件任何角落都算数,等于没门;对抗复审
  * 复审 round1 F3。)理由要写**为什么它不该被单机/跨部署搬运**,带出处。
  */
 export const NON_PORTABLE_DOMAIN_REASONS = {
@@ -185,7 +185,7 @@ export class FileConfigStore {
         const raw = await this.#readDomainRaw(domain);
         if (raw === undefined)
             return undefined; // missing/empty file → domain absent (not schema defaults)
-        // 0.19.0(codex 复审 round2 F3):与 buildEffective **同一条** parse-and-warn 判据。此前本方法直接
+        // 0.19.0(对抗复审 复审 round2 F3):与 buildEffective **同一条** parse-and-warn 判据。此前本方法直接
         // parseDomain,于是 `exportBundle`(它就是逐域走 getDomain 读的)会把一份携带未知键的域**静默剥**
         // 成一份"干净"的 bundle —— 再 import 回去就是一次持久的配置丢失,全程零告警。
         return parseDomainLoud(domain, raw, this.opts.onWarning);

package/dist/safety-merge-spec.d.ts

@@ -85,7 +85,7 @@ export type MemberDirection = z.infer<typeof MemberDirection>;
 /** One member's admission row. `minTrust` ABSENT ⇒ the category's `minTrust` applies: a row can refine the floor
  *  only by SAYING so; omission never lowers it (fail-closed by construction).
  *
- *  `boolPole` (S-59 件八, codex r3 [high]) — VALUE-DIRECTIONAL admission for a boolean member whose two poles
+ *  `boolPole` (S-59 件八, 对抗复审 r3 [high]) — VALUE-DIRECTIONAL admission for a boolean member whose two poles
  *  point opposite ways (`enabled:true` narrows the sandbox, `enabled:false` opens it): a write EQUAL to
  *  `boolPole.strict` (strict equality, never truthiness — a string "true" is not the pole) is the tightening
  *  write and is admitted at `boolPole.minTrust`; ANY other write — the loose pole, a non-boolean, or a
@@ -591,7 +591,7 @@ export type SafetyMergeCategory = keyof typeof SAFETY_MERGE_SPEC;
  *  DISTRIBUTIVE over `C` on purpose: a resolver holds a WIDENED `SafetyMergeCategory` (out of its key→category
  *  map), and a non-distributive form would index the whole union at once, fail the `members` check on the
  *  whole-key categories and collapse to `never` — typing `membersOf(category)` as `readonly never[]` at exactly
- *  the seam these helpers exist for (codex R2-F1). */
+ *  the seam these helpers exist for (对抗复审 R2-F1). */
 export type SafetyMergeMember<C extends SafetyMergeCategory> = C extends SafetyMergeCategory ? (typeof SAFETY_MERGE_SPEC)[C] extends {
     readonly members: infer M;
 } ? Extract<keyof M, string> : never : never;
@@ -604,7 +604,7 @@ export declare function membersOf<C extends SafetyMergeCategory>(category: C): r
  * Fail-CLOSED and loud on both misuse arms — a category without `members` has no member to name, and a member
  * outside the declared set is a caller bug, not "use the category floor" (that silent arm is exactly what would
  * let a typo admit a bucket under the wrong rule).
- * Value-aware (codex r3): pass the CANDIDATE VALUE being written for a value-directional (`boolPole`) member —
+ * Value-aware (对抗复审 r3): pass the CANDIDATE VALUE being written for a value-directional (`boolPole`) member —
  * the strict pole resolves to `boolPole.minTrust`, everything else (loose pole / non-boolean / no value) to the
  * row floor. Rows without `boolPole` ignore the value entirely.
  * @param categoryLabel only decorates the error message (the spec value carries no name of its own).

package/dist/safety-merge-spec.js

@@ -97,7 +97,7 @@ export const MemberDirection = z.enum(["loosen", "tighten"]);
 /** One member's admission row. `minTrust` ABSENT ⇒ the category's `minTrust` applies: a row can refine the floor
  *  only by SAYING so; omission never lowers it (fail-closed by construction).
  *
- *  `boolPole` (S-59 件八, codex r3 [high]) — VALUE-DIRECTIONAL admission for a boolean member whose two poles
+ *  `boolPole` (S-59 件八, 对抗复审 r3 [high]) — VALUE-DIRECTIONAL admission for a boolean member whose two poles
  *  point opposite ways (`enabled:true` narrows the sandbox, `enabled:false` opens it): a write EQUAL to
  *  `boolPole.strict` (strict equality, never truthiness — a string "true" is not the pole) is the tightening
  *  write and is admitted at `boolPole.minTrust`; ANY other write — the loose pole, a non-boolean, or a
@@ -183,7 +183,7 @@ export const SAFETY_MERGE_SPEC = {
     //   · network.allowAllUnixSockets / network.allowLocalBinding `false` = the opening stays shut ⇒ tighten;
     //   · filesystem.allowManagedReadPathsOnly `true` ⇒ tighten (same managed-only consumer caveat);
     //   · filesystem.denyWrite / filesystem.denyRead — deny arrays only ever narrow ⇒ tighten in every write.
-    // A boolean member's admission is VALUE-directional and the pole is MODELED (codex r3 [high]): each boolean
+    // A boolean member's admission is VALUE-directional and the pole is MODELED (对抗复审 r3 [high]): each boolean
     // row carries `boolPole {strict, minTrust:"local"}` and keeps its ROW floor at the loosen floor "global" —
     // value-aware consumers admit the strict pole at "local"; pole-blind consumers (whose schema strips boolPole)
     // read tighten@global and withhold BOTH poles from low-trust layers (fail-closed: convenience lost, never a
@@ -251,7 +251,7 @@ export function membersOf(category) {
  * Fail-CLOSED and loud on both misuse arms — a category without `members` has no member to name, and a member
  * outside the declared set is a caller bug, not "use the category floor" (that silent arm is exactly what would
  * let a typo admit a bucket under the wrong rule).
- * Value-aware (codex r3): pass the CANDIDATE VALUE being written for a value-directional (`boolPole`) member —
+ * Value-aware (对抗复审 r3): pass the CANDIDATE VALUE being written for a value-directional (`boolPole`) member —
  * the strict pole resolves to `boolPole.minTrust`, everything else (loose pole / non-boolean / no value) to the
  * row floor. Rows without `boolPole` ignore the value entirely.
  * @param categoryLabel only decorates the error message (the spec value carries no name of its own).

package/dist/types.js

@@ -746,7 +746,7 @@ export const LimitsConfig = z.object({
     //    在上一份好配置);未知键原样承运,由消费方(键表在它手里)决定认或不认。
     //  · 附带收益:老编辑器(TOC)写回新 center 的 limits 文档时不会把自己不认识的键写没了(strip 语义下
     //    writeDomainFile 会真的丢键)。
-    //  · **承运 ≠ 沉默**(codex 复审 round2 F2):未知成员会被 `"unknown-keys-carried"` 警告逐个点名
+    //  · **承运 ≠ 沉默**(对抗复审 复审 round2 F2):未知成员会被 `"unknown-keys-carried"` 警告逐个点名
     //    (config-fns 的已知键表由本 schema 的 shape 单源派生)——拼错的键名于是有人说,而值仍然到得了
     //    消费方手里,两头都不吃亏。
     //  · 失效条件(如实):若限额面将来收敛为「契约先行、消费方只读已声明键」,本论证不再成立;届时改回

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/settings-schema",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "Sema settings schema — pure config contract (zod domains + effective-config + roster resolution + ref-integrity + remoteExec) shared by sema-registry, sema-server, and the TOC desktop/CLI. One source of truth. (Renamed at 1.0.0 from @sema-agent/registry-core — name and docs only, no behavior change; note the range moves 0.19.0 -> 1.0.0, so a dependency must become ^1.0.0. The old names @sema-agent/registry-core <=0.19.0 and @sema-ai/registry-core remain published, frozen, for migration.)",
   "type": "module",
   "license": "BUSL-1.1",