@sema-agent/settings-schema 11.2.0 → 12.0.0

package/dist/one-time-migrations.js

@@ -12,8 +12,8 @@
  * 同一串字节换意思的改动一律**换表示**(SS-M6 因此是「`atModelAllowlist` → `atMention`」换字段,而不是翻 `[]` 的义)。
  *
  * ## 入口(纯函数:不读环境、不读墙钟、不改入参、**不抬任何版本号**)
- *  · {@link migrateStoredDocuments} —— 一组**存储文档**(域名 → 文档)。一个 scope 的全部草稿、一个 principal 层(个人 models / mcp /
- *    skills / plugins)、回滚史里的一条单域行,各调一次;`coverage` 说这组文档是不是一个 scope 的全集(只有 SS-M1 要知道:缺席的
+ *  · {@link migrateStoredDocuments} —— 一组**存储文档**(域名 → 文档;还有本机的 `remote-exec` —— `config.d/remote-exec.json`,
+ *    只有 SS-M7 的座位走查读它)。一个 scope 的全部草稿、一个 principal 层(个人 models / mcp / skills / plugins)、回滚史里的一条单域行,各调一次;`coverage` 说这组文档是不是一个 scope 的全集(只有 SS-M1 要知道:缺席的
  *    `governance` 是「从未设过」还是「没给」)。缺的域 = 不动。
  *  · {@link migrateEffectiveSnapshot} —— 一份**冻结的 effective**(发布快照、回滚历史里的整份快照、引擎的 last-known-good 文件)。改写规则
  *    与草稿同(零语义变 ⇒ 不越过发布审批:改的是表示,不是已批准的内容);不从草稿重建;`version` / `updatedAt` 与其余信封键原样。
@@ -34,6 +34,8 @@ import { LANE_ENV_OWNER, STORE_ENV_KEYS, isLaneEnvKey } from "./execution-lane-i
 import { EXECUTION_LANE_WORDS, MEMORY_ENGINE_BACKENDS, STORE_BACKENDS } from "./execution-lanes.js";
 import { INTEGER } from "./integer.js";
 import { RUNTIME_LIFT_TARGETS } from "./runtime-lift-targets.js";
+import { RETIRED_ROLE_WORDS } from "./retired-role-words.js";
+import { REMOTE_EXEC_DOCUMENT, RemoteExecSpec } from "./remote-exec.js";
 import { DOMAIN_SCHEMAS, HOSTS_ARRAY_MAX, HOST_NAME_MAX, NON_SECRET_URL, isDomainName, isRetiredDomainName } from "./types.js";
 import { workerRowVerdict } from "./worker-row-verdict.js";
 import { unwrapSchema } from "./zod-unwrap.js";
@@ -128,10 +130,24 @@ export const ONE_TIME_MIGRATIONS = [
         removableAfter: "2026-11-09",
         rewrites: "every NON_SECRET_URL seat in a domain document (derived from the domain schemas, not listed by hand — today models.models[].baseUrl, " +
             "mcp.servers[].transport.url, execution.sessionMirror.engineUrl, workers.workers[].coords.gitApiBaseUrl): `#` and everything after it are removed " +
-            "(a fragment never goes on the wire)",
+            "(a fragment never goes on the wire); the same walk covers config.d/remote-exec.json, derived from its schema the same way " +
+            "(today the k8s apiUrl and s3Snapshot.endpoint) — the command-line migrate reads and rewrites it as one more document",
         removal: "the next major after the window: delete the SS-M7 step and its schema walk; the NON_SECRET_URL fragment rule loses its SS-M7 clause",
         afterRemoval: "the NON_SECRET_URL shape judge, which refuses a fragment (`#` included) on read and write",
     },
+    {
+        id: "SS-M8",
+        oldForm: "refused",
+        introducedIn: "12.0.0",
+        releasedOn: "2026-10-12",
+        removableAfter: "2026-11-11",
+        rewrites: "models / rosters: role words removed by core 7.49.0: team, synthesize — the keys roles.team / roles.synthesize (models.roles and every " +
+            "rosters[].roles) are removed whatever their value (12.0.0 drops both words from ModelRole: no role reads them, and the engine refuses " +
+            "them); every other role and key stays as stored",
+        removal: "the next major after the window: delete the SS-M8 step; the retired role-word tombstone stays — its SS-M8 clause goes",
+        afterRemoval: "the retired role-word tombstone (permanent): a residual roles.team / roles.synthesize is refused on read and write (read: the entry is dropped " +
+            "when other roles survive, else models degrades to its default; rosters: the scope fails to read)",
+    },
     {
         id: "SS-M9",
         oldForm: "refused",
@@ -187,6 +203,7 @@ export function migrateStoredDocuments(docs, opts) {
     stepHostsBounds(out, receipts);
     stepModelKeyOneOf(out, receipts);
     stepAtMention(out, receipts);
+    stepRetiredRoleWords(out, receipts);
     stepModelsDefault(out, receipts);
     stepUrlFragments(out, receipts);
     stepWorkers6x(out, receipts);
@@ -673,6 +690,45 @@ function stepAtMention(out, receipts) {
             out.rosters = { ...rosters, rosters: next };
     }
 }
+// ── SS-M8:退役的角色词 ────────────────────────────────────────────────────────────────────────────────
+/** 一个 `roles` 图上的退役角色词键删掉(值不论 —— 没有角色读它);逐键一张 `dropped-inert` 收据。返回改后的图或 `undefined`(没改 / 不是对象:判形是读者的事)。 */
+function withoutRetiredRoles(roles, document, at, receipts) {
+    if (!isPlainObject(roles))
+        return undefined;
+    const present = RETIRED_ROLE_WORDS.filter((w) => Object.prototype.hasOwnProperty.call(roles, w));
+    if (present.length === 0)
+        return undefined;
+    let next = roles;
+    for (const w of present) {
+        next = without(next, w);
+        receipts.push(receipt("SS-M8", document, [...at, "roles", w], "dropped-inert"));
+    }
+    return next;
+}
+function stepRetiredRoleWords(out, receipts) {
+    const models = out.models;
+    if (isPlainObject(models)) {
+        const roles = withoutRetiredRoles(models.roles, "models", [], receipts);
+        if (roles !== undefined)
+            out.models = { ...models, roles };
+    }
+    const rosters = out.rosters;
+    if (isPlainObject(rosters) && Array.isArray(rosters.rosters)) {
+        const rows = rosters.rosters;
+        let next;
+        rows.forEach((row, index) => {
+            if (!isPlainObject(row))
+                return;
+            const roles = withoutRetiredRoles(row.roles, "rosters", ["rosters", index], receipts);
+            if (roles === undefined)
+                return;
+            next ??= [...rows];
+            next[index] = { ...row, roles };
+        });
+        if (next !== undefined)
+            out.rosters = { ...rosters, rosters: next };
+    }
+}
 // ── SS-M9:models.default → roles.default ──────────────────────────────────────────────────────────────
 /** 迁移前「缺省模型是谁」的生效读法 = server 的缺省解析以结构键 `default` 为第一级,主任务真跑它(N-7 两答复现:`default` = A、`roles.default`
  *  = B 时主任务跑 A,core 的 `default` 角色解到 B)。所以并过去的是 `default` 的值:`roles.default` 缺席 ⇒ 搬入;同名 ⇒ 搬入(重复的那一份
@@ -694,6 +750,14 @@ function stepModelsDefault(out, receipts) {
     out.models = { ...without(doc, "default"), roles: { ...roles, default: { model: name } } };
 }
 // ── SS-M7:URL fragment ────────────────────────────────────────────────────────────────────────────────
+/** SS-M7 走查的文档 → 它的 schema(座位从 schema 派生的那一只来源):配置域按 `DOMAIN_SCHEMAS`,`remote-exec` 按 `RemoteExecSpec`;别的文档没有 URL 座位。 */
+function urlSeatSchemaOf(document) {
+    if (isDomainName(document))
+        return DOMAIN_SCHEMAS[document];
+    if (document === REMOTE_EXEC_DOCUMENT)
+        return RemoteExecSpec;
+    return undefined;
+}
 /** 这只(已展开的)schema 是不是一个 `NON_SECRET_URL` 座位:就是它,或是「先归一、再交给它」的管道(`z.string().trim().pipe(NON_SECRET_URL)`)。 */
 function isUrlSeat(s) {
     return s === NON_SECRET_URL || (s instanceof z.ZodPipe && unwrapSchema(s.out) === NON_SECRET_URL);
@@ -775,7 +839,8 @@ function stripFragments(schema, value, path, onStrip, depth = 0) {
     }
     return value;
 }
-/** 本包域 schema 里全部 URL 座位的坐标模式(派生;数组 / Record 位写 `*`)—— 迁移不用它,它给钉与说明看「今天派生出哪些座位」。 */
+/** SS-M7 走查的全部 URL 座位的坐标模式(派生;数组 / Record 位写 `*`;域文档以域名起头,`remote-exec.json` 以 `remote-exec` 起头)—— 迁移不用它,
+ *  它给钉与说明看「今天派生出哪些座位」。 */
 export function urlSeatPatterns() {
     const out = [];
     const walk = (schema, path, depth) => {
@@ -813,16 +878,18 @@ export function urlSeatPatterns() {
     };
     for (const [d, schema] of Object.entries(DOMAIN_SCHEMAS))
         walk(schema, [d], 0);
+    walk(RemoteExecSpec, [REMOTE_EXEC_DOCUMENT], 0);
     return out;
 }
 function stepUrlFragments(out, receipts) {
     for (const d of Object.keys(out)) {
-        if (!isDomainName(d))
+        const schema = urlSeatSchemaOf(d);
+        if (schema === undefined)
             continue;
         const doc = out[d];
         if (doc === undefined)
             continue;
-        const next = stripFragments(DOMAIN_SCHEMAS[d], doc, [], (path) => receipts.push(receipt("SS-M7", d, path, "rewritten")));
+        const next = stripFragments(schema, doc, [], (path) => receipts.push(receipt("SS-M7", d, path, "rewritten")));
         if (next !== doc)
             out[d] = next;
     }

package/dist/quoted-issue.d.ts

@@ -0,0 +1,41 @@
+/**
+ * 包内私有叶子模块(运行期零依赖,浏览器安全):**custom issue 的唯一铸点**(全包一只;11.0.0 时它住在 `./types` 里、只管那一个文件)。
+ *
+ * 律(一条):本包 schema 自己铸的每一条 custom issue —— `ctx.addIssue({ code: "custom", … })`、`.refine(判据, …)`、引用完整性的 `RefIssue`
+ * —— 都带 {@link QuotedIssueParams}(句子的固定词 `template` 与值 `operands`,值位是洞),`message` 恒是 {@link renderQuotedSentence} 从它渲出的,
+ * 铸点不手写第二遍。读者因此对 custom issue 只有一种读法:读结构化的句子(日志边界逐值打指纹、诊断面把值换成洞),不在「带 params 的读 params、
+ * 不带的退回 message」之间分流。没有值的定句一样走这里(`operands` 为空)。源码门在测试 custom-issue-params(扫 `src/` 全部铸点)。
+ *
+ * 不在本律里的(如实):zod 内建码的 issue —— `.max(n, 句)` / `.regex(re, 句)` 的 `too_big` / `invalid_format`、墓碑字段 `z.never` 的 `invalid_type`、
+ * 联合的错误映射 —— 它们的码不是 `custom`,`params` 不是 zod 给它们的槽位;它们的句子是定句(不插配置里的值),读者读 `message`。
+ */
+/** The params of a custom issue whose sentence QUOTES values (S-1075, 11.0.0) —— plain data: the sentence's fixed parts and the
+ *  values between them, in order, so `message` is exactly {@link renderQuotedSentence} of them. A reader that has to treat the
+ *  user-written parts of a sentence differently from its fixed words (a log boundary fingerprinting each value, the sanitizer
+ *  bounding each value's length) reads them HERE instead of guessing where a value starts in the sentence. Every custom issue this
+ *  package raises carries them (the fixed sentences too — those carry no operands). */
+export interface QuotedIssueParams {
+    readonly template: readonly string[];
+    readonly operands: readonly (string | number)[];
+}
+/** The one rendering of a quoted sentence: `template[0] + show(operands[0]) + template[1] + … + template[n]`. `show` defaults to
+ *  the value as written (that is how `message` is minted); a sanitizer / log boundary passes its own. */
+export declare function renderQuotedSentence(p: QuotedIssueParams, show?: (operand: string | number) => string): string;
+/** A custom issue's quoted sentence and its params (what {@link buildQuotedIssue} mints; spread into `ctx.addIssue`, or passed as a
+ *  `.refine` second argument). */
+export type QuotedIssue = {
+    readonly message: string;
+    readonly params: QuotedIssueParams;
+};
+/** Fixed sentence text spliced into a quoted sentence (a migration signpost, a closed vocabulary listed as the way out, a field
+ *  name): it joins the template, it is NOT an operand —— operands are the values the config holds, the only parts a log boundary
+ *  fingerprints and the sanitizer bounds (S-815). */
+export interface FixedText {
+    readonly fixedText: string;
+}
+export declare const fixed: (text: string) => FixedText;
+/** Mint a custom issue's `message` + `params` from a tagged template (`buildQuotedIssue\`duplicate model "${name}"\``): every
+ *  interpolation is an operand unless wrapped in {@link fixed} (then it is template text). THE minting point of custom issues in this
+ *  package — a sentence written straight into `message` would put a value into a sentence with no record of where it is, and give
+ *  readers a second way to read an issue. */
+export declare function buildQuotedIssue(strings: TemplateStringsArray, ...parts: (string | number | FixedText)[]): QuotedIssue;

package/dist/quoted-issue.js

@@ -0,0 +1,35 @@
+/**
+ * 包内私有叶子模块(运行期零依赖,浏览器安全):**custom issue 的唯一铸点**(全包一只;11.0.0 时它住在 `./types` 里、只管那一个文件)。
+ *
+ * 律(一条):本包 schema 自己铸的每一条 custom issue —— `ctx.addIssue({ code: "custom", … })`、`.refine(判据, …)`、引用完整性的 `RefIssue`
+ * —— 都带 {@link QuotedIssueParams}(句子的固定词 `template` 与值 `operands`,值位是洞),`message` 恒是 {@link renderQuotedSentence} 从它渲出的,
+ * 铸点不手写第二遍。读者因此对 custom issue 只有一种读法:读结构化的句子(日志边界逐值打指纹、诊断面把值换成洞),不在「带 params 的读 params、
+ * 不带的退回 message」之间分流。没有值的定句一样走这里(`operands` 为空)。源码门在测试 custom-issue-params(扫 `src/` 全部铸点)。
+ *
+ * 不在本律里的(如实):zod 内建码的 issue —— `.max(n, 句)` / `.regex(re, 句)` 的 `too_big` / `invalid_format`、墓碑字段 `z.never` 的 `invalid_type`、
+ * 联合的错误映射 —— 它们的码不是 `custom`,`params` 不是 zod 给它们的槽位;它们的句子是定句(不插配置里的值),读者读 `message`。
+ */
+/** The one rendering of a quoted sentence: `template[0] + show(operands[0]) + template[1] + … + template[n]`. `show` defaults to
+ *  the value as written (that is how `message` is minted); a sanitizer / log boundary passes its own. */
+export function renderQuotedSentence(p, show = String) {
+    return p.template.reduce((out, part, i) => (i === 0 ? part : `${out}${show(p.operands[i - 1])}${part}`), "");
+}
+export const fixed = (text) => ({ fixedText: text });
+/** Mint a custom issue's `message` + `params` from a tagged template (`buildQuotedIssue\`duplicate model "${name}"\``): every
+ *  interpolation is an operand unless wrapped in {@link fixed} (then it is template text). THE minting point of custom issues in this
+ *  package — a sentence written straight into `message` would put a value into a sentence with no record of where it is, and give
+ *  readers a second way to read an issue. */
+export function buildQuotedIssue(strings, ...parts) {
+    const template = [strings[0]];
+    const operands = [];
+    parts.forEach((part, i) => {
+        if (typeof part === "object")
+            template[template.length - 1] += part.fixedText + strings[i + 1];
+        else {
+            operands.push(part);
+            template.push(strings[i + 1]);
+        }
+    });
+    const params = { template, operands };
+    return { message: renderQuotedSentence(params), params };
+}

package/dist/remote-exec.d.ts

@@ -27,6 +27,9 @@
  * ONLY; the service owns the adapter implementations.
  */
 import { z } from "zod";
+/** The name of this contract's document in a `config.d` directory (`config.d/remote-exec.json`) —— the one spelling: the local reader /
+ *  writer, the directory migration and the command line name the document by it. It is not a config domain (not in `DOMAIN_SCHEMAS`). */
+export declare const REMOTE_EXEC_DOCUMENT: "remote-exec";
 export declare const RemoteExecSpec: z.ZodDiscriminatedUnion<[z.ZodObject<{
     provider: z.ZodLiteral<"host">;
     workdir: z.ZodOptional<z.ZodString>;

package/dist/remote-exec.js

@@ -28,11 +28,15 @@
  */
 import { z } from "zod";
 import { INTEGER } from "./integer.js";
-import { ENV_NAME, K8S_QUANTITY, NON_SECRET_URL_NO_MIGRATION, TCP_PORT, containsSecretToken, hasNul } from "./types.js";
+import { buildQuotedIssue } from "./quoted-issue.js";
+import { ENV_NAME, K8S_QUANTITY, NON_SECRET_URL, TCP_PORT, containsSecretToken, hasNul } from "./types.js";
 import { retiredLaneWordRefusal } from "./execution-lanes.js";
+/** The name of this contract's document in a `config.d` directory (`config.d/remote-exec.json`) —— the one spelling: the local reader /
+ *  writer, the directory migration and the command line name the document by it. It is not a config domain (not in `DOMAIN_SCHEMAS`). */
+export const REMOTE_EXEC_DOCUMENT = "remote-exec";
 /** A non-empty exec-bound string (an image / path / shell / arg the adapter feeds to spawn()/fs). Rejects a NUL
  *  byte uniformly — a NUL validates here but makes Node throw at spawn/boot (fail-OPEN → runtime crash). R20. */
-const execStr = z.string().min(1).refine((s) => !hasNul(s), "must not contain a NUL byte");
+const execStr = z.string().min(1).refine((s) => !hasNul(s), buildQuotedIssue `must not contain a NUL byte`);
 /** Container knobs of the `local-docker` lane. `network` defaults to `none` at the adapter (the safe posture for
  *  untrusted code — see the dual-mode design note). */
 const DOCKER_FIELDS = {
@@ -83,8 +87,9 @@ export const RemoteExecSpec = z.discriminatedUnion("provider", [
         provider: z.literal("k8s"),
         /** Sandbox container image (service: K8S_SANDBOX_IMAGE). Required so a run is reproducible. */
         image: execStr,
-        /** Kube API URL (service: K8S_API_URL); absent → in-cluster service account. NO embedded credentials. */
-        apiUrl: NON_SECRET_URL_NO_MIGRATION.optional(),
+        /** Kube API URL (service: K8S_API_URL); absent → in-cluster service account. NO embedded credentials. A stored fragment is rewritten
+         *  by the one-time migration SS-M7 (this file is one of its documents), so the refusal names it. */
+        apiUrl: NON_SECRET_URL.optional(),
         /** env-NAME holding the kube bearer token (service: K8S_TOKEN). NEVER the token. */
         tokenEnv: ENV_NAME.optional(),
         /** env-NAME holding the base64 CA cert (service: K8S_CA_CERT_B64). NEVER the cert bytes. */
@@ -102,7 +107,7 @@ export const RemoteExecSpec = z.discriminatedUnion("provider", [
          *  "all three of endpoint/access/secret required" gate). */
         s3Snapshot: z
             .object({
-            endpoint: NON_SECRET_URL_NO_MIGRATION, // S3/MinIO endpoint — creds go in accessKeyEnv/secretKeyEnv, never the URL
+            endpoint: NON_SECRET_URL, // S3/MinIO endpoint — creds go in accessKeyEnv/secretKeyEnv, never the URL (a stored fragment: SS-M7, like apiUrl)
             bucket: execStr.optional(),
             accessKeyEnv: ENV_NAME,
             secretKeyEnv: ENV_NAME,
@@ -117,9 +122,9 @@ export const RemoteExecSpec = z.discriminatedUnion("provider", [
         provider: z.literal("ssh"),
         // host + username are persisted to config.d/remote-exec.json — scan for a secret-shaped literal (a secret must go
         // in privateKeyEnv, not the login). R14.
-        host: execStr.refine((s) => !containsSecretToken(s), "no secret literal in ssh host — credentials go in privateKeyEnv"),
+        host: execStr.refine((s) => !containsSecretToken(s), buildQuotedIssue `no secret literal in ssh host — credentials go in privateKeyEnv`),
         port: TCP_PORT.optional(),
-        username: execStr.refine((s) => !containsSecretToken(s), "no secret literal in ssh username — credentials go in privateKeyEnv"),
+        username: execStr.refine((s) => !containsSecretToken(s), buildQuotedIssue `no secret literal in ssh username — credentials go in privateKeyEnv`),
         /** env-NAME holding the SSH private key (service: SSH_PRIVATE_KEY). NEVER the key value. */
         privateKeyEnv: ENV_NAME,
         mountPath: execStr.optional(),

package/dist/resolve-roster.d.ts

@@ -13,7 +13,7 @@
 import type { AtMention, EffectiveConfig, EffectiveWire, ModelRole, RoleTarget, RosterEntry } from "./types.js";
 import { type RefIssue } from "./cross-domain.js";
 /** primaryModel 标记喂的角色族(§3)。 */
-export declare const ROSTER_PRIMARY_ROLES: readonly ["default", "team", "synthesize"];
+export declare const ROSTER_PRIMARY_ROLES: readonly ["default"];
 /** cheapModel 标记喂的角色族(§3)。 */
 export declare const ROSTER_CHEAP_ROLES: readonly ["subagent", "summarize"];
 /** 把 roster 的主/cheap 角色标记派生成 roles 片段(PURE)。显式 roster.roles 逐角色盖过它;它盖过全局

package/dist/resolve-roster.js

@@ -2,12 +2,12 @@ import { stableHash } from "./hash.js";
 import { danglingRefs } from "./cross-domain.js";
 import { toSkillsManifest } from "./skills-manifest.js";
 // ── 主/cheap 角色标记语义(0.6.3, E3)────────────────────────────────
-// service 现有 ModelRoles 口径:default/team/synthesize→主、subagent/summarize→cheap。1.8.0 起 `classifier`/`consolidate`
+// service 现有 ModelRoles 口径:default→主(12.0.0 起唯一;`team` / `synthesize` 随 core 7.49.0 删)、subagent/summarize→cheap。1.8.0 起 `classifier`/`consolidate`
 // 同 `verifier` 一样**不派生**(归 cheap 会盖掉 models.tiers 档位与 core 兜底链)。`verifier` 刻意
 // 不派生(unset→core 的 default 兜底链,与 service 语义一致)。常量导出=单一语义源,service 收敛小单与
 // web-admin 表单同源引用,别第二份。
 /** primaryModel 标记喂的角色族(§3)。 */
-export const ROSTER_PRIMARY_ROLES = ["default", "team", "synthesize"];
+export const ROSTER_PRIMARY_ROLES = ["default"];
 /** cheapModel 标记喂的角色族(§3)。 */
 export const ROSTER_CHEAP_ROLES = ["subagent", "summarize"];
 /** 把 roster 的主/cheap 角色标记派生成 roles 片段(PURE)。显式 roster.roles 逐角色盖过它;它盖过全局
@@ -86,7 +86,7 @@ export function resolveEffectiveForWorker(eff, worker) {
     // `{select}`-form (capability-based) roles name no model → kept.
     // Per-role merge (roster overrides global PER ROLE) — NOT a whole-map replace. The types promise "unset
     // roster roles fall back to global models.roles per role"; a whole-map `??` silently dropped the global
-    // `subagent`/`team`/… when a roster set only `default`. Round-3 fix. Then drop any dangling {model}.
+    // `subagent`/`summarize`/… when a roster set only `default`. Round-3 fix. Then drop any dangling {model}.
     // 0.6.3: marker-derived roles (primaryModel/cheapModel semantics) sit BETWEEN global and explicit
     // roster.roles — global < markers < explicit per-role. Markers are subset-validated at PUT; a stale marker
     // after a catalog change still falls through the dangling-{model} drop below (defence-in-depth).

package/dist/retired-role-words.d.ts

@@ -0,0 +1,5 @@
+/** 退役的角色词(闭集;逐字)。 */
+export declare const RETIRED_ROLE_WORDS: readonly ["team", "synthesize"];
+/** 一组被判官拒下的角色键 / 角色词里若有退役词 ⇒ 那一句(点名退役词与 SS-M8;同组里别的不认识的词也点名,一个不漏);没有 ⇒ `undefined`
+ *  (交回 zod 自己的句子)。`ModelRole` 的判句(一个词)与 `roles` 图的未知键判句(一组键)都调这一只。 */
+export declare function retiredRoleWordsRefusal(words: readonly unknown[]): string | undefined;

package/dist/retired-role-words.js

@@ -0,0 +1,25 @@
+/**
+ * 包内私有(不进主桶、不进 exports 表):12.0.0 退役的**角色词**墓碑 —— 引擎 core 7.49.0 把 `team` / `synthesize` 从角色表里删了(对未知角色词响亮拒),
+ * 本包的 `ModelRole` 随之收成 6 词。墓碑是**拒**,不是第二种读法:判官遇到这两个词不把它们读成任何角色,只说「这是一份没迁的旧形」以及去哪儿迁
+ * (一次性迁移 SS-M8,`./one-time-migrations`)。一处写词、一处写句:`ModelRole` 的判句、`roles` 图的未知键判句与 SS-M8 的改写步都读这里。
+ * 迁移族按登记表的窗整族删,墓碑留下 —— 到那时句子里的迁移指路由删码那一车去掉(登记表 SS-M8 行的 `removal`)。
+ */
+import { retiredFormSentence } from "./retired-form.js";
+/** 退役的角色词(闭集;逐字)。 */
+export const RETIRED_ROLE_WORDS = ["team", "synthesize"];
+const ROLE_WORDS_RETIRED = {
+    retiredIn: "12.0.0",
+    now: "no role reads it (core 7.49.0 removed the role and refuses the word)",
+    migration: "SS-M8",
+};
+const isRetiredRoleWord = (w) => RETIRED_ROLE_WORDS.some((r) => r === w);
+/** 一组被判官拒下的角色键 / 角色词里若有退役词 ⇒ 那一句(点名退役词与 SS-M8;同组里别的不认识的词也点名,一个不漏);没有 ⇒ `undefined`
+ *  (交回 zod 自己的句子)。`ModelRole` 的判句(一个词)与 `roles` 图的未知键判句(一组键)都调这一只。 */
+export function retiredRoleWordsRefusal(words) {
+    const retired = RETIRED_ROLE_WORDS.filter((r) => words.includes(r));
+    if (retired.length === 0)
+        return undefined;
+    const others = words.filter((w) => !isRetiredRoleWord(w)).map((w) => JSON.stringify(String(w)));
+    const head = others.length === 0 ? "" : `unrecognized role ${others.length === 1 ? "word" : "words"} ${others.join(", ")}; `;
+    return head + retiredFormSentence(`role word ${retired.join(" / ")}`, ROLE_WORDS_RETIRED);
+}

package/dist/rfc3339.d.ts

@@ -0,0 +1,10 @@
+/**
+ * 包内私有叶子模块:**一只** RFC 3339 时刻判(从 `./web-admin-credential` 搬出 —— 凭证信封的 `expiresAt` 与项目登记的 `archivedAt` 读同一只,
+ * 不各写一份)。
+ */
+import { z } from "zod";
+/** RFC 3339 `date-time` 的**剖面**:zod 的 `z.iso.datetime({offset:true})` 管日历有效性(月日范围、闰年、时分秒范围),
+ *  这里的正则自己判另三处 —— 秒必备、数字偏移必须是 `±hh:mm`、偏移的时 00–23 / 分 00–59(`10:00Z`、`+0800` 与 `+99:99`
+ *  都不是 RFC 3339,后者 `Date.parse` 读成 NaN)。这三处的判据在本正则,不随 zod 哪一版收不收而变。大写 `T` / `Z`、不收闰秒 `:60`:读方普遍用
+ *  `Date.parse` 取时刻,这是那组形里它处处读得准的子集。 */
+export declare const RFC3339_DATE_TIME: z.ZodISODateTime;

package/dist/rfc3339.js

@@ -0,0 +1,12 @@
+/**
+ * 包内私有叶子模块:**一只** RFC 3339 时刻判(从 `./web-admin-credential` 搬出 —— 凭证信封的 `expiresAt` 与项目登记的 `archivedAt` 读同一只,
+ * 不各写一份)。
+ */
+import { z } from "zod";
+/** RFC 3339 `date-time` 的**剖面**:zod 的 `z.iso.datetime({offset:true})` 管日历有效性(月日范围、闰年、时分秒范围),
+ *  这里的正则自己判另三处 —— 秒必备、数字偏移必须是 `±hh:mm`、偏移的时 00–23 / 分 00–59(`10:00Z`、`+0800` 与 `+99:99`
+ *  都不是 RFC 3339,后者 `Date.parse` 读成 NaN)。这三处的判据在本正则,不随 zod 哪一版收不收而变。大写 `T` / `Z`、不收闰秒 `:60`:读方普遍用
+ *  `Date.parse` 取时刻,这是那组形里它处处读得准的子集。 */
+export const RFC3339_DATE_TIME = z.iso
+    .datetime({ offset: true })
+    .regex(/T\d{2}:\d{2}:\d{2}(?:\.\d+)?(?:Z|[+-](?:[01]\d|2[0-3]):[0-5]\d)$/, "must be an RFC 3339 date-time: seconds and a Z / ±hh:mm offset (hh 00-23, mm 00-59) are required");

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

@@ -53,8 +53,8 @@
 import { z } from "zod";
 /** How values from different layers/principals combine for a category. */
 export declare const MergeShape: z.ZodEnum<{
-    concat: "concat";
     replace: "replace";
+    concat: "concat";
     denyFirst: "denyFirst";
     runAll: "runAll";
     overrideByName: "overrideByName";
@@ -185,8 +185,8 @@ export declare const TightenRule: z.ZodDiscriminatedUnion<[z.ZodObject<{
 export type TightenRule = z.infer<typeof TightenRule>;
 export declare const MergeCategorySpec: z.ZodObject<{
     mergeShape: z.ZodEnum<{
-        concat: "concat";
         replace: "replace";
+        concat: "concat";
         denyFirst: "denyFirst";
         runAll: "runAll";
         overrideByName: "overrideByName";