@sema-agent/settings-schema 6.0.0 → 6.1.0

package/CHANGELOG.md

@@ -6,6 +6,168 @@
 > `@sema-agent/registry-core`(更早还曾是 `@sema-ai/registry-core`)。本档 `0.19.0` 以下各节里的
 > 包名是**历史记录**,如实保留不追改。
 
+## 6.1.0 — 2026-09-25 — 四件 additive:`entry-dropped` 身份(S-712)· 中心凭证信封 + 三态判别器(S-698)· `RestartSignal` 一处定义(S-741)· 中心凭证两键名 + 二选一判官(S-742);`redactSecrets` 私钥 PEM 串内任意位置且判在替换前(6.0.0 起三面既有盲点顺带关)
+
+> 本节四件全 additive(新可选键 / 新导出 / 新文件),零删零改名;版号与节标题由发版方写。判档口径见下方「发版纪律」:
+> 新键 / 新导出 = minor。
+
+### S-712 · `entry-dropped` 告警带被丢条目的身份(`identity?`,additive)
+
+`EffectiveReadWarning` 的 `entry-dropped` 臂加可选键 `identity?: DroppedEntryIdentity`(`{ name?: string; id?: string;
+enabled?: boolean }`,新导出类型);`DroppedEntry`(`salvageEntries` 的记账行)同带。**一条律,不分域**:只从被丢条目
+**原文**取 —— 字符串 `name` / `id`、布尔 `enabled`,只认自有**数据**属性(不触发访问器),类型不对 ⇒ 不带该键(不猜、
+不 `String()` 转换),`redactSecrets` 会改动的串 ⇒ 不带该键(与坐标段、`error` 文案**同一只**脱敏判据:坐标段必须
+在场所以打码出门;身份可缺,打过码的串不再是身份,所以是**不带**而不是打码),三键都读不出 ⇒ 不带 `identity`(不铸
+空对象)。**缺席 = 读不出**(非字符串,或不能原样出门),两种原因刻意不分:消费方的正确处置相同(身份未知)。铸点单一:数组 / Record 两种集合形共用
+一只记账行铸点,域面(`buildEffective`)与 wire 面(skills manifest)共用一只告警铸点;`projectWarning` 的
+`entry-dropped` 臂把 `identity` 带进投影(缺席不铸键)。
+
+- **谁需要** = server(S-712 半场):它今天拿告警坐标回读原文档取被丢模型条目的身份(`read-warnings.ts`
+  `droppedEntryIdentity(rawDoc, path)`),本地腿的原文档是解析之后再读一次盘得来的,两次读之间文件一改就对不上,
+  只能 fail-closed 整组拒;身份随告警走之后这只函数换数据源、原文档入参删除。
+- **谁受伤** = 运行期无(additive 可选键;持 `EffectiveReadWarning` 穷举 `switch` 的消费方零编译红,没有新 kind)。
+  **提货成本一处**(对抗轮 #1 订正:初稿写「web-admin 无适配器」是错的):web-admin 有一致性适配器
+  (`src/lib/config/conformance-adapter.ts`)与**自己入库**的语料,其中 `wa05-credential-as-unknown-key-in-a-salvaged-skills-entry`
+  在一条被丢的 skills 条目(`name:"broken"`)上断言 `entry-dropped`,且 `test/settings-schema-conformance.test.ts` 要求
+  每条 `wa*` 在 domains 腿 `pass` ⇒ 提货 6.1.0 时这一条会报告警差(多出 `identity:{name:"broken"}`),要按新读数重新
+  加冕 —— 发布帖 @web-admin 点名。server 两条读腿的告警直接来自本包 `onWarning`,提货即带身份,不红。
+- **消费方** = server(`splitFoldedReadWarnings` 改读 `w.identity`;`enabled` 缺席按今天的 `!== false` 口径自判;
+  `name` 缺席 = 读不出(非字符串**或**脱敏会改动它),模型面按身份未知处置时拒因句请说「没有可读的名字」,别说
+  「不是字符串」—— 对抗轮 #4 的二义在契约层刻意不分,措辞归读方);
+  web-admin / cli 可选读(管理面 / 壳在「条目被丢」提示里点名);core n/a。
+- **一致性语料再加冕**(`npm run conformance:bless`,additive 键):6 条 case 的 `domains` 期望多出 `identity`
+  (`c01` / `c02` / `c23` / `cli01` / `cli02` / `t04`,共 8 条告警;零删、零改其它字段,`baseline.json` 零变化)。
+  kit 自带语料随包走,消费方无需为它 bless(自己入库的语料见上一条)。**新语料 `c40-s712-identity-only-what-reads-out`**
+  (对抗轮 #5):被丢条目的 `name` 是 Bearer 形串、`enabled` 是 `"yes"` ⇒ 身份只剩 `id`;正控条目三键齐全。变异门
+  `test/conformance-mutation.test.ts` 为身份铸点登记两靶(脱敏判据 / enabled 只收布尔),加 `c40` 前两靶变异体全绿,
+  加后各红。第三条律(只认数据属性)JSON 表达不出 getter,由单测看着,如实登记。
+- **historical 归一器加投影级钩子**(对抗轮 #3,`./conformance` additive):`ConformanceNormalizer.warning?(p)`,先于
+  `path` 作用、两侧同过;`scripts/conformance-historical.mjs` 的有损归一器用它剥掉 `entry-dropped.identity` —— 不剥的话,
+  照 `docs/CONFORMANCE.md` 重跑 historical 会把 6 条 case 记成旧版行为红(2.1.0 由 1 条涨到 7 条,
+  `test/conformance-corpus.test.ts` 随之红;对抗腿实跑)。修后在隔离副本里真重跑 2.1.0 / 6.0.0:行为红 1 / 0,
+  `firstRedOn` 零变化,语料测试 12 / 12;入库证据未重写(读数与入库一致)。
+- **红先**:`test/entry-dropped-identity-6.1.0.test.ts` 对 6.0.0 源 **9 红 / 2 绿**(绿的两格 = 读不出 ⇒ 缺席、
+  好条目零告警的控制格),改源后 11 / 11。对抗轮(独立 opus 腿,codex 缺席顶替)追加:#2 秘密判据两格(NBSP 分隔 /
+  短令牌的 Bearer 串随身份明文出门;判据与坐标脱敏同一只)对首版 **2 红** → 修后绿;#3 投影钩子一格 **1 红**(tsc 同红)→
+  绿;#5 变异两靶 **2 红**(变异体存活)→ 加 `c40` 后绿。**验修轮**(同一 opus 腿,只核修复提交):11 条原发现
+  读数全闭合;新 **N1 [medium]**:#2 改用 `redactSecrets` 判据后,PEM 私钥(头里带空格,脱敏器的定点两遍够不着)作
+  `name` / `id` 随身份明文出门(首版的 `containsSecretToken` 扣得住,6.0.0 无身份 —— 秘密轴回归;同一盲点在 6.0.0 的
+  坐标 / `error` 脱敏里本就存在)⇒ **在源头修** `redactSecrets`:出口不变量 `containsSecretToken(redactSecrets(x)) === false`,
+  定点两遍之后探测器仍判阳 ⇒ 整串打码;坐标、`error` 文案、身份三面一起补上,身份判据仍是 `redactSecrets(v) === v`
+  一只。红先两格(PEM 身份 / 脱敏器出口不变量)对 `0397672` **2 红** → 绿。**N4 [nit]**:`c40` 加「短 Bearer 令牌」与
+  「PEM 私钥」两条被丢条目,变异门加两靶(身份判据退回旧探测器 / 去掉整串兜底),对旧 `c40` **2 红**(变异体存活)→
+  新 `c40` 下绿。**N3 [nit]**(`readEffectiveWire` 的 `Number.isFinite` 与 `RestartSignal` 的 `z.number().finite()` 是同一条
+  判据的两处拼写)登记不修:语义等价,抽一只共用定义要为一行判据新开叶模块,留作下次触碰时顺手。
+  **codex 一审**(gpt-6-astra,`--base 5153d2a`,对 `7b92977`,needs-attention 1 [high]):PEM 私钥的 header 不在串首
+  (前导换行 / `key: ` 前缀)时,探测器(`SECRET_LITERAL_RE` 串首锚 + 按空格分词拆散带空格的 header)看不见,
+  `redactSecrets` 原样放行 ⇒ `identity.id` / 投影 / Record 坐标带出整把私钥(6.0.0 的告警不暴露它)。**源头修**:
+  新导出 `PRIVATE_KEY_PEM_HEADER`(`types.ts`,私钥 PEM header 的**唯一**定义,无锚)—— `SECRET_LITERAL_RE` 由它拼出
+  (源串与 6.0.0 逐字相同,有钉),`redactSecrets` 的整串兜底加「串内任意位置见到它 ⇒ 整串扣留」;坐标 / `error` /
+  身份三面同一只。**刻意不**放宽校验侧探测器 `containsSecretToken`(让它拒串中 PEM = 收紧它校验的每个字段 = major),
+  登记为欠账。红先三格(前导换行 + 前缀的身份 / 脱敏器 / 源串拼装钉)对 `7b92977` **3 红** → 绿;`c40` 加一条带
+  `key: ` 前缀 PEM 的被丢条目,变异门加一靶(去掉「串内任意位置」一道),对旧 `c40` **1 红**(变异体存活)→ 新 `c40` 下绿。
+  **codex 验修轮**(`--base 7b92977`,对 `050c8e6`,needs-attention 1 [high]):修复自身的**顺序缺口** —— `sk-note:-----BEGIN
+  PRIVATE KEY-----…` 这类密钥形前缀**紧贴** header 的串,令牌那一遍先把 `sk-note:-----BEGIN` 整段换成 `[redacted-secret]`,
+  替换后的 header 检查看不到 header,私钥体原样出门。修:`PRIVATE_KEY_PEM_HEADER` 改判**原文**(任何替换之前),仍是
+  `redactSecrets` 一处。红先四面各一格(坐标 / error / 身份 / 投影 + 秘密扫描,Ed25519 私钥现场生成)对 `050c8e6`
+  **3 红 / 1 绿**(身份面 `050c8e6` 已扣留)→ 4 绿;`c40` 加该形(作被丢条目 `id` 与 `roles` 坏键),变异门加一靶
+  (检查挪回替换之后)对旧 `c40` **1 红** → 绿。**对 6.0.0 的判定**:同一夹具在 `5153d2a` 的独立树上跑,坐标 / error /
+  投影三面**同样泄**(6.0.0 起的既有盲点,不是本版回归);身份面是本版新面,`050c8e6` 已扣留。本版把三面既有盲点一并关掉。
+- **边界(如实登记)**:身份只取 `name` / `id` / `enabled` 三键;server 现有载体还读 `provider`,它不是身份,
+  不在本键里 —— 要不要把 `provider` 也随告警走是 server 半场的决定(可继续按坐标回读或从投影外取),本版不猜。
+
+### S-698 · 中心凭证文件的信封形 `CenterCredentialEnvelope` + 三态判别器 `parseCenterCredentialFile`(新文件,additive)
+
+新模块 `src/center-credential.ts`(主 barrel 导出,不开新 subpath —— 与 `cross-session.ts` 同:纯 zod、browser-safe):
+`CENTER_CREDENTIAL_ENVELOPE_KIND = "user-session"`、`CenterCredentialEnvelope`(zod,`.strict()`;`kind` 字面、
+`accessToken`(JWT,`looksLikeJwt`)/ `refreshToken` 走与裸行**同一条令牌律**(可打印 ASCII 0x20–0x7E、首尾可见、中间可有空格)、`expiresAt` =
+RFC 3339 date-time(zod `datetime({offset:true})` 管日历有效性,再补「秒必备 + 偏移必须 `±hh:mm` 且时 00–23 / 分 00–59」
+zod 放过的形;不收闰秒 `:60`)、`issuer` = `NON_SECRET_URL`(签发它的中心的基础 URL;与 `remoteExec` 的 `apiUrl` /
+`endpoint` 同一只判据,不另写更窄的一份))、类型 `CenterCredentialFile` 与 `parseCenterCredentialFile(text)`。判别律
+(design/325 §1)一条、唯一实现:`trim()`(含 BOM)后空 ⇒ `unreadable("empty")`;`{` 开头 ⇒ 只按信封读,失败 = `unreadable`
+(**不回落**裸行);否则取首行(第一个 CR / LF 之前),是令牌 ⇒ `bare`,不是 ⇒ `unreadable`(放不进 Authorization
+头的行不是 bearer)。`reason` 不回显文件内容(只点字段名 + zod 问题码 +
+未知键个数;`JSON.parse` 的报错会引用原文片段,不转述)。
+
+- **谁需要** = S-698 长寿引擎续签:壳登录后可能关掉、引擎继续跑几天,访问令牌过期后中心请求逐条失败;信封让
+  引擎手里有 refresh token 与到期时刻,续签器(server 半场)据此在到期前续。
+- **谁受伤** = 无(新导出、新文件)。server 改调本判别器之后,相对它今天的读法(整段 `trim()` 后当 bearer)有
+  **三处行为差**,如实登记,都只在今天本就发不对的文件上可见:① **多行**裸行文件 ⇒ 只取首行(今天发出去的 header
+  含换行、不合法);② `trim()` 后以 `{` 开头的文件 ⇒ 今天当 bearer 发出去,本判别器判信封、读不成即 `unreadable`
+  (判别律本身);③ 首行含控制 / 非 ASCII 字符 ⇒ `unreadable`(前面粘了不可见字符的信封今天会连同 refreshToken 一起当 bearer
+  发出门 —— 对抗轮 #7)。**如实登记**:Latin-1 令牌今天能用(HTTP 头的 ByteString 收、中心逐字比得上),这里判
+  `unreadable`(非 ASCII 与不可见字符分不开,取 fail-closed);含空格的口令式共享令牌照收(验修轮 N2)。同一个令牌
+  走 `SEMA_REGISTRY_TOKEN`(env 腿)不过本律 —— env 值逐字承运与 server 今天同,要不要让 env 值也过令牌律归 server 半场。
+- **消费方** = server(`src/center-credential.ts` 文件形 `read()` 改调 `parseCenterCredentialFile`:`bare` ⇒ 既有
+  `classify`;`envelope` ⇒ `accessToken` 按 `user-jwt` 分箱 + 续签器读 `refreshToken` / `expiresAt` / `issuer`;
+  `unreadable` ⇒ 既有不可读臂);cli(L-653 壳半场:登录 / device-code 成功后写信封,写前用 `CenterCredentialEnvelope`
+  自校);web-admin n/a(端点已在);core n/a。
+- **红先**:`test/center-credential-envelope-6.1.0.test.ts`(经主 barrel 取,导出面同测)对 6.0.0 源 **14 红 / 0 绿**,
+  改源后 14 / 14。对抗轮(独立 opus 腿,codex 缺席顶替)追加四格,对首版 **4 红** → 修后 18 / 18:#6 偏移越界
+  (`+99:99` / `+24:00` / `+23:60` / `-99:00` 首版判信封、`Date.parse` 为 NaN)· #7 `{` 前粘 trim 不剥的字符
+  (`\u0085` / `\u0001` / `\u00AD` …)首版整份信封判 bare · #7 裸行令牌律 · #10 `accessToken` 带 CRLF / 是 `wpt_` 拉取令牌
+  首版判信封。验修轮 N2(令牌律首版拒掉含空格的口令式共享令牌)两格对 `6f22564` **2 红** → 放宽为「可打印 ASCII、
+  首尾可见」后绿。
+
+### S-742 · 中心凭证两个声明键名 `CENTER_CREDENTIAL_ENV` + 二选一判官 `judgeCenterCredentialDeclaration`(additive)
+
+同 `src/center-credential.ts` 尾段:`CENTER_CREDENTIAL_ENV = { token: "SEMA_REGISTRY_TOKEN", tokenFile:
+"SEMA_REGISTRY_TOKEN_FILE" } as const`;类型 `CenterCredentialDeclaration`;`judgeCenterCredentialDeclaration(env)` →
+`{from:"env"; token}` | `{from:"file"; path}` | `{from:"absent"}`。规则从 server `readCenterCredentialDeclaration`
+上提、**逐字同**:空串 = 未设(不 trim);两个都设(非空)⇒ throw,拒句逐字取 server c60beebe
+`src/center-credential.ts:93-96`(「… are both set — pick exactly one: … Two writers on one credential is a guess, not a
+config.」,点名两键、不回显值);只读这两个键。**一处有意的差**:server 在这一步把文件路径解析成绝对路径
+(`node:path` `resolve`),本包纯契约不碰 `node:path`、也不知道读方的 cwd ⇒ `path` 原样返回,解析留给读方。
+
+- **谁需要** = 管理面(给 worker 渲染 env)与壳(给本机引擎写 env)今天各自手抄这两个键名,规则只活在 server
+  —— 手抄键名会静默漂(C-R75);上提后三方 import 同一份键名与同一条规则([8325] 一请,server [8326] 认领)。
+- **谁受伤** = 无(新导出)。
+- **消费方** = server(`readCenterCredentialDeclaration` 改为 `judgeCenterCredentialDeclaration(env)` + 自己的
+  `resolvePath`;`CENTER_TOKEN_ENV` / `CENTER_TOKEN_FILE_ENV` 两常量改引 `CENTER_CREDENTIAL_ENV`);web-admin(worker env
+  渲染处两键名改 import,[8327] 同波一天);cli(本机引擎 env 写入处改 import;写前可用判官自校不会同设);core n/a。
+- **红先**:`test/center-credential-declaration-6.1.0.test.ts`(env / file / absent / both 四格 + 空串两格 + 键名 +
+  只读两键,期望拒句是从 server 源**抄来**的字面,不从实现派生)对 6.0.0 源 **7 红 / 0 绿**,改源后 7 / 7。
+
+### S-741 · 重启信号 `RestartSignal` 定义一次:心跳键 `InstanceAnnouncement.restart?` + `/health` 读法 `readRestartSignal`(additive)
+
+`src/fleet.ts` 新导出 `RestartSignal`(zod + 类型)= `{ reasons: z.array(z.string().min(1)).min(1), version: z.number().finite(),
+since: z.number().int().nonnegative() }` 与 `readRestartSignal(health: unknown): RestartSignal | undefined`;`InstanceAnnouncement`
+加 `restart: RestartSignal.optional()`(同一只 schema 对象,测试按运行期对象同一钉住;`InstanceRegistration` =
+`InstanceAnnouncement.extend(…)`,随之同带)。**在场 ⇔ 需要重启**,形里没有 `required` 布尔。`/health` 一侧:
+**`InstanceHealth` 形不动**(passthrough,`restart` 与顶层冗余布尔 `restartRequired` 照 6.0.0 原样承运、不入类型),
+读它走 `readRestartSignal`(对 `health.restart` safeParse,形不合 / 缺席 / 非对象 / 访问器抛错 ⇒ `undefined`,不抛;
+只认 `restart`,不读 `restartRequired`)。`version` 与 `readEffectiveWire` 读配置版本**同一条判据**(有限数)。
+
+> **形的裁定(发布方,两次)**:① 任务书初稿写的是 `{ required: true, reasons, version: string, since: string }`。
+> 亲读 server c60beebe:`/health` 已发 `restart: { reasons, version, since }`(`src/http/dispatch.ts:271`),`version` =
+> 中心配置版本(**number**,`src/config-center/restart-signal.ts:101-108`),`since` = epoch ms(**number**),对象里
+> 没有 `required`;web-admin 自审稿 §2.4 也明写「不要 `restartRequired` 布尔 + `restart` 两键 —— 布尔与在场性冗余」。
+> 照初稿做,心跳与 `/health` 由同一只 getter 铸出两种形。主会话裁:取已发 wire 形,`required` 不要。
+> ② 对抗轮(独立 opus 腿)#8:同一个配置版本,`readEffectiveWire` 收任意有限数、首版 `RestartSignal` 却要非负整数 ⇒
+> 中心一发非整数版本,整条心跳 400、实例不登记 —— 主会话裁 `version` 改 `z.number().finite()`,一个量一条判据。
+> #9:首版把 `InstanceHealth.restart` 类型化 = 宽读改严判(形不合的 `/health` 体由过变拒),照「发版纪律」字面是
+> major —— 主会话裁 **6.1.0 不做**,`InstanceHealth` 形不动,另给 `readRestartSignal`。**欠账**:`InstanceHealth.restart`
+> 上严判是 **7.0.0 项**(届时按硬 breaking 三句办:类型化、形不合即拒,消费方 tsc / parse 红即通知)。
+
+- **谁需要** = T3 心跳形(web-admin 自审稿 §2.4,[8323] ④ / [8326] ②):引擎心跳带重启信号 → 中心按策略给恰好需要
+  的 worker 打 `recreateNonce` → 编排器照旧执行。心跳成了 `/health` 之外的第二个出口,所以形只定义一次。
+- **谁受伤** = 无(新可选键 + 新导出;`InstanceHealth` 一字不动)。旧 web-admin 收到带 `restart` 的心跳:
+  `InstanceAnnouncement` 是默认 strip 的 `z.object`,该键被剥,行为同今。心跳里 `restart` 形不合 ⇒ 新 web-admin 对
+  整条心跳 400(可选子键拖整行,如实登记;server 铸点与 `/health` 同一只 getter,形由本 schema 约束)。
+- **消费方** = server(S-741 半场:`FleetClientOpts` 加 restart getter —— 与 `/health` 同一只 `restartState` —— 心跳体带
+  `restart`,翻转即刻再 announce;`/health` 零改);web-admin(`/api/fleet/instances` 收键、存、策略旋钮缺省关,[8327]
+  同波一天;存行整替不合并:不带 `restart` 的一拍 = 不再需要;若中心探针要读 `/health` 的重启信号,用 `readRestartSignal`,
+  别自己 parse `health.restart`);cli n/a;core n/a。
+- **文档句同批(主会话追加,不改类型)**:`InstanceAnnouncement.ready` 的注由「self-declared: bootDone && !draining」改为
+  「self-declared readiness: model roster landed AND not draining (server ≥7.102.0; older engines: !draining only)」——
+  server 车OE S-740 起心跳 `ready` 与 `/health` 就绪同一只谓词;旧注与 server 今天的实现(`ready = !isDraining()`)
+  和明天的实现都不符。`test/docs-hygiene.test.ts` 外部版本白名单登 server `7.102.0`(注里点名的是 server 版本,
+  不是本包)。
+- **红先**:首版 `test/restart-signal-6.1.0.test.ts` 对 6.0.0 源 **6 红 / 3 绿**(绿的三格:server 今天 `/health` 真形
+  parse 必过 —— 6.0.0 下它靠 passthrough 过,照初稿的 `required` + 字符串形它会红;不带 `restart` 照旧过的 additive 格;
+  类型面格(`expectTypeOf`,由 `tsc` 执法、运行期空跑)),首版改源后 9 / 9。二裁改写后的本文件对**首版实现**
+  **6 红 / 5 绿**(红:`readRestartSignal` 缺席四格、`InstanceHealth` 形不动格、version 有限数格),改源后 11 / 11。
+
 ## 6.0.0 — 2026-09-24 — `crossSessionInbound` 词表随 core 7.30.0 改为 `wake / next-turn / hold / refuse`,`accept` 退役(BREAKING,枚举改词;server S-616 提货同批)
 
 > **版号裁定(发布方)**:本批只有一处改动 —— `CROSS_SESSION_INBOUND_VALUES` 由 `["accept","hold","refuse"]`

package/README.md

@@ -95,6 +95,23 @@ sound). `npm ls --prod` therefore shows only `zod`. Node built-ins only (`node:c
   (`shouldForceJwksRefresh`, `jwksWithinOfflineGrace`, `classifyTimeClaims`, `toVerifiedIdentity`).
   The normative rules R1–R10 in its header are the service verifier's implementation spec.
   `VerifiedIdentity` carries an optional `scope` (the token's active tenant scope — see `api/scopes`).
+- **Center credential file** (`center-credential.ts`, main barrel; S-698): the file behind
+  `SEMA_REGISTRY_TOKEN_FILE` is one of two KINDS — a bare line (one static token — the same kind of file as today:
+  its first line, printable ASCII with no control / non-ASCII characters; user JWT vs worker pull token stays the reader's `looksLikeJwt` call) or a
+  `CenterCredentialEnvelope` (strict JSON: `kind: "user-session"` = `CENTER_CREDENTIAL_ENVELOPE_KIND`, a JWT
+  `accessToken` and a `refreshToken` under the same token law as the bare line, RFC 3339
+  `expiresAt` with seconds and a `Z` / `±hh:mm` offset in range, `issuer` = the issuing center's base URL judged
+  by the same `NON_SECRET_URL` the `remoteExec` endpoints use — same-origin is the reader's comparison).
+  `parseCenterCredentialFile(text)` is the ONE discrimination law — trimmed text starting with `{` is read ONLY
+  as an envelope (a failure is `unreadable`, never a fallback to a bare line); anything else is a bare line,
+  and a first line that is not a token is `unreadable` too (never sent as a bearer); empty is `unreadable`. The `reason` names envelope fields / zod issue codes / an unknown-key COUNT, never file
+  content. Pure: reading, atomically writing and renewing the file are the consumers' job. S-742 lifts the
+  DECLARATION face here too: `CENTER_CREDENTIAL_ENV` (`{ token: "SEMA_REGISTRY_TOKEN", tokenFile:
+  "SEMA_REGISTRY_TOKEN_FILE" }` — one spelling for the center rendering worker env, the shell writing its local
+  engine's env, and the server reading it) and `judgeCenterCredentialDeclaration(env)` → `env` / `file` /
+  `absent`, the one pick-exactly-one rule: an empty string is unset, BOTH set (non-empty) throws (the refusal
+  names the two keys, never a value), the file path comes back verbatim (resolving a relative one against a cwd
+  is the reader's job).
 - **Multi-tenant scopes** (`api/scopes.ts`, subpath `./api/scopes`): the scope contract — the `Scope`
   entity (`{id,name,createdAt}`, reserved default `"global"` always exists), per-scope `ScopeMember`
   rows (`{scopeId,principal,role}` on the existing viewer<editor<publisher<admin ladder), the optional
@@ -118,7 +135,16 @@ sound). `npm ls --prod` therefore shows only `zod`. Node built-ins only (`node:c
   tolerance on the same read path: one malformed catalog entry is dropped on its own (named through
   `onWarning` as `entry-dropped`) and its siblings survive, instead of the whole domain falling to
   its schema default. It is the SAME `DOMAIN_READ_FALLBACK` table that decides where this applies — gate
-  domains keep failing loud, entry by entry included. **3.0.0** re-casts every coordinate these warnings
+  domains keep failing loud, entry by entry included. **S-712** (additive) lets each `entry-dropped` carry an
+  optional `identity?: { name?, id?, enabled? }` read from the dropped entry's OWN text (`DroppedEntryIdentity`):
+  a string `name` / `id` and a boolean `enabled`, own data properties only, each key present only when it
+  reads with that exact type and `redactSecrets` leaves it unchanged — the SAME redactor the coordinates and the
+  error text go through (not guessed, not coerced, not masked — a masked string identifies nothing); nothing
+  readable ⇒ no `identity` key (absent = "not safely readable", whichever the reason). A consumer learns WHICH entry was
+  dropped without re-reading the source document by coordinate (the document it holds may not be the one this
+  read saw). `identity` is part of the warning projection, so the conformance gate compares it (corpus
+  case `c40` pins the two laws JSON can express; the historical normalizer strips it, since older versions cannot
+  mint it — `ConformanceNormalizer.warning?`). **3.0.0** re-casts every coordinate these warnings
   carry (`entry-dropped.path`, `unknown-keys-*.keys`) from a dot-joined STRING to a structured
   `ConfigPath = readonly (string | number)[]` — a string segment is an object key (verbatim, `.` included),
   a number segment is an array index — because the string form was a LOSSY encoding: a key literally named
@@ -141,7 +167,16 @@ sound). `npm ls --prod` therefore shows only `zod`. Node built-ins only (`node:c
   `./node`): the durable self-wake record shape + `parseSchedulerStore` / `serializeSchedulerStore`
   (forward-compatible: unknown fields survive a round-trip, malformed records are dropped one by one).
 - **Fleet contract** (`fleet.ts`, subpath `./fleet`): drain protocol, instance discovery, dispatch policy,
-  quota lease, usage report, quota-reset event.
+  quota lease, usage report, quota-reset event. **S-741** adds the restart signal, defined ONCE:
+  `RestartSignal` (`{ reasons: string[] (≥1, non-empty words), version: number (the config-center version that
+  differs from boot — finite, judged exactly as `readEffectiveWire` judges a config version), since: number (epoch
+  ms, non-negative integer) }` — exactly what the server already ships on /health). The heartbeat carries it as
+  `InstanceAnnouncement.restart?` (so `InstanceRegistration` carries it too); on /health, `InstanceHealth` is
+  UNCHANGED (passthrough — `restart` and the redundant top-level `restartRequired` ride untyped, so today's lenient
+  read stays lenient) and `readRestartSignal(health)` reads `health.restart` against the one shape (`undefined` on
+  any mismatch, never throws). Presence is the signal (present ⇔ restart required; no `required` boolean inside).
+  A heartbeat re-announces the full row, so one without `restart` means "no longer required". Typing
+  `InstanceHealth.restart` strictly is left for the next major.
 - **Declared-but-unvalidated keys** (`PARSE_TRANSPARENT_KEYS`, 2.0.0): the ONE registry of keys this package
   carries verbatim WITHOUT checking their shape, each row naming who does check it (the engine's ingest side,
   a consumer's projection, or the key's own guard). Today: `models[].extraBody`, `models[].compat` (1.10.0),

package/conformance/VERSION

@@ -1 +1 @@
-6.0.0
+6.1.0

package/conformance/cases/c01-entry-salvage-then-typo/expected.json

@@ -72,6 +72,9 @@
     "warnings": [
       {
         "domain": "models",
+        "identity": {
+          "name": "broken-no-provider"
+        },
         "kind": "entry-dropped",
         "path": [
           "models",

package/conformance/cases/c02-hosts-clamp-stacked/expected.json

@@ -74,6 +74,9 @@
       },
       {
         "domain": "hosts",
+        "identity": {
+          "name": "UPPER-BAD"
+        },
         "kind": "entry-dropped",
         "path": [
           "hosts",

package/conformance/cases/c23-mixed-validity-models/expected.json

@@ -84,6 +84,9 @@
     "warnings": [
       {
         "domain": "models",
+        "identity": {
+          "name": "bad-entry"
+        },
         "kind": "entry-dropped",
         "path": [
           "models",

package/conformance/cases/c40-s712-identity-only-what-reads-out/expected.json

@@ -0,0 +1,166 @@
+{
+  "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": {
+          "summarize": {
+            "model": "keep"
+          }
+        },
+        "tierGroups": []
+      },
+      "plugins": {
+        "plugins": []
+      },
+      "projects": {
+        "projects": {}
+      },
+      "prompts": {
+        "bindings": []
+      },
+      "rosters": {
+        "rosters": []
+      },
+      "runtime": {},
+      "scenarios": {
+        "scenarios": []
+      },
+      "skills": {
+        "skills": []
+      },
+      "systems": {
+        "systems": []
+      },
+      "workers": {
+        "workers": []
+      }
+    },
+    "warnings": [
+      {
+        "domain": "models",
+        "identity": {
+          "id": "withheld-id"
+        },
+        "kind": "entry-dropped",
+        "path": [
+          "models",
+          1
+        ]
+      },
+      {
+        "domain": "models",
+        "identity": {
+          "enabled": false,
+          "id": "off-id",
+          "name": "off-model"
+        },
+        "kind": "entry-dropped",
+        "path": [
+          "models",
+          2
+        ]
+      },
+      {
+        "domain": "models",
+        "identity": {
+          "id": "short-bearer-id"
+        },
+        "kind": "entry-dropped",
+        "path": [
+          "models",
+          3
+        ]
+      },
+      {
+        "domain": "models",
+        "identity": {
+          "id": "pem-id"
+        },
+        "kind": "entry-dropped",
+        "path": [
+          "models",
+          4
+        ]
+      },
+      {
+        "domain": "models",
+        "identity": {
+          "name": "prefixed-pem"
+        },
+        "kind": "entry-dropped",
+        "path": [
+          "models",
+          5
+        ]
+      },
+      {
+        "domain": "models",
+        "identity": {
+          "name": "glued-pem"
+        },
+        "kind": "entry-dropped",
+        "path": [
+          "models",
+          6
+        ]
+      },
+      {
+        "domain": "models",
+        "kind": "entry-dropped",
+        "path": [
+          "roles",
+          "[redacted-secret]"
+        ]
+      }
+    ],
+    "metadata": {
+      "version": 11,
+      "updatedAt": "2026-09-25T00:00:00.000Z"
+    }
+  },
+  "wire": {
+    "derive": true
+  },
+  "localRoot": {
+    "derive": true,
+    "localVersion": 527399447574205
+  }
+}

package/conformance/cases/c40-s712-identity-only-what-reads-out/input.json

@@ -0,0 +1,64 @@
+{
+  "meta": {
+    "version": 11,
+    "updatedAt": "2026-09-25T00:00:00.000Z"
+  },
+  "domains": {
+    "models": {
+      "models": [
+        {
+          "name": "keep",
+          "provider": "openai",
+          "id": "keep-id",
+          "apiKeyEnv": "OPENAI_API_KEY"
+        },
+        {
+          "name": "Authorization: Bearer FAKE-S712-CORPUS-00000000",
+          "provider": "openai",
+          "id": "withheld-id",
+          "enabled": "yes",
+          "apiKeyEnv": "not an env name"
+        },
+        {
+          "name": "off-model",
+          "provider": "openai",
+          "id": "off-id",
+          "enabled": false,
+          "apiKeyEnv": "not an env name"
+        },
+        {
+          "name": "tok=Bearer abc1234",
+          "provider": "openai",
+          "id": "short-bearer-id",
+          "apiKeyEnv": "not an env name"
+        },
+        {
+          "name": "-----BEGIN RSA PRIVATE KEY-----\nMIIEFAKES712CORPUSPEMBODY0000\n-----END RSA PRIVATE KEY-----",
+          "provider": "openai",
+          "id": "pem-id",
+          "apiKeyEnv": "not an env name"
+        },
+        {
+          "name": "prefixed-pem",
+          "provider": "openai",
+          "id": "key: -----BEGIN OPENSSH PRIVATE KEY-----\nMIIEFAKES712CODEXPREFIXED0000\n-----END OPENSSH PRIVATE KEY-----",
+          "apiKeyEnv": "not an env name"
+        },
+        {
+          "name": "glued-pem",
+          "provider": "openai",
+          "id": "sk-note:-----BEGIN PRIVATE KEY-----\nMC4CAQAwBQYDK2VwFAKES712GLUEDCORPUS0000000000\n-----END PRIVATE KEY-----",
+          "apiKeyEnv": "not an env name"
+        }
+      ],
+      "roles": {
+        "summarize": {
+          "model": "keep"
+        },
+        "sk-note:-----BEGIN PRIVATE KEY-----\nMC4CAQAwBQYDK2VwFAKES712GLUEDCORPUS0000000000\n-----END PRIVATE KEY-----": {
+          "model": "keep"
+        }
+      }
+    }
+  }
+}

package/conformance/cases/c40-s712-identity-only-what-reads-out/meta.json

@@ -0,0 +1,13 @@
+{
+  "contributor": "contract",
+  "claim": "S-712 身份律的两道闸压在语料上:被丢条目的 name 是一段脱敏器会改动的串(Bearer 形)⇒ identity 不带 name(同一条告警里坐标会打码,身份不许把原文带出去);enabled 是字符串 \"yes\" ⇒ 不带 enabled;id 是干净字符串 ⇒ 照带。另两条被丢条目压脱敏判据的两道边:`tok=Bearer abc1234`(短令牌,探测器 containsSecretToken 不判阳、脱敏器会改)与一整段 PEM 私钥(头里带空格,脱敏器的定点两遍够不着、靠整串兜底)⇒ 两条的 name 都不带。正控:另一条被丢条目 name / id / enabled:false 三键齐全逐字带出。读腿若放宽任一闸,告警面多出字段即红;秘密清单同时由告警面零命中门看着。",
+  "firstRedOn": [],
+  "secrets": [
+    "FAKE-S712-CORPUS-00000000",
+    "abc1234",
+    "MIIEFAKES712CORPUSPEMBODY0000",
+    "MIIEFAKES712CODEXPREFIXED0000",
+    "MC4CAQAwBQYDK2VwFAKES712GLUEDCORPUS0000000000"
+  ],
+  "note": "对抗轮 #5(车OD 2026-09-25):变异门 `test/conformance-mutation.test.ts` 为 readEntryIdentity 登记两靶(`redactSecrets(v) === v` → `true`、`typeof enabled === \"boolean\"` → `enabled !== void 0`),加本条之前两靶变异体全绿(语料缺口),加本条之后两靶各红。第三条律(只认数据属性、不触发访问器)JSON 表达不出 getter,不在本条射程内,由单测看着。firstRedOn 为空:旧版铸不出 identity,historical 归一器两侧剥掉 identity,本条在旧版上不计行为红 —— 它是护栏,不是真门。 验修轮 N4 / N1(车OD 2026-09-25):加入短令牌与 PEM 两条 —— 身份判据退回旧的 containsSecretToken 时短令牌那条带出 name ⇒ 本条红;redactSecrets 去掉整串兜底时 PEM 那条带出 name ⇒ 本条红。 codex 一审 [high](2026-09-25):再加一条 `id` = 带 `key: ` 前缀的 PEM 私钥(header 不在串首,探测器看不见)⇒ 身份只剩 name;redactSecrets 去掉「串内任意位置 PEM header」一道时本条红。 codex 验修轮 [high](2026-09-25):再加 `sk-note:` 紧贴私钥 PEM header 的串,既作被丢条目的 `id`(身份面)又作 `roles` 的坏键(坐标面 + zod error 面);redactSecrets 把 PEM 检查挪回替换之后时本条红(令牌那一遍先把 `sk-note:-----BEGIN` 换掉)。"
+}

package/conformance/cases/cli01-model-name-nfc-vs-nfd/expected.json

@@ -72,6 +72,10 @@
     "warnings": [
       {
         "domain": "models",
+        "identity": {
+          "id": "café-id",
+          "name": "café"
+        },
         "kind": "entry-dropped",
         "path": [
           "models",
@@ -80,6 +84,10 @@
       },
       {
         "domain": "models",
+        "identity": {
+          "id": "café-id",
+          "name": "café"
+        },
         "kind": "entry-dropped",
         "path": [
           "models",

package/conformance/cases/cli02-control-and-zero-width-chars/expected.json

@@ -85,6 +85,10 @@
     "warnings": [
       {
         "domain": "models",
+        "identity": {
+          "id": "a\u0007b-id",
+          "name": "a\u0007b"
+        },
         "kind": "entry-dropped",
         "path": [
           "models",
@@ -93,6 +97,10 @@
       },
       {
         "domain": "models",
+        "identity": {
+          "id": "zero​width-id",
+          "name": "zero​width"
+        },
         "kind": "entry-dropped",
         "path": [
           "models",

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

@@ -72,6 +72,10 @@
     "warnings": [
       {
         "domain": "models",
+        "identity": {
+          "id": "bad-id",
+          "name": "bad"
+        },
         "kind": "entry-dropped",
         "path": [
           "models",

package/dist/api/auth-bridge.d.ts

@@ -266,13 +266,13 @@ export declare const VerifiedIdentity: z.ZodObject<{
 }, "strip", z.ZodTypeAny, {
     principal: string;
     role?: string | undefined;
-    scope?: string | undefined;
     grantId?: string | undefined;
+    scope?: string | undefined;
 }, {
     principal: string;
     role?: string | undefined;
-    scope?: string | undefined;
     grantId?: string | undefined;
+    scope?: string | undefined;
 }>;
 export type VerifiedIdentity = z.infer<typeof VerifiedIdentity>;
 /** The verifier's total result — exactly one of ok/error. */