@sema-agent/settings-schema 3.0.0 → 3.0.1

package/CHANGELOG.md

@@ -6,6 +6,29 @@
 > `@sema-agent/registry-core`(更早还曾是 `@sema-ai/registry-core`)。本档 `0.19.0` 以下各节里的
 > 包名是**历史记录**,如实保留不追改。
 
+## 3.0.1 — 2026-09-22 — 纯文档 patch:订正幽灵版号、重写消费接入档到 3.0.0、README 真话、待裁账并入 ROADMAP、产品名统一、一致性门新增 4 条对抗语料
+
+**零行为改动、零类型改动、零 wire 面变化。**
+
+- 全仓订正开发期遗留的幽灵版号 `1.11.0`:这一批开发时叫 `1.11.0`,发布定版时改叫 `2.0.0`,但改名没
+  传导进源码注释与文档(npm 上从未有过 `1.11.0`)。本档给 config-center 产品的迁移句 `^1.11.0` 是一个
+  永远解析不到任何版本的提货范围,已订正为 `^2.0.0`。
+- 新增一格门:文档 / `src/` 里出现的 `x.y.z` 必须是本档真有的一节(或落在有理由的外部产品版本白名单
+  里)——不许再有第二个幽灵版号。
+- `docs/CONSUMER-INTEGRATION.md` 重写到 3.0.0(此前停在改名定版前一节,2.0.0/2.1.0/3.0.0 三版未跟):
+  删除两条今天会带消费方接错线的过期指路 —— 老 env 名 `CONFIG_CENTER_URL` 在真实部署里是**拒启键**
+  (已改名 `SEMA_REGISTRY_URL`);「service 与 client 都调 `loadLocalConfig`」的说法与四仓生产码
+  (零 import)不符,真实接线是 `FileConfigStore` 直连。补齐 `ConfigPath`/`formatConfigPath`、
+  `./conformance`、已删 `./api/wire` 四节。
+- README 改正一条过期的「待迁移」声明:cli 的 trust-rank 消费批早已兑现(不再是 pending)。
+- 三条仍然有效的历史待裁事项(GC 工具的 `new Date()`、`refIntegrityIssues` 无级联校验、
+  `atModelAllowlist` 空语义二义)从一份标着「历史存档」却记着未拍板项的文档,搬进 `ROADMAP.md`
+  「立案」(坐标复核到 3.0.0),原文档删除 —— 待裁事项只留一份真源。
+- 产品旧名(`sema-registry` / `sema-web`)统一为现名 `sema-web-admin`。
+- 一致性门语料新增 4 条对抗用例(`contributor: test`),覆盖:告警对象上 `domain` 缺席必须原样传成
+  缺席、逐条容错域与闸门域的结论必须隔离、域内条目键上的原型名(`__proto__`/`constructor`/`toString`)
+  不被剥键扫描吞掉、坏条目值里的秘密字面永不上线四个面。
+
 ## 3.0.0 — 2026-09-16 — 告警坐标改铸**结构化段** `ConfigPath`(BREAKING)+ 删死出口 `./api/wire`(BREAKING)+ wire 透传判据修原型链漏洞 + 跨仓一致性门 kit(新 subpath `./conformance`)
 
 > **版号裁定(发布方)**:本批三件里有两件是**纯 API 面**的破坏性改动 —— ①`EffectiveReadWarning` 的
@@ -445,7 +468,7 @@ parse 失败** —— 一份在上游合法的 `settings.json` 只因带了 `Pre
   两边可以直接对拍(派生 vs 登记),不必各自反射。
 - **config-center 产品(舰队管理台)**:①写侧仍走 `parseDomain`(严判,一字未变)—— 逐条容错只在**读**
   路径;②读面同 worker 服务:坏条目不再连坐;③它今天装的是改名前、冻结在 `0.15.0` 的旧名包,本版之前的
-  全部契约它都不认,提货 `^1.11.0` 是它自己的车。
+  全部契约它都不认,提货 `^2.0.0` 是它自己的车。
 
 ## 1.10.0 — 2026-09-09 — `models.models[].compat` 引擎兼容声明席(镜像 `OpenAICompletionsCompat`;新键=minor)
 

package/README.md

@@ -22,12 +22,12 @@
 > deprecate 标指向新名。
 
 Engine-agnostic, zero-dependency contract layer for the sema stack — **one source of truth** for the
-config domain across the center (the config-center product — today `sema-web` — the fleet admin), the
+config domain across the center (the config-center product — today `sema-web-admin` — the fleet admin), the
 server (the workers), and the client (desktop/CLI) seams. No two copies of the schema.
 
-> 命名说明:config-center 这个**产品**曾叫 `sema-registry`,现在是 `sema-web`(后续还会再改名)。
-> 本**包**名与产品名解耦,**不随产品改名而动**(1.0.0 这次改名是本包自身的正名,与产品名无关)——
-> 下文凡提「center / config-center 产品」即指该产品的当期实现。
+> 命名说明:config-center 这个**产品**曾叫 `sema-registry`,又改成 `sema-web`,现在是 `sema-web-admin`
+> (clay 令 2026-08-26 仓改名;后续仍可能再改)。本**包**名与产品名解耦,**不随产品改名而动**(1.0.0 这次
+> 改名是本包自身的正名,与产品名无关)—— 下文凡提「center / config-center 产品」即指该产品的当期实现。
 
 - **Source of truth**: `github.com/sema-agent/sema-settings-schema`, branch `main` (private org repo; renamed from `sema-registry-core` on 2026-08-26, old URLs redirect).
   仓名本步不动(只改包名)。
@@ -71,8 +71,12 @@ sound). `npm ls --prod` therefore shows only `zod`. Node built-ins only (`node:c
   step — those live in the consumers (engine import door, shell resolver), each on its own release schedule.
   1.2.0 adds the **trust ordering primitives**: `trustRank(layer)` (v2-design §1 verbatim, `managed 6 > global 5 >
   project 4 > local 3 > session 2 > task 1`) and `isAtLeast(layer, minTrust)` — the ladder every resolver is to
-  compare floors against; consumers retire their own rank tables onto it (the CLI's `TRUST_RANK` migration is
-  pending on its side, board [5807] ③ — exporting the primitive does not by itself make it the single source).
+  compare floors against; consumers retire their own rank tables onto it. **3.0.1 correction**: this used to say
+  the CLI's `TRUST_RANK` migration was still pending (board [5807] ③) — it shipped in the CLI's own 1.2.0
+  consumption batch (board [5815], 2026-08-31): the CLI's third literal copy of the ladder is deleted
+  (`src/sema/settings/keyContracts.ts` self-documents the retirement) and its resolver now really imports
+  `isAtLeast` from this package (`src/sema/settings/resolver.ts`). Exporting the primitive DID make it the
+  single source, for this consumer.
   `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 @@
-3.0.0
+3.0.1

package/conformance/cases/t01-absent-domain-key-not-null/expected.json

@@ -0,0 +1,93 @@
+{
+  "domains": {
+    "outcome": "effective",
+    "effective": {
+      "collab": {
+        "templates": []
+      },
+      "entitlement": {
+        "budgetGroups": [],
+        "groupBindings": [],
+        "subjects": [],
+        "tiers": []
+      },
+      "execution": {
+        "allowedLanes": [
+          "host"
+        ],
+        "required": false
+      },
+      "governance": {},
+      "hosts": {
+        "hosts": [
+          {
+            "approved": true,
+            "drain": false,
+            "enabled": true,
+            "labels": [],
+            "name": "box1"
+          }
+        ]
+      },
+      "limits": {},
+      "mcp": {
+        "servers": []
+      },
+      "models": {
+        "models": [
+          {
+            "api": "openai-completions",
+            "apiKeyEnv": "OPENAI_API_KEY",
+            "enabled": true,
+            "id": "m0-id",
+            "name": "m0",
+            "provider": "openai",
+            "quotaWeight": 1,
+            "reasoning": false,
+            "tier": "standard",
+            "vision": false
+          }
+        ],
+        "roles": {},
+        "tierGroups": []
+      },
+      "plugins": {
+        "plugins": []
+      },
+      "projects": {
+        "projects": {}
+      },
+      "prompts": {
+        "bindings": []
+      },
+      "rosters": {
+        "rosters": []
+      },
+      "runtime": {},
+      "scenarios": {
+        "scenarios": []
+      },
+      "skills": {
+        "skills": []
+      },
+      "systems": {
+        "systems": []
+      },
+      "workers": {
+        "workers": []
+      }
+    },
+    "warnings": [],
+    "metadata": {
+      "version": 7,
+      "updatedAt": "2026-09-16T00:00:00.000Z"
+    }
+  },
+  "wire": {
+    "derive": true
+  },
+  "localRoot": {
+    "derive": true,
+    "localVersion": 2247688933988744
+  }
+}

package/conformance/cases/t01-absent-domain-key-not-null/input.json

@@ -0,0 +1,29 @@
+{
+  "meta": {
+    "version": 7,
+    "updatedAt": "2026-09-16T00:00:00.000Z"
+  },
+  "domains": {
+    "models": {
+      "models": [
+        {
+          "name": "m0",
+          "provider": "openai",
+          "id": "m0-id",
+          "apiKeyEnv": "OPENAI_API_KEY"
+        }
+      ]
+    },
+    "hosts": {
+      "hosts": [
+        {
+          "name": "box1",
+          "approved": true
+        }
+      ]
+    },
+    "web-admin-ui": {
+      "theme": "dark"
+    }
+  }
+}

package/conformance/cases/t01-absent-domain-key-not-null/meta.json

@@ -0,0 +1,6 @@
+{
+  "contributor": "test",
+  "claim": "告警对象上 `domain` **缺席**(不是 `null`、不是空串)时,三腿必须原样传成缺席。消费方普遍写 `{domain: w.domain, …}` 这种投影(web-admin [7285] ③ 实测 `unread-config-file` 无必填 `domain`),谁把缺席折成 `null` 或 `\"\"`,谁就让下游多红一处而自己看不见。",
+  "firstRedOn": [],
+  "note": "一条输入里同时放两条 `unread-config-file`:`hosts.json`(非便携域 ⇒ **带** `domain`)与 `web-admin-ui.json`(非域名 ⇒ **不带** `domain`)。两种形并排,所以「把缺席一律折成 null」与「把 domain 整个丢掉」两种错法都会红,而不是只挡住其中一种。诚实边界:`unread-config-file` 是 `config.d/` 扫描**独有**的 kind(闭集里唯一 `domain` 可选的那条),所以「缺席传成缺席」这件事**结构上只在 local-root 腿上可观察**;domains / wire 两腿在本条上是零告警的正控(它们不该凭空造出这条告警)。firstRedOn 空是**实跑**出来的:五个历史版本(1.0.0/1.5.0/1.10.0/2.0.0/2.1.0)在本条上全绿 ⇒ 护栏,不是回归凭证。"
+}

package/conformance/cases/t02-entry-salvage-vs-whole-domain-refusal/expected.json

@@ -0,0 +1,16 @@
+{
+  "domains": {
+    "outcome": "rejected",
+    "stage": "validate"
+  },
+  "wire": {
+    "outcome": "rejected",
+    "stage": "validate",
+    "why": "domains 腿是拒绝态,不派生;wire 腿把同一份 rosters 文档交给同一个 buildEffective(skills/prompts 之外零改道),闸门域的 throw 穿过信封层 ⇒ 拒绝层与 domains 腿相同"
+  },
+  "localRoot": {
+    "outcome": "rejected",
+    "stage": "validate",
+    "why": "models 与 rosters 都是便携域,两份文件层都过得去(都是 JSON 对象),拒绝发生在域校验层而不是 parse 层"
+  }
+}

package/conformance/cases/t02-entry-salvage-vs-whole-domain-refusal/input.json

@@ -0,0 +1,32 @@
+{
+  "meta": {
+    "version": 7,
+    "updatedAt": "2026-09-16T00:00:00.000Z"
+  },
+  "domains": {
+    "models": {
+      "models": [
+        {
+          "name": "keep",
+          "provider": "openai",
+          "id": "keep-id",
+          "apiKeyEnv": "OPENAI_API_KEY"
+        },
+        {
+          "name": 5,
+          "id": "bad-id"
+        }
+      ]
+    },
+    "rosters": {
+      "rosters": [
+        {
+          "name": "r1"
+        },
+        {
+          "name": 5
+        }
+      ]
+    }
+  }
+}

package/conformance/cases/t02-entry-salvage-vs-whole-domain-refusal/meta.json

@@ -0,0 +1,6 @@
+{
+  "contributor": "test",
+  "claim": "同一份坏条目,放进逐条容错的域(`models`,`DOMAIN_READ_FALLBACK=\"default\"`)与放进 fail-loud 的闸门域(`rosters`,`=\"throw\"`),结论必须不同:前者丢那一条并恰报一条 `entry-dropped`、**不得同时**报 `domain-defaulted`(一域一个结论);后者**整份读在 validate 层被拒**(不是回落到 schema 默认 —— 对闸门域回落就是放宽闸门)。server [6782] 与 web-admin [7285] G2/G4 是同一件事的两半,跨腿读错会把『逐条容错』顺手放宽到闸门域,把这条设计为拒的输入读成绿(带两条 `entry-dropped`)。",
+  "firstRedOn": [],
+  "note": "【claim 措辞订正 2026-09-19,test 自纠】初稿写的是「后者整域回落」—— **是本方写错**:「回落」是 `DOMAIN_READ_FALLBACK=\"default\"` 那一族的动作,闸门域是 `\"throw\"` = fail-loud,整份读被拒。出处:契约自述 `config-fns.js` 的 `DOMAIN_READ_FALLBACK` 头注(defaulting would LOOSEN gates)+ 契约自带 `c05-gate-domain-bad-entry-throws` 金样(rejected/validate)+ 本仓 historical 实跑五版一致。claim 已按实测改写,对抗意图不变。两域放**同形**坏条目(`name` 是数字):`models`(DOMAIN_READ_FALLBACK=\"default\")与 `rosters`(=\"throw\",且是唯一一个便携的数组形闸门域)。3.0.0 实测:闸门域坏条目使**整份读**在 `validate` 层拒,三腿同形 —— 因此本条的期望是 `rejected/validate`,`models` 那半场在同一份输入里**结构上观察不到**。这正是本条的判别力所在:一个把逐条容错顺手放宽到闸门域的消费方,会把这条设计为拒的 case 读成绿(带两条 `entry-dropped`)。claim 前半场(`models` 恰一条 `entry-dropped`、零 `domain-defaulted`)由 verify.mjs 的配对正控臂(同一份输入去掉 `rosters` 域)钉住,读数记在 _SUMMARY.json 的 t02.pairedControl。claim 里「闸门域整域回落」的『回落』一词与契约自述的 `\"throw\"` = fail-loud 不符 —— 见 _SUMMARY.json 的 claimVsObserved。firstRedOn 空是**实跑**出来的:1.0.0/1.5.0/1.10.0/2.0.0/2.1.0 五版在本条上都是 expected-rejected(闸门域坏条目整份拒这条律从 1.0.0 起一字未动)⇒ 护栏,不是回归凭证。"
+}

package/conformance/cases/t03-prototype-name-key-not-swallowed/expected.json

@@ -0,0 +1,107 @@
+{
+  "domains": {
+    "outcome": "effective",
+    "effective": {
+      "collab": {
+        "templates": []
+      },
+      "entitlement": {
+        "budgetGroups": [],
+        "groupBindings": [],
+        "subjects": [],
+        "tiers": []
+      },
+      "execution": {
+        "allowedLanes": [
+          "host"
+        ],
+        "required": false
+      },
+      "governance": {},
+      "hosts": {
+        "hosts": []
+      },
+      "limits": {},
+      "mcp": {
+        "servers": []
+      },
+      "models": {
+        "models": [
+          {
+            "api": "openai-completions",
+            "apiKeyEnv": "OPENAI_API_KEY",
+            "enabled": true,
+            "id": "m0-id",
+            "name": "m0",
+            "provider": "openai",
+            "quotaWeight": 1,
+            "reasoning": false,
+            "tier": "standard",
+            "vision": false
+          }
+        ],
+        "roles": {},
+        "tierGroups": []
+      },
+      "plugins": {
+        "plugins": []
+      },
+      "projects": {
+        "projects": {}
+      },
+      "prompts": {
+        "bindings": []
+      },
+      "rosters": {
+        "rosters": []
+      },
+      "runtime": {},
+      "scenarios": {
+        "scenarios": []
+      },
+      "skills": {
+        "skills": []
+      },
+      "systems": {
+        "systems": []
+      },
+      "workers": {
+        "workers": []
+      }
+    },
+    "warnings": [
+      {
+        "domain": "models",
+        "keys": [
+          [
+            "models",
+            0,
+            "__proto__"
+          ],
+          [
+            "models",
+            0,
+            "constructor"
+          ],
+          [
+            "models",
+            0,
+            "toString"
+          ]
+        ],
+        "kind": "unknown-keys-dropped"
+      }
+    ],
+    "metadata": {
+      "version": 7,
+      "updatedAt": "2026-09-16T00:00:00.000Z"
+    }
+  },
+  "wire": {
+    "derive": true
+  },
+  "localRoot": {
+    "derive": true,
+    "localVersion": 3232605402901914
+  }
+}

package/conformance/cases/t03-prototype-name-key-not-swallowed/input.json

@@ -0,0 +1,25 @@
+{
+  "meta": {
+    "version": 7,
+    "updatedAt": "2026-09-16T00:00:00.000Z"
+  },
+  "domains": {
+    "models": {
+      "models": [
+        {
+          "name": "m0",
+          "provider": "openai",
+          "id": "m0-id",
+          "apiKeyEnv": "OPENAI_API_KEY",
+          "__proto__": {
+            "polluted": true
+          },
+          "constructor": {
+            "polluted": true
+          },
+          "toString": "nope"
+        }
+      ]
+    }
+  }
+}

package/conformance/cases/t03-prototype-name-key-not-swallowed/meta.json

@@ -0,0 +1,6 @@
+{
+  "contributor": "test",
+  "claim": "`__proto__` / `constructor` / `toString` 作为域内条目的键,**在坏条目上**:告警坐标必须把它当**普通字面键**点名、`effective` 的原型必须不被污染、三腿读法一致。本方在 server 7.87.0 G6 实测过同族(`answer.answers[0].__proto__` ⇒ `400 request.field_invalid` 且 `unknownKeys` 逐字点名);也在本仓自证里把 `__proto__` 的断言方向搞反过一次(`JSON.parse` + spread **保留** own 属性、plain assignment 才污染原型),所以这条同时是护栏。",
+  "firstRedOn": [],
+  "note": "【claim 收窄 2026-09-19,server [7621] ① 指出、主会话亲验】初稿把 `__proto__` **作好条目的 record 键**也算进「当普通字面键报进坐标」。**实测不成立**:`parseDomainLoud('limits', {__proto__:1, ok:2}, …)` 的告警 keys 只有 `['ok']`,`parsed` 上无 own `__proto__`(原型仍是 `Object.prototype`)—— 好条目上的原型名键在 zod 3 正常解析路径上本来就被丢,是 [7617] 已知限制,不是本条要钉的东西。claim 已收窄到**坏条目**那半场(真的、可判、有判别力);好条目那半场不入语料。与契约仓 c12 的差别:c12 打的是**顶层键**(`k in built` 一路问到 Object.prototype ⇒ open-world 承诺失效),本条打的是**域内条目的键**(剥键扫描 `collectDropped` 的 `Object.keys` / `hasOwnProperty` 两处判据,以及 salvage/rebase 路径上的对象重建)。构造坑(本方亲踩,记在此处防下一个人重踩):用 JS 对象字面量 `{\"__proto__\": {...}}` 造这条输入会**设置原型而不是加一个键**,于是 `isPlainJsonObject` 判假、整条扫描被跳过、case 测了个寂寞;语料走 `JSON.parse` 才拿到自有键 —— 这也是为什么这条必须以磁盘语料形存在,而不是测试里一个内联对象。firstRedOn 空是**实跑**出来的:五个旧版(1.0.0/1.5.0/1.10.0/2.0.0/2.1.0)在本条上全绿 —— S-332 那个 bug 只落在**顶层键**那一层(契约 c12 五版全红),域内条目键这一层从 1.0.0 起就一直对 ⇒ 本条是护栏,不是回归凭证。"
+}

package/conformance/cases/t04-secret-literal-never-in-warning-value/expected.json

@@ -0,0 +1,105 @@
+{
+  "domains": {
+    "outcome": "effective",
+    "effective": {
+      "collab": {
+        "templates": []
+      },
+      "entitlement": {
+        "budgetGroups": [],
+        "groupBindings": [],
+        "subjects": [],
+        "tiers": []
+      },
+      "execution": {
+        "allowedLanes": [
+          "host"
+        ],
+        "required": false
+      },
+      "governance": {},
+      "hosts": {
+        "hosts": []
+      },
+      "limits": {},
+      "mcp": {
+        "servers": []
+      },
+      "models": {
+        "models": [
+          {
+            "api": "openai-completions",
+            "apiKeyEnv": "OPENAI_API_KEY",
+            "enabled": true,
+            "id": "keep-id",
+            "name": "keep",
+            "provider": "openai",
+            "quotaWeight": 1,
+            "reasoning": false,
+            "tier": "standard",
+            "vision": false
+          }
+        ],
+        "roles": {},
+        "tierGroups": []
+      },
+      "plugins": {
+        "plugins": []
+      },
+      "projects": {
+        "projects": {}
+      },
+      "prompts": {
+        "bindings": []
+      },
+      "rosters": {
+        "rosters": []
+      },
+      "runtime": {},
+      "scenarios": {
+        "scenarios": []
+      },
+      "skills": {
+        "skills": []
+      },
+      "systems": {
+        "systems": []
+      },
+      "workers": {
+        "workers": []
+      }
+    },
+    "warnings": [
+      {
+        "domain": "models",
+        "kind": "entry-dropped",
+        "path": [
+          "models",
+          1
+        ]
+      },
+      {
+        "domain": "models",
+        "keys": [
+          [
+            "models",
+            0,
+            "apiKeyInline"
+          ]
+        ],
+        "kind": "unknown-keys-dropped"
+      }
+    ],
+    "metadata": {
+      "version": 7,
+      "updatedAt": "2026-09-16T00:00:00.000Z"
+    }
+  },
+  "wire": {
+    "derive": true
+  },
+  "localRoot": {
+    "derive": true,
+    "localVersion": 2614200563056761
+  }
+}

package/conformance/cases/t04-secret-literal-never-in-warning-value/input.json

@@ -0,0 +1,25 @@
+{
+  "meta": {
+    "version": 7,
+    "updatedAt": "2026-09-16T00:00:00.000Z"
+  },
+  "domains": {
+    "models": {
+      "models": [
+        {
+          "name": "keep",
+          "provider": "openai",
+          "id": "keep-id",
+          "apiKeyEnv": "OPENAI_API_KEY",
+          "apiKeyInline": "sk-FAKE-CORPUS-0000000000000000"
+        },
+        {
+          "name": "bad",
+          "provider": "openai",
+          "id": "bad-id",
+          "api": "ghp_FAKE-CORPUS-1111111111111111"
+        }
+      ]
+    }
+  }
+}

package/conformance/cases/t04-secret-literal-never-in-warning-value/meta.json

@@ -0,0 +1,14 @@
+{
+  "contributor": "test",
+  "claim": "坏条目的**值**里埋 `sk-`/`ghp_` 形秘密字面:告警面必须**名字上线、值永不上线**(与 `hosts-grandfathered` 同律)。本方给 web-admin G3 加过同款正控 —— 没有正控时『没打印秘密』与『判据没跑到那一行』同形。",
+  "firstRedOn": [
+    "settings-schema@1.0.0",
+    "settings-schema@1.10.0",
+    "settings-schema@1.5.0"
+  ],
+  "secrets": [
+    "sk-FAKE-CORPUS-0000000000000000",
+    "ghp_FAKE-CORPUS-1111111111111111"
+  ],
+  "note": "两条秘密走**两条不同的告警路径**,所以「值不上线」在两条路上分别被判:①`sk-` 那把是**存活条目**上一个未知键的值 ⇒ 只该出现在 `unknown-keys-dropped` 的键坐标里(键名 `apiKeyInline` 上线、值不上线);②`ghp_` 那把是**被丢条目**上一个 enum 字段的值 ⇒ zod 的 `invalid_enum_value` 会把 `received` 原样回显,只有 `sanitizeZodError`/`redactSecrets` 挡着 ⇒ 它落在 `entry-dropped.error` 的文案面上,而 `findSecretLeaks` 恰恰扫这一面。正控(判据到达性)由 expected 的两条告警坐标承担:`[\"models\",0,\"apiKeyInline\"]` 与 `[\"models\",1]` 必须在场,证明剥键扫描与抢救路径都真跑到了。扫描器自身的判别力由 verify.mjs 的 decoy 臂钉住(把一个**非**秘密形的 enum 值当秘密登记 ⇒ findSecretLeaks 必须命中),否则「零命中」与「扫描器恒返回空」同形。语料里的两把是**假串**,不是任何真凭据。⚠️ firstRedOn 里的三个旧版**不是在秘密轴上红的**:逐版直读 `findSecretLeaks`(1.0.0/1.5.0/1.10.0/2.0.0/2.1.0)**五版全零命中**;那三版红是因为 1.11.0 才有的逐条容错还不存在,整个 `models` 域退默认(只报一条 `domain-defaulted`),于是 effective 与告警多重集都对不上。⇒ 在**秘密轴**上这条同样是护栏;把「这条 case 在旧版上红」读成「旧版泄过秘密」是从读数推到结论的那一类错,读数见 _historical-readout.json#t04SecretAxis。"
+}

package/conformance/historical/settings-schema@1.0.0.json

@@ -8,9 +8,10 @@
     "why": "旧版坐标是点号串、今天是段数组;归一 = 按 `.` 拼串,这正是 3.0.0 要消掉的有损编码(`[\"a.b\"]` 与 `[\"a\",\"b\"]` 归一后同串)"
   },
   "summary": {
-    "pass": 99,
-    "diff": 36,
-    "expected-rejected": 12,
+    "pass": 105,
+    "diff": 39,
+    "diff-ledgered": 0,
+    "expected-rejected": 15,
     "harness-error": 0,
     "skipped": 0
   },
@@ -955,6 +956,86 @@
         }
       }
     },
+    "t01-absent-domain-key-not-null": {
+      "firstRed": false,
+      "legs": {
+        "domains": {
+          "status": "pass",
+          "behaviour": false,
+          "detail": "effective, warnings and metadata all match"
+        },
+        "wire": {
+          "status": "pass",
+          "behaviour": false,
+          "detail": "effective, warnings and metadata all match"
+        },
+        "localRoot": {
+          "status": "pass",
+          "behaviour": false,
+          "detail": "effective, warnings and metadata all match"
+        }
+      }
+    },
+    "t02-entry-salvage-vs-whole-domain-refusal": {
+      "firstRed": false,
+      "legs": {
+        "domains": {
+          "status": "expected-rejected",
+          "behaviour": false,
+          "detail": "rejected at `validate` as expected"
+        },
+        "wire": {
+          "status": "expected-rejected",
+          "behaviour": false,
+          "detail": "rejected at `validate` as expected"
+        },
+        "localRoot": {
+          "status": "expected-rejected",
+          "behaviour": false,
+          "detail": "rejected at `validate` as expected"
+        }
+      }
+    },
+    "t03-prototype-name-key-not-swallowed": {
+      "firstRed": false,
+      "legs": {
+        "domains": {
+          "status": "pass",
+          "behaviour": false,
+          "detail": "effective, warnings and metadata all match"
+        },
+        "wire": {
+          "status": "pass",
+          "behaviour": false,
+          "detail": "effective, warnings and metadata all match"
+        },
+        "localRoot": {
+          "status": "pass",
+          "behaviour": false,
+          "detail": "effective, warnings and metadata all match"
+        }
+      }
+    },
+    "t04-secret-literal-never-in-warning-value": {
+      "firstRed": true,
+      "legs": {
+        "domains": {
+          "status": "diff",
+          "behaviour": true,
+          "detail": "1 effective diff(s), 2 missing / 1 extra warning(s), 0 metadata diff(s)"
+        },
+        "wire": {
+          "status": "diff",
+          "behaviour": true,
+          "detail": "1 effective diff(s), 2 missing / 1 extra warning(s), 0 metadata diff(s)"
+        },
+        "localRoot": {
+          "status": "diff",
+          "behaviour": true,
+          "detail": "1 effective diff(s), 2 missing / 1 extra warning(s), 0 metadata diff(s)"
+        }
+      }
+    },
     "z01-every-domain-empty-object": {
       "firstRed": false,
       "legs": {