@sema-agent/settings-schema 1.7.1 → 1.7.2

package/CHANGELOG.md

@@ -6,6 +6,15 @@
 > `@sema-agent/registry-core`(更早还曾是 `@sema-ai/registry-core`)。本档 `0.19.0` 以下各节里的
 > 包名是**历史记录**,如实保留不追改。
 
+## 1.7.2 — 2026-09-06 — `source` 改**解析透明**(`z.unknown()`;patch)
+
+- 1.7.1 的 `z.string()` 对 `source: null`(或数字/数组/对象)仍在解析处拒 ⇒ 整域 all-or-nothing 下**一个**非串标签让整套
+  `mcp.servers` 默认为空——而 1.6.0 之前该键被 default-strip 剥掉、无害,故这是 1.7.x 引入的**升级回归**(消费方 codex
+  对抗复审 [high],`buildEffective` 与 `readEffectiveWire` 两腿复现)。1.7.2 起 `source: z.unknown().optional()`:
+  任何 JSON 值原样到消费方,规则(非空 ≤80 字符串)与坏形处置(丢键留 server + 留痕)**只**在消费方一处。
+- 红先:`test/mcp-source-label.test.ts` ③ 改「七形全过、原样」+ ③b「坏标签兄弟不拖累好 server」。
+- 类病(任一字段解析拒 ⇒ 整域默认)仍归消费方 S-144 另车。
+
 ## 1.7.1 — 2026-09-06 — `source` 改**只管类型**(撤回 1.7.0 的 min/max 解析拒;patch)
 
 - 1.7.0 把标签规则(非空 ≤80)写进 zod ⇒ 本域整域 all-or-nothing 解析下,**一个**空/超长标签让整套 `mcp.servers`

package/dist/types.d.ts

@@ -7322,16 +7322,18 @@ export declare const McpServerSpec: z.ZodObject<{
      *  consumer can group servers by where they were declared). An OPEN set: CC's `plugin` / `user` /
      *  `project` / `local` are conventions, not a vocabulary — a deployment's own word is equally legal, so
      *  no closed table here (a closed table would reject the operator's grouping word at parse). ABSENT =
-     *  no label (`.optional()`, no default — a label has no default tier). 🔴 TYPE-ONLY here (any string):
-     *  the label RULE (non-empty, ≤80 chars) lives in ONE place — the consumer's projection helper, which
-     *  drops a malformed label's KEY, keeps the server and records the drop. It deliberately does NOT live
-     *  here: this domain parses all-or-nothing, so a `min(1)`/`max(80)` at parse would let one empty label
-     *  default the ENTIRE mcp domain (every server gone) — a blast radius a display label must never have
-     *  (1.7.0 shipped that shape for a few hours; 1.7.1 retracts it). Display-only: no gate / policy / trust
+     *  no label (`.optional()`, no default — a label has no default tier). 🔴 ZERO rules here (`z.unknown()`):
+     *  the label RULE (string, non-empty, ≤80 chars) lives in ONE place — the consumer's projection helper,
+     *  which drops a malformed label's KEY, keeps the server and records the drop. Nothing may live here:
+     *  this domain parses all-or-nothing, so ANY rejection at parse (1.7.0 `min/max`, 1.7.1 `z.string()`
+     *  against a `null`) lets one bad label default the ENTIRE mcp domain — every server gone, silently when
+     *  no onWarning is wired — a blast radius a display label must never have. 1.7.2 makes the key
+     *  parse-transparent: whatever JSON value the file carries reaches the consumer verbatim. Display-only:
+     *  no gate / policy / trust
      *  effect (the trust axis is `contentOrigin` above, which stays a closed table). Before this key existed
      *  both legs stripped it (default-strip object); this is the declaration half of the consumer-side fix
      *  (ticket B-036 / S-143), the projection half lives in the consumer. */
-    source: z.ZodOptional<z.ZodString>;
+    source: z.ZodOptional<z.ZodUnknown>;
     notes: z.ZodOptional<z.ZodString>;
 }, "strip", z.ZodTypeAny, {
     name: string;
@@ -7353,7 +7355,7 @@ export declare const McpServerSpec: z.ZodObject<{
     notes?: string | undefined;
     allowTools?: string[] | undefined;
     contentOrigin?: "local" | "execution" | "external" | undefined;
-    source?: string | undefined;
+    source?: unknown;
 }, {
     name: string;
     transport: {
@@ -7374,7 +7376,7 @@ export declare const McpServerSpec: z.ZodObject<{
     allowTools?: string[] | undefined;
     elicitation?: boolean | undefined;
     contentOrigin?: "local" | "execution" | "external" | undefined;
-    source?: string | undefined;
+    source?: unknown;
 }>;
 export type McpServerSpec = z.infer<typeof McpServerSpec>;
 export declare const McpConfig: z.ZodEffects<z.ZodObject<{
@@ -7451,16 +7453,18 @@ export declare const McpConfig: z.ZodEffects<z.ZodObject<{
          *  consumer can group servers by where they were declared). An OPEN set: CC's `plugin` / `user` /
          *  `project` / `local` are conventions, not a vocabulary — a deployment's own word is equally legal, so
          *  no closed table here (a closed table would reject the operator's grouping word at parse). ABSENT =
-         *  no label (`.optional()`, no default — a label has no default tier). 🔴 TYPE-ONLY here (any string):
-         *  the label RULE (non-empty, ≤80 chars) lives in ONE place — the consumer's projection helper, which
-         *  drops a malformed label's KEY, keeps the server and records the drop. It deliberately does NOT live
-         *  here: this domain parses all-or-nothing, so a `min(1)`/`max(80)` at parse would let one empty label
-         *  default the ENTIRE mcp domain (every server gone) — a blast radius a display label must never have
-         *  (1.7.0 shipped that shape for a few hours; 1.7.1 retracts it). Display-only: no gate / policy / trust
+         *  no label (`.optional()`, no default — a label has no default tier). 🔴 ZERO rules here (`z.unknown()`):
+         *  the label RULE (string, non-empty, ≤80 chars) lives in ONE place — the consumer's projection helper,
+         *  which drops a malformed label's KEY, keeps the server and records the drop. Nothing may live here:
+         *  this domain parses all-or-nothing, so ANY rejection at parse (1.7.0 `min/max`, 1.7.1 `z.string()`
+         *  against a `null`) lets one bad label default the ENTIRE mcp domain — every server gone, silently when
+         *  no onWarning is wired — a blast radius a display label must never have. 1.7.2 makes the key
+         *  parse-transparent: whatever JSON value the file carries reaches the consumer verbatim. Display-only:
+         *  no gate / policy / trust
          *  effect (the trust axis is `contentOrigin` above, which stays a closed table). Before this key existed
          *  both legs stripped it (default-strip object); this is the declaration half of the consumer-side fix
          *  (ticket B-036 / S-143), the projection half lives in the consumer. */
-        source: z.ZodOptional<z.ZodString>;
+        source: z.ZodOptional<z.ZodUnknown>;
         notes: z.ZodOptional<z.ZodString>;
     }, "strip", z.ZodTypeAny, {
         name: string;
@@ -7482,7 +7486,7 @@ export declare const McpConfig: z.ZodEffects<z.ZodObject<{
         notes?: string | undefined;
         allowTools?: string[] | undefined;
         contentOrigin?: "local" | "execution" | "external" | undefined;
-        source?: string | undefined;
+        source?: unknown;
     }, {
         name: string;
         transport: {
@@ -7503,7 +7507,7 @@ export declare const McpConfig: z.ZodEffects<z.ZodObject<{
         allowTools?: string[] | undefined;
         elicitation?: boolean | undefined;
         contentOrigin?: "local" | "execution" | "external" | undefined;
-        source?: string | undefined;
+        source?: unknown;
     }>, "many">>;
 }, "strip", z.ZodTypeAny, {
     servers: {
@@ -7526,7 +7530,7 @@ export declare const McpConfig: z.ZodEffects<z.ZodObject<{
         notes?: string | undefined;
         allowTools?: string[] | undefined;
         contentOrigin?: "local" | "execution" | "external" | undefined;
-        source?: string | undefined;
+        source?: unknown;
     }[];
 }, {
     servers?: {
@@ -7549,7 +7553,7 @@ export declare const McpConfig: z.ZodEffects<z.ZodObject<{
         allowTools?: string[] | undefined;
         elicitation?: boolean | undefined;
         contentOrigin?: "local" | "execution" | "external" | undefined;
-        source?: string | undefined;
+        source?: unknown;
     }[] | undefined;
 }>, {
     servers: {
@@ -7572,7 +7576,7 @@ export declare const McpConfig: z.ZodEffects<z.ZodObject<{
         notes?: string | undefined;
         allowTools?: string[] | undefined;
         contentOrigin?: "local" | "execution" | "external" | undefined;
-        source?: string | undefined;
+        source?: unknown;
     }[];
 }, {
     servers?: {
@@ -7595,7 +7599,7 @@ export declare const McpConfig: z.ZodEffects<z.ZodObject<{
         allowTools?: string[] | undefined;
         elicitation?: boolean | undefined;
         contentOrigin?: "local" | "execution" | "external" | undefined;
-        source?: string | undefined;
+        source?: unknown;
     }[] | undefined;
 }>;
 export type McpConfig = z.infer<typeof McpConfig>;
@@ -10122,16 +10126,18 @@ export declare const DOMAIN_SCHEMAS: {
              *  consumer can group servers by where they were declared). An OPEN set: CC's `plugin` / `user` /
              *  `project` / `local` are conventions, not a vocabulary — a deployment's own word is equally legal, so
              *  no closed table here (a closed table would reject the operator's grouping word at parse). ABSENT =
-             *  no label (`.optional()`, no default — a label has no default tier). 🔴 TYPE-ONLY here (any string):
-             *  the label RULE (non-empty, ≤80 chars) lives in ONE place — the consumer's projection helper, which
-             *  drops a malformed label's KEY, keeps the server and records the drop. It deliberately does NOT live
-             *  here: this domain parses all-or-nothing, so a `min(1)`/`max(80)` at parse would let one empty label
-             *  default the ENTIRE mcp domain (every server gone) — a blast radius a display label must never have
-             *  (1.7.0 shipped that shape for a few hours; 1.7.1 retracts it). Display-only: no gate / policy / trust
+             *  no label (`.optional()`, no default — a label has no default tier). 🔴 ZERO rules here (`z.unknown()`):
+             *  the label RULE (string, non-empty, ≤80 chars) lives in ONE place — the consumer's projection helper,
+             *  which drops a malformed label's KEY, keeps the server and records the drop. Nothing may live here:
+             *  this domain parses all-or-nothing, so ANY rejection at parse (1.7.0 `min/max`, 1.7.1 `z.string()`
+             *  against a `null`) lets one bad label default the ENTIRE mcp domain — every server gone, silently when
+             *  no onWarning is wired — a blast radius a display label must never have. 1.7.2 makes the key
+             *  parse-transparent: whatever JSON value the file carries reaches the consumer verbatim. Display-only:
+             *  no gate / policy / trust
              *  effect (the trust axis is `contentOrigin` above, which stays a closed table). Before this key existed
              *  both legs stripped it (default-strip object); this is the declaration half of the consumer-side fix
              *  (ticket B-036 / S-143), the projection half lives in the consumer. */
-            source: z.ZodOptional<z.ZodString>;
+            source: z.ZodOptional<z.ZodUnknown>;
             notes: z.ZodOptional<z.ZodString>;
         }, "strip", z.ZodTypeAny, {
             name: string;
@@ -10153,7 +10159,7 @@ export declare const DOMAIN_SCHEMAS: {
             notes?: string | undefined;
             allowTools?: string[] | undefined;
             contentOrigin?: "local" | "execution" | "external" | undefined;
-            source?: string | undefined;
+            source?: unknown;
         }, {
             name: string;
             transport: {
@@ -10174,7 +10180,7 @@ export declare const DOMAIN_SCHEMAS: {
             allowTools?: string[] | undefined;
             elicitation?: boolean | undefined;
             contentOrigin?: "local" | "execution" | "external" | undefined;
-            source?: string | undefined;
+            source?: unknown;
         }>, "many">>;
     }, "strip", z.ZodTypeAny, {
         servers: {
@@ -10197,7 +10203,7 @@ export declare const DOMAIN_SCHEMAS: {
             notes?: string | undefined;
             allowTools?: string[] | undefined;
             contentOrigin?: "local" | "execution" | "external" | undefined;
-            source?: string | undefined;
+            source?: unknown;
         }[];
     }, {
         servers?: {
@@ -10220,7 +10226,7 @@ export declare const DOMAIN_SCHEMAS: {
             allowTools?: string[] | undefined;
             elicitation?: boolean | undefined;
             contentOrigin?: "local" | "execution" | "external" | undefined;
-            source?: string | undefined;
+            source?: unknown;
         }[] | undefined;
     }>, {
         servers: {
@@ -10243,7 +10249,7 @@ export declare const DOMAIN_SCHEMAS: {
             notes?: string | undefined;
             allowTools?: string[] | undefined;
             contentOrigin?: "local" | "execution" | "external" | undefined;
-            source?: string | undefined;
+            source?: unknown;
         }[];
     }, {
         servers?: {
@@ -10266,7 +10272,7 @@ export declare const DOMAIN_SCHEMAS: {
             allowTools?: string[] | undefined;
             elicitation?: boolean | undefined;
             contentOrigin?: "local" | "execution" | "external" | undefined;
-            source?: string | undefined;
+            source?: unknown;
         }[] | undefined;
     }>;
     readonly plugins: z.ZodEffects<z.ZodObject<{

package/dist/types.js

@@ -1893,16 +1893,18 @@ export const McpServerSpec = z.object({
      *  consumer can group servers by where they were declared). An OPEN set: CC's `plugin` / `user` /
      *  `project` / `local` are conventions, not a vocabulary — a deployment's own word is equally legal, so
      *  no closed table here (a closed table would reject the operator's grouping word at parse). ABSENT =
-     *  no label (`.optional()`, no default — a label has no default tier). 🔴 TYPE-ONLY here (any string):
-     *  the label RULE (non-empty, ≤80 chars) lives in ONE place — the consumer's projection helper, which
-     *  drops a malformed label's KEY, keeps the server and records the drop. It deliberately does NOT live
-     *  here: this domain parses all-or-nothing, so a `min(1)`/`max(80)` at parse would let one empty label
-     *  default the ENTIRE mcp domain (every server gone) — a blast radius a display label must never have
-     *  (1.7.0 shipped that shape for a few hours; 1.7.1 retracts it). Display-only: no gate / policy / trust
+     *  no label (`.optional()`, no default — a label has no default tier). 🔴 ZERO rules here (`z.unknown()`):
+     *  the label RULE (string, non-empty, ≤80 chars) lives in ONE place — the consumer's projection helper,
+     *  which drops a malformed label's KEY, keeps the server and records the drop. Nothing may live here:
+     *  this domain parses all-or-nothing, so ANY rejection at parse (1.7.0 `min/max`, 1.7.1 `z.string()`
+     *  against a `null`) lets one bad label default the ENTIRE mcp domain — every server gone, silently when
+     *  no onWarning is wired — a blast radius a display label must never have. 1.7.2 makes the key
+     *  parse-transparent: whatever JSON value the file carries reaches the consumer verbatim. Display-only:
+     *  no gate / policy / trust
      *  effect (the trust axis is `contentOrigin` above, which stays a closed table). Before this key existed
      *  both legs stripped it (default-strip object); this is the declaration half of the consumer-side fix
      *  (ticket B-036 / S-143), the projection half lives in the consumer. */
-    source: z.string().optional(),
+    source: z.unknown().optional(),
     notes: z.string().optional(),
 });
 export const McpConfig = z

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/settings-schema",
-  "version": "1.7.1",
+  "version": "1.7.2",
   "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",