@sema-agent/settings-schema 14.2.0 → 14.3.0

package/CHANGELOG.md

@@ -10,6 +10,21 @@
 
 (空)
 
+## 14.3.0 — 2026-10-21 — minor:信任阶梯词表做纯常量 `MIN_TRUST_WORDS`(`MinTrust` 由它派生;`trustRank` / `isAtLeast` 闭包零 zod,整函数抄走的消费方只登记一只全局)
+
+> 档位(按发版纪律):**minor** —— 加性:新导出 `MIN_TRUST_WORDS`(包根与 `./safety-merge-spec`);型 `MinTrust`、枚举的词与声明序、`trustRank` 的数值与全部答案、未知词的 RangeError 句逐字节不变。
+
+- **信任阶梯的词表是一只纯常量 `MIN_TRUST_WORDS`;`trustRank` / `isAtLeast` 的闭包只引这一只纯数据,不碰 zod**。此前 `trustRank` 的 `switch` 本身零 zod,
+  唯一的 zod 引用是 `default` 臂 RangeError 句里的 `MinTrust.options.join(", ")` —— 于是按「闭包零 import、只登记全局」整函数抄走判官的消费方抄不了
+  `isAtLeast → trustRank` 这条链(`layerAdmission` 经它判层档);手写一份层表就是第二份层表。现在词表来源是数据:
+  `export const MIN_TRUST_WORDS = ["local", "session", "project", "global", "managed", "task"] as const`(声明序 = 既有枚举序,逐字节不变;声明序不是阶梯,阶梯只经 `trustRank`),
+  `MinTrust = z.enum(MIN_TRUST_WORDS)` 由它派生(与 `AUTONOMY_MODES` → `AutonomyMode` 同形),`trustRank` 的默认臂句读 `MIN_TRUST_WORDS.join(", ")`(句字节不变)。
+  结果:`trustRank` 的自由标识符 = `MIN_TRUST_WORDS` + JS 内建 `RangeError` / `String`,`isAtLeast` 的 = `trustRank`;抄走这一对的消费方把 `MIN_TRUST_WORDS` 登记成全局就够了。
+  不另出第二只函数、不出生成物(一只判官一份源)。
+  三问 —— **谁需要**:按闭包抄判官的消费方(构建期生成器),以及任何抄 `layerAdmission` 链的包;**谁受伤**:无(新导出,既有导出对既有输入的答案逐格不变);**补偿**:无需。
+  钉:`test/trust-ladder-zod-free.test.ts`(① 常量逐位 ≡ `MinTrust.options` 且 = 既有声明序 · ② 两只函数的自由标识符与代码标识符 · ③ 裸 `node:vm` 上下文只注入 `MIN_TRUST_WORDS`,六词 rank / 6×6 真值表 / 未知词的 RangeError 句与包内直接调用逐字节同);
+  `test/safety-merge-spec.test.ts` 的声明序文本钉改读新形(词表字面量恰一处、`MinTrust` 由它派生恰一处)。
+
 ## 14.2.0 — 2026-10-18 — minor:守卫迹象报告序改句 · 关停位任一层 tighten-only(删 managed-only 告知)· 项目层 `.claude/settings*.json` 只经 layerAdmission 读 tighten 方向并点名未读部分 · 控制 / 双向字符剥除集根导出(server / cli 同读,漂移门 ⑨ 退役)
 
 > 档位(按发版纪律):**minor** —— 全部加性:新导出(`CONTROL_AND_BIDI_CHARS` · `stripControlAndBidi` · `hasControlOrBidi` · `layerReadsTightenOnly` · `LAYER_PARTS_UNREAD_CODE` ·

package/README.md

@@ -297,6 +297,10 @@ therefore shows only `zod`. Node built-ins only (`node:crypto`, `node:fs`).
   query sits at the row floor `global`, and the merge is boolStricter (one layer's ON beats every layer's OFF). The table has no managed-only floor
   for them (`permissionMode`'s seam no longer says so): a consumer that stamped one locally retires it onto this row, so its judge and its
   resolver read the same row.
+  The ladder's words are a runtime value, the pure-data table `MIN_TRUST_WORDS` (`["local", "session", "project", "global", "managed", "task"]`): `MinTrust` (the
+  zod enum) is derived from it, and `trustRank` / `isAtLeast` read nothing else — apart from the JavaScript built-ins `RangeError` / `String`, the body of
+  `trustRank` names `MIN_TRUST_WORDS` and `isAtLeast` names `trustRank`, so a consumer that copies the pair whole (a closure with no import, only globals
+  registered) registers that one table instead of writing a ladder of its own. The table's order is the enum's declaration order, not the ladder.
   `MinTrust` gains the `task` word (the runtime task overlay, the loosest floor; appended, declaration order
   otherwise unchanged — the declaration order is not the ladder, `trustRank` is). The published table does not
   use `task`; the widened vocabulary is visible to consumers that hold a `Record<MinTrust, …>` / exhaustive

package/conformance/VERSION

@@ -1 +1 @@
-14.2.0
+14.3.0

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

@@ -60,10 +60,19 @@ export declare const MergeShape: z.ZodEnum<{
     overrideByName: "overrideByName";
 }>;
 export type MergeShape = z.infer<typeof MergeShape>;
+/** The trust-tier VOCABULARY as a RUNTIME VALUE — the ONE source of the ladder's words, in the same form as
+ *  `AUTONOMY_MODES`: {@link MinTrust} (the zod enum) and its type are DERIVED from this table, and {@link trustRank} /
+ *  {@link isAtLeast} read the words from it (their RangeError sentence lists them). Pure data, no zod: a consumer that
+ *  copies the ladder's judge functions whole — a closure with no import, only globals registered — registers this
+ *  table as the one global the closure needs, instead of writing a ladder of its own.
+ *  ⚠️ The DECLARATION ORDER is NOT the rank (it is the 1.1.0 order with `task` appended — kept byte-stable because
+ *  reordering is breaking); never index it as a ladder — use {@link trustRank}. */
+export declare const MIN_TRUST_WORDS: readonly ["local", "session", "project", "global", "managed", "task"];
 /** The trust-tier VOCABULARY a category — or, since 1.1.0, one of its members — names as its admission floor
  *  (the MINIMUM trust a layer/principal must have to set it). The RANK is v2-design §1:29,
  *  `managed 6 > global 5 > project 4 > local 3 > session 2 > task 1`, published as {@link trustRank}; compare with
  *  {@link isAtLeast}. `task` (1.2.0) is the runtime task overlay — the lowest trust, the loosest floor.
+ *  Derived from {@link MIN_TRUST_WORDS} (the words and their declaration order are unchanged).
  *  ⚠️ This enum's DECLARATION ORDER is NOT the rank (it is the 1.1.0 order with `task` appended — kept byte-stable
  *  because reordering is breaking); never index it as a ladder — use {@link trustRank}. */
 export declare const MinTrust: z.ZodEnum<{
@@ -80,11 +89,14 @@ export type MinTrust = z.infer<typeof MinTrust>;
  *  The numbers themselves are contract (a consumer may persist or log them), not merely their order.
  *  Exhaustive over {@link MinTrust}: a word added to the enum without a rank is a COMPILE error here; a word that
  *  is not in the enum at runtime (a JavaScript / deserialized caller) is a loud RangeError — never `undefined` or
- *  `NaN`, which would turn every comparison into a silent `false`. */
+ *  `NaN`, which would turn every comparison into a silent `false`.
+ *  Self-contained: apart from the JavaScript built-ins `RangeError` / `String`, the body names exactly one
+ *  free identifier, the pure-data {@link MIN_TRUST_WORDS} — no zod — so a consumer may copy it whole. */
 export declare function trustRank(layer: MinTrust): number;
 /** `trustRank(layer) ≥ trustRank(minTrust)` — "is a source at `layer` trusted enough to set a key / member whose
  *  floor is `minTrust`?" (1.2.0). The comparison a resolver's admission check is; reflexive (a floor admits its
- *  own tier). Both arguments are validated by {@link trustRank} (unknown word ⇒ RangeError). */
+ *  own tier). Both arguments are validated by {@link trustRank} (unknown word ⇒ RangeError). Its body names one free
+ *  identifier, {@link trustRank} — so the pair copies whole with {@link MIN_TRUST_WORDS} as the only registered global. */
 export declare function isAtLeast(layer: MinTrust, minTrust: MinTrust): boolean;
 /** Which way a MEMBER moves the engine's unattended surface (1.1.0). `loosen` = admits an action without a human
  *  that would otherwise ask/deny — a privilege, so it needs trust; `tighten` = only ever narrows — restricting is

package/dist/safety-merge-spec.js

@@ -53,19 +53,30 @@
 import { z } from "zod";
 /** How values from different layers/principals combine for a category. */
 export const MergeShape = z.enum(["denyFirst", "replace", "runAll", "overrideByName", "concat"]);
+/** The trust-tier VOCABULARY as a RUNTIME VALUE — the ONE source of the ladder's words, in the same form as
+ *  `AUTONOMY_MODES`: {@link MinTrust} (the zod enum) and its type are DERIVED from this table, and {@link trustRank} /
+ *  {@link isAtLeast} read the words from it (their RangeError sentence lists them). Pure data, no zod: a consumer that
+ *  copies the ladder's judge functions whole — a closure with no import, only globals registered — registers this
+ *  table as the one global the closure needs, instead of writing a ladder of its own.
+ *  ⚠️ The DECLARATION ORDER is NOT the rank (it is the 1.1.0 order with `task` appended — kept byte-stable because
+ *  reordering is breaking); never index it as a ladder — use {@link trustRank}. */
+export const MIN_TRUST_WORDS = ["local", "session", "project", "global", "managed", "task"];
 /** The trust-tier VOCABULARY a category — or, since 1.1.0, one of its members — names as its admission floor
  *  (the MINIMUM trust a layer/principal must have to set it). The RANK is v2-design §1:29,
  *  `managed 6 > global 5 > project 4 > local 3 > session 2 > task 1`, published as {@link trustRank}; compare with
  *  {@link isAtLeast}. `task` (1.2.0) is the runtime task overlay — the lowest trust, the loosest floor.
+ *  Derived from {@link MIN_TRUST_WORDS} (the words and their declaration order are unchanged).
  *  ⚠️ This enum's DECLARATION ORDER is NOT the rank (it is the 1.1.0 order with `task` appended — kept byte-stable
  *  because reordering is breaking); never index it as a ladder — use {@link trustRank}. */
-export const MinTrust = z.enum(["local", "session", "project", "global", "managed", "task"]);
+export const MinTrust = z.enum(MIN_TRUST_WORDS);
 /** The trust RANK of a floor / layer word — v2-design §1:29 verbatim (`MANAGED 6 > GLOBAL 5 > PROJECT 4 > LOCAL 3 >
  *  SESSION 2 > TASK 1`), the ONE published ladder every resolver compares against (1.2.0). Higher = more trusted.
  *  The numbers themselves are contract (a consumer may persist or log them), not merely their order.
  *  Exhaustive over {@link MinTrust}: a word added to the enum without a rank is a COMPILE error here; a word that
  *  is not in the enum at runtime (a JavaScript / deserialized caller) is a loud RangeError — never `undefined` or
- *  `NaN`, which would turn every comparison into a silent `false`. */
+ *  `NaN`, which would turn every comparison into a silent `false`.
+ *  Self-contained: apart from the JavaScript built-ins `RangeError` / `String`, the body names exactly one
+ *  free identifier, the pure-data {@link MIN_TRUST_WORDS} — no zod — so a consumer may copy it whole. */
 export function trustRank(layer) {
     switch (layer) {
         case "managed": return 6;
@@ -76,13 +87,14 @@ export function trustRank(layer) {
         case "task": return 1;
         default: {
             const unknown = layer;
-            throw new RangeError(`MinTrust: unknown trust word '${String(unknown)}' (words: ${MinTrust.options.join(", ")})`);
+            throw new RangeError(`MinTrust: unknown trust word '${String(unknown)}' (words: ${MIN_TRUST_WORDS.join(", ")})`);
         }
     }
 }
 /** `trustRank(layer) ≥ trustRank(minTrust)` — "is a source at `layer` trusted enough to set a key / member whose
  *  floor is `minTrust`?" (1.2.0). The comparison a resolver's admission check is; reflexive (a floor admits its
- *  own tier). Both arguments are validated by {@link trustRank} (unknown word ⇒ RangeError). */
+ *  own tier). Both arguments are validated by {@link trustRank} (unknown word ⇒ RangeError). Its body names one free
+ *  identifier, {@link trustRank} — so the pair copies whole with {@link MIN_TRUST_WORDS} as the only registered global. */
 export function isAtLeast(layer, minTrust) {
     return trustRank(layer) >= trustRank(minTrust);
 }

package/docs/API-SURFACE.md

@@ -4,9 +4,9 @@
 > 每次全量重算并逐名比对 —— 加 / 删 / 改形一个导出而不重生成本档 ⇒ 红。导出面的每次变动因此以本档的 diff 出现在评审里。
 > 形:`value` = 运行期拿得到的值;`type` = 只在类型层;`value+type` = 同名的值与类型(zod schema 与它推出的类型)。
 
-子路径 24 条(资产出口 `./package.json` / `./fleet-paths.json` 不是模块,不列),导出名合计 1337 个(同名在多条子路径上各计一次)。
+子路径 24 条(资产出口 `./package.json` / `./fleet-paths.json` 不是模块,不列),导出名合计 1339 个(同名在多条子路径上各计一次)。
 
-## `.`(661)
+## `.`(662)
 
 - `ABSOLUTE_HOST_PATH_MAX` — value
 - `ACCESS_TOKEN_TTL_SECONDS` — value
@@ -236,6 +236,7 @@
 - `MCP_POLICY_RULES` — value
 - `MCP_SERVER_LIST_KEYS` — value
 - `MEMORY_ENGINE_BACKENDS` — value
+- `MIN_TRUST_WORDS` — value
 - `MODEL_ENTRY_REFUSAL_CODES` — value
 - `MODEL_PLANE_REFUSAL_CODES` — value
 - `MODEL_SWITCH_SOURCES` — value
@@ -1037,9 +1038,10 @@
 - `REMOTE_EXEC_DOCUMENT` — value
 - `RemoteExecSpec` — value+type
 
-## `./safety-merge-spec`(18)
+## `./safety-merge-spec`(19)
 
 - `FailMode` — value+type
+- `MIN_TRUST_WORDS` — value
 - `MemberAdmission` — value+type
 - `MemberDirection` — value+type
 - `MergeCategorySpec` — value+type

package/llms-full.txt

@@ -1,6 +1,6 @@
 <!--
 llms-full.txt — 自包含全文 · 消费方(使用者)视角 · @sema-agent/settings-schema
-重写日期: 2026-10-18 | 包版本: 14.2.0
+重写日期: 2026-10-21 | 包版本: 14.3.0
 生成方式: 无生成脚本——按当前树 src/*.ts 导出面 + package.json + README/CHANGELOG 手写事实版。
 证据约定: 每条"它怎么工作"的断言附 (文件: 符号) 坐标,刻意不用行号(行号逐版腐烂;符号名由
 typecheck 与 test/package-surface.test.ts、test/docs-hygiene.test.ts 等常驻门钉住)。无证据推断显式标【推断】。
@@ -346,6 +346,8 @@ entitlement/execution/limits = `none`;`projects` = `salvage`,整域档位仍 `"t
   `memberMinTrust`(禁自铸表)。
 - 信任阶梯(1.2.0):`trustRank`(managed 6 > global 5 > project 4 > local 3 > session 2 > task 1)、
   `isAtLeast`;`MinTrust` 含 `task`(声明序非阶梯,阶梯唯一真源是 `trustRank`)。
+  词表是一只纯常量 `MIN_TRUST_WORDS`(`local, session, project, global, managed, task`;`MinTrust` zod 枚举由它派生):`trustRank` 的闭包自由名 = `MIN_TRUST_WORDS` + JS 内建
+  `RangeError` / `String`,`isAtLeast` 的 = `trustRank` —— 整函数抄走这一对的生成器(client-core)把 `MIN_TRUST_WORDS` 登记成全局即可,不许手写层表 / 词表字面量。
 - 设置源表(src/settings-sources.ts,主 barrel):`SETTINGS_SOURCES`(合并序 user<project<local<flag<policy)、`SETTINGS_SOURCE_CONTRACT`
   (user global / project project 仓库可控 / local project 仓库可控 / flag global / policy managed)、`WORKSPACE_TRUST_STATES`
   (accepted/declined/no_trust_step)、`layerAdmission(source, workspace, category, member?, value?)` → admitted / trust_withheld / below_trust_floor

package/llms.txt

@@ -1,6 +1,6 @@
 <!--
 llms.txt — 消费方(使用者)视角索引 · @sema-agent/settings-schema
-重写日期: 2026-10-18 | 包版本: 14.2.0
+重写日期: 2026-10-21 | 包版本: 14.3.0
 生成方式: 无生成脚本——按当前树的 src/*.ts 导出面 + package.json + README/CHANGELOG 手写事实版;
 每条断言附证据坐标(文件:符号),刻意不用行号(行号随每版腐烂,符号名由 typecheck/test 钉住)。
 刷新触发: package.json 版号变更(test/docs-hygiene.test.ts D 组钉「包版本:」与 package.json 相等、
@@ -95,7 +95,7 @@ llms.txt — 消费方(使用者)视角索引 · @sema-agent/settings-schema
 - **跨会话两键**(1.6.0 新增,`settings.json` 面;6.0.0 词表随 core 7.30.0 改):`crossSessionInbound`(wake/next-turn/hold/refuse + `default`=未设;`accept` 已退役,文件层响亮拒)
   与 `dialogExpiry`(60s/5m/10m/never,缺省 5m);另出两只层读取器,坏值 `ok:false` 不静默折缺省。
   (src/cross-session.ts: `CrossSessionSettings` / `readCrossSessionInbound` / `readDialogExpiry`)
-- **安全合并表** `SAFETY_MERGE_SPEC` + 信任阶梯 `trustRank` / `isAtLeast` + 成员级准入 `memberAdmission`;关停位 `disableBypassPermissionsMode` / `disableAutoMode`
+- **安全合并表** `SAFETY_MERGE_SPEC` + 信任阶梯 `trustRank` / `isAtLeast`(词表来源 = 纯常量 `MIN_TRUST_WORDS`,闭包零 zod)+ 成员级准入 `memberAdmission`;关停位 `disableBypassPermissionsMode` / `disableAutoMode`
   = 类目 `killSwitches`(尾插):任一层可收紧、不放宽 —— 开 = tighten@local(任一设置文件层),关 / 非布尔 / 不带值 = 行地板 global,合并 boolStricter;没有「只许托管层」的地板。
   (src/safety-merge-spec.ts)
 - **设置源表 + 层准入**:`SETTINGS_SOURCES`(合并序)/ `SETTINGS_SOURCE_CONTRACT`(信任档 + 是否仓库可控;本地层与项目层同 `project` 档)/

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/settings-schema",
-  "version": "14.2.0",
+  "version": "14.3.0",
   "description": "Sema settings schema — pure config contract (zod domains + effective-config + roster resolution + ref-integrity + remoteExec) shared by sema-web-admin, 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",