@wairon/cli 5.1.1-dev.77 → 5.1.1-dev.79

package/dist/index.js

@@ -4397,9 +4397,11 @@ var RulesConfigSchema = import_zod3.z.object({
   materializeAgentFiles: import_zod3.z.boolean().default(false),
   /**
    * Severity overrides for SDD validation rules.
-   * Key: rule code (e.g. CIRCULAR_DEPENDENCY), Value: error | warning | off
+   * Key: rule code (e.g. CIRCULAR_DEPENDENCY), Value: error | warning | notice | off.
+   * A notice is still reported, but never makes the tree invalid and never
+   * fails `--ci`; off is not reported at all.
    */
-  sddRuleSeverity: import_zod3.z.record(import_zod3.z.enum(["error", "warning", "off"])).default({}),
+  sddRuleSeverity: import_zod3.z.record(import_zod3.z.enum(["error", "warning", "notice", "off"])).default({}),
   /** Dynamic naming conventions and stereotype suffix rules */
   naming: NamingRuleConfigSchema.optional(),
   /** Dynamic metadata documentation constraints */
@@ -7822,6 +7824,8 @@ body:not(.panel-closed) #panelToggle { background:var(--accent); color:#fff; bor
 #panel .flowbtn:hover { background:var(--hover-bg); }
 #panel .issue { border-left:3px solid var(--danger); padding:6px 9px; margin:6px 0; background:var(--card); font-size:12px; border-radius:0 7px 7px 0; }
 #panel .issue.warning { border-left-color:var(--warn); }
+#panel .issue.notice { border-left-color:var(--accent); }
+#panel .issue .sev { font-size:10px; color:var(--dim); text-transform:uppercase; letter-spacing:.04em; margin-left:6px; }
 #panel .issue code { font-size:10.5px; color:var(--dim); }
 
 /* Presentation mode = the canvas page, focused: the header chrome and legend
@@ -8032,7 +8036,15 @@ var MODEL = __MODEL_JSON__;
   });
   document.getElementById('issueCount').textContent =
     MODEL.issues.filter(function (i) { return i.severity === 'error'; }).length + 'e/' +
-    MODEL.issues.filter(function (i) { return i.severity === 'warning'; }).length + 'w';
+    MODEL.issues.filter(function (i) { return i.severity === 'warning'; }).length + 'w/' +
+    MODEL.issues.filter(function (i) { return i.severity === 'notice'; }).length + 'n';
+  // A node is marked failing only for an error or a warning; one that holds
+  // only notices gets its own quieter mark, never the failing one.
+  function issueMark(id) {
+    var list = state.showIssues && issuesBySpec[id];
+    if (!list) return '';
+    return list.some(function (i) { return i.severity !== 'notice'; }) ? ' hasIssue' : ' hasNotice';
+  }
 
   var PATTERN_TYPES = { Repository:1, FeatureComponent:1, RouterComponent:1 };
   // A retired Specialist or Gateway renders as a plain box marked retired, so a
@@ -8372,6 +8384,9 @@ var MODEL = __MODEL_JSON__;
       { selector: 'edge.stubHover', style: { 'line-color': t.selGlow, 'target-arrow-color': t.selGlow, width: 2.6, opacity: 1, 'z-compound-depth': 'top' } },
       { selector: '.dimmed', style: { opacity: 0.13 } },
       { selector: '.hasIssue', style: { 'border-color': t.issue, 'border-style': 'dashed', 'border-width': 3 } },
+      // Notices only: the node keeps its own border colour and width (no layout
+      // nudge), drawn dotted so it reads as noted rather than failing.
+      { selector: '.hasNotice', style: { 'border-style': 'dotted' } },
       // Overlay only (no border) \u2014 a border changes node geometry, which nudges
       // the compound parent and makes hover flicker; overlay never affects layout.
       { selector: '.sel', style: { 'overlay-color': t.selGlow, 'overlay-opacity': 0.34, 'overlay-padding': 6 } },
@@ -9161,7 +9176,7 @@ var MODEL = __MODEL_JSON__;
       var kindCls = t.kind === 'entity' ? 'typeEntity' : 'typeValue';
       var dim = !typeMatches(t);
       var extra = (dim ? ' dimmed' : '')
-        + (state.showIssues && issuesBySpec[t.id] ? ' hasIssue' : '')
+        + issueMark(t.id)
         + (state.selectedKind === 'type' && state.selected === t.id ? ' sel' : '');
       if (sh.plain) {
         eles.push({
@@ -9451,7 +9466,7 @@ var MODEL = __MODEL_JSON__;
       }
       classes += (e.hasKids ? ' drillable' : '') + (isPub ? ' public' : '')
         + (dim ? ' dimmed' : '')
-        + (state.showIssues && issuesBySpec[e.id] ? ' hasIssue' : '')
+        + issueMark(e.id)
         + (state.selectedKind === e.kind && state.selected === e.id ? ' sel' : '');
       if (inner) {
         var boxNode = { data: { id: aid, label: e.kind === 'subsystem' ? nameOf(e) : nameOf(e), w: p.w, h: p.h, tw: p.w - 16 }, classes: classes };
@@ -11396,7 +11411,7 @@ var MODEL = __MODEL_JSON__;
   }
   function issueHtml(list) {
     return list.map(function (i) {
-      return '<div class="issue ' + esc(i.severity) + '"><code>' + esc(i.code) + '</code><br>' + esc(i.message) + '</div>';
+      return '<div class="issue ' + esc(i.severity) + '"><code>' + esc(i.code) + '</code><span class="sev">' + esc(i.severity) + '</span><br>' + esc(i.message) + '</div>';
     }).join('');
   }
 
@@ -12083,7 +12098,7 @@ function defaultTargetConfig(type) {
     enabled: true
   };
 }
-var WAIRON_VERSION = "5.1.1-dev.77";
+var WAIRON_VERSION = "5.1.1-dev.79";
 var GITHUB_REPO = "SYW-Apps/Waffle-AIron";
 var ARCHITECT_AGENT_ID = "agent-architect";
 var ARCHITECT_TEMPLATE_ID = "architect";
@@ -13465,7 +13480,7 @@ var publicSurfaceBoundContractRule = {
 // src/core/rules/integrity/lint-allows.ts
 var lintAllowsRule = {
   name: "lint-allows",
-  description: "Per-spec lint suppressions (lint.allow) must name real issue codes and actually suppress a finding \u2014 unknown codes and stale allows are flagged. An allow covers exactly the occurrence it names: a finding that reports a site is silenced only by an allow whose `at` is that site, a finding that reports none only by an allow that names none, and an aggregating finding only by an allow whose `covers` lists every unit it reports \u2014 a unit nobody listed is named back as new instead of inheriting a decision taken about its neighbours. So a coarse allow left on a rule that names sites, and an allow whose site the run no longer reports, are both UNUSED_LINT_ALLOW, and the finding names the sites that did fire. Allows silence warnings only; errors always surface.",
+  description: "Per-spec lint suppressions (lint.allow) must name real issue codes and actually suppress a finding \u2014 unknown codes and stale allows are flagged. An allow covers exactly the occurrence it names: a finding that reports a site is silenced only by an allow whose `at` is that site, a finding that reports none only by an allow that names none, and an aggregating finding only by an allow whose `covers` lists every unit it reports \u2014 a unit nobody listed is named back as new instead of inheriting a decision taken about its neighbours. So a coarse allow left on a rule that names sites, and an allow whose site the run no longer reports, are both UNUSED_LINT_ALLOW, and the finding names the sites that did fire. Allows silence warnings and notices; errors always surface.",
   codes: [
     { code: "UNKNOWN_LINT_ALLOW_CODE", defaultSeverity: "warning", summary: "lint.allow names an issue code no registered rule emits" },
     { code: "UNUSED_LINT_ALLOW", defaultSeverity: "warning", summary: "lint.allow entry matched no finding this run \u2014 the code never fired, or it fired at sites this allow does not name" }
@@ -20569,6 +20584,9 @@ var DEPTH_GATED_CODES = {
   UNUSED_COMPONENT: "narratives",
   UNUSED_METHOD: "narratives"
 };
+function atMostWarning(severity) {
+  return severity === "error" ? "warning" : severity;
+}
 var COMPLETENESS_RULES = /* @__PURE__ */ new Set([
   "MISSING_IMPLEMENTATION_METHOD",
   "MISSING_NARRATIVE",
@@ -20840,7 +20858,7 @@ function buildRuleContext(opts) {
       return profileSeverity;
     }
     if (isDraftContext && COMPLETENESS_RULES.has(ruleCode)) {
-      return "warning";
+      return atMostWarning(defaultSeverity);
     }
     return defaultSeverity;
   };
@@ -20914,13 +20932,13 @@ function buildRuleContext(opts) {
         allowClaimed = true;
         const grew = (parts?.covers ?? []).filter((unit) => !(allow.covers ?? []).includes(unit));
         if (grew.length === 0) {
-          if (severity === "warning") return;
+          if (severity !== "error") return;
         } else {
           text2 = `${text2} A lint.allow covers this site, but not ${grew.length} part(s) of it \u2014 ${grew.map((u) => `"${u}"`).join("; ")} ${grew.length === 1 ? "is" : "are"} new. Decide on them: add them to the allow's \`covers\` with a reason that is actually true, or fix them.`;
         }
       }
     }
-    if (specId && parts && severity === "warning" && !allowClaimed) {
+    if (specId && parts && severity !== "error" && !allowClaimed) {
       const entry = carriedLookup.get(carriedKey(specId, code, parts.at));
       if (entry) {
         entry.fired = true;
@@ -21066,7 +21084,8 @@ function validateComponentCandidate(candidate, opts = {}) {
   const own = issues.filter((i) => !i.specId || i.specId === candidate.id);
   return {
     errors: own.filter((i) => i.severity === "error"),
-    warnings: own.filter((i) => i.severity === "warning")
+    warnings: own.filter((i) => i.severity === "warning"),
+    notices: own.filter((i) => i.severity === "notice")
   };
 }
 
@@ -21090,7 +21109,7 @@ var RESOLUTION_FAILURE_CODES = /* @__PURE__ */ new Set([
   "INVALID_TRUSTED_LINK",
   "CROSS_TREE_REF_UNRESOLVED"
 ]);
-var SEVERITY_RANK = { off: 0, warning: 1, error: 2 };
+var SEVERITY_RANK = { off: 0, notice: 1, warning: 2, error: 3 };
 function issueKey(issue2) {
   return `${issue2.code}|${issue2.specId ?? ""}`;
 }
@@ -28239,6 +28258,15 @@ var logger = {
       console.warn(import_chalk.default.yellow("\u26A0") + "  " + import_chalk.default.yellow(message));
     }
   },
+  /**
+   * A finding reported at `notice` severity: listed, never a failure. Kept
+   * visually apart from warn so a reader never mistakes one for the other.
+   */
+  notice(message) {
+    if (shouldLog("info")) {
+      console.log(import_chalk.default.blue("\u25C6") + "  " + import_chalk.default.blue("notice ") + message);
+    }
+  },
   error(message) {
     console.error(import_chalk.default.red("\u2716") + "  " + import_chalk.default.red(message));
   },
@@ -28519,11 +28547,15 @@ function candidateOptions() {
   return config ? { rules: config.rules, projectType: config.projectType } : {};
 }
 function noticesFrom(verdict) {
-  return verdict.warnings.map((w) => `${w.code}: ${w.message}`);
+  return [
+    ...verdict.warnings.map((w) => `${w.code}: ${w.message}`),
+    ...verdict.notices.map((n) => `${n.code} (notice): ${n.message}`)
+  ];
 }
-function componentCandidateGate(options = candidateOptions()) {
+function componentCandidateGate(options = candidateOptions(), storedOwner) {
   return {
     gate: (kind, merged) => {
+      refuseUnknownOwner(kind, merged, storedOwner);
       if (kind !== "component") return;
       const verdict = validateComponentCandidate(merged, options);
       if (verdict.errors.length) throw new Error(formatCandidateRefusal(verdict));
@@ -28531,6 +28563,14 @@ function componentCandidateGate(options = candidateOptions()) {
     }
   };
 }
+function refuseUnknownOwner(kind, merged, storedOwner) {
+  if (kind !== "component" && kind !== "type") return;
+  const owner = merged.subsystem;
+  if (!owner || owner === storedOwner) return;
+  if (loadSpec("subsystem", owner)) return;
+  const sentence = MISSING_PARENT[kind](owner);
+  throw new Error(`${sentence} Nothing was written.`);
+}
 var STORE_MANAGED_FIELDS = /* @__PURE__ */ new Set(["status", "updatedAt"]);
 var ALWAYS_CARRIED_FIELDS = /* @__PURE__ */ new Set(["ext"]);
 var STATUS_ORDER = ["draft", "design", "complete"];
@@ -28826,9 +28866,9 @@ function deleteSpec2(kind, id) {
 }
 function updateSpecGated(kind, id, delta, dryRun) {
   const bound2 = candidateOptions();
-  const gate = componentCandidateGate(bound2);
   const testRoots = bound2.rules?.conformance?.testRoots ?? [];
-  const stored = testRoots.length > 0 ? loadSpec(kind, id) : null;
+  const stored = loadSpec(kind, id);
+  const gate = componentCandidateGate(bound2, stored?.subsystem);
   const report = updateSpec(kind, id, delta, gate, dryRun);
   const changed = changedMethods(report);
   if (changed.length > 0 && testRoots.length > 0) {
@@ -29128,7 +29168,7 @@ var specChangeReportOutput = {
   ...staleServerOutput
 };
 var validationIssueOutput = {
-  severity: import_zod11.z.enum(["error", "warning"]).describe("The finding's severity after project overrides."),
+  severity: import_zod11.z.enum(["error", "warning", "notice"]).describe("The finding's severity after project overrides."),
   code: import_zod11.z.string().describe("The rule code, UPPER_SNAKE \u2014 the stable handle to filter and suppress by."),
   message: import_zod11.z.string().describe("What is wrong, named."),
   agentId: import_zod11.z.string().optional().describe("The agent the finding concerns, when it concerns one."),
@@ -29141,9 +29181,12 @@ var validationIssueOutput = {
   )
 };
 var validateTreeOutput = {
-  valid: import_zod11.z.boolean().describe("False when the tree holds at least one error."),
+  valid: import_zod11.z.boolean().describe("False when the tree holds at least one error; warnings and notices never make it false."),
   errors: import_zod11.z.array(import_zod11.z.object(validationIssueOutput)).describe("Every finding of severity error."),
   warnings: import_zod11.z.array(import_zod11.z.object(validationIssueOutput)).describe("Every finding of severity warning."),
+  notices: import_zod11.z.array(import_zod11.z.object(validationIssueOutput)).describe(
+    "Every finding of severity notice: reported, never a failure \u2014 they never make the tree invalid and never fail `wairon validate --ci`."
+  ),
   resolvedThrough: import_zod11.z.object({
     root: import_zod11.z.string().describe("The top root that was validated."),
     scope: import_zod11.z.string().describe("The mount chain the verdict was scoped to.")
@@ -29530,7 +29573,7 @@ function createMcpServer(options = {}) {
     server,
     "validateTopology",
     {
-      description: "Validate the project's agent topology. Returns errors and warnings (duplicate ids, overlapping ownership, missing paths, etc.). Supports optional subsystem scoping.",
+      description: "Validate the project's agent topology. Returns errors, warnings and notices (duplicate ids, overlapping ownership, missing paths, etc.). Supports optional subsystem scoping.",
       inputSchema: {
         subsystem: import_zod11.z.string().optional().describe("Only validate topology for agents under the specified subsystem")
       }
@@ -29550,7 +29593,8 @@ function createMcpServer(options = {}) {
         return json({
           valid: result.issues.filter((i) => i.severity === "error").length === 0,
           errors: result.issues.filter((i) => i.severity === "error"),
-          warnings: result.issues.filter((i) => i.severity === "warning")
+          warnings: result.issues.filter((i) => i.severity === "warning"),
+          notices: result.issues.filter((i) => i.severity === "notice")
         });
       } catch (e) {
         return errText(String(e));
@@ -30268,7 +30312,7 @@ ${renderChangeReport(report)}`,
     server,
     "sdd_validate_tree",
     {
-      description: "Validate the SDD spec tree, checking parent references, contract compatibility, narratives, and component type boundaries. Supports scoping and recursion controls. Findings come back as structured content too, under the schema this tool declares \u2014 errors and warnings already split, each with its code, severity, message and the spec it concerns \u2014 so a caller filters them as objects instead of parsing the JSON text block and hoping its shape holds.",
+      description: "Validate the SDD spec tree, checking parent references, contract compatibility, narratives, and component type boundaries. Supports scoping and recursion controls. Findings come back as structured content too, under the schema this tool declares \u2014 errors, warnings and notices already split into three lists (a notice never makes the tree invalid and never fails --ci), each with its code, severity, message and the spec it concerns \u2014 so a caller filters them as objects instead of parsing the JSON text block and hoping its shape holds.",
       inputSchema: {
         subsystem: import_zod11.z.string().optional().describe("Only validate the specified subsystem (granular)"),
         recursive: import_zod11.z.boolean().optional().describe("Whether to recursively validate subprojects (default: true)")
@@ -30289,6 +30333,7 @@ ${renderChangeReport(report)}`,
           valid: result.valid,
           errors: result.issues.filter((i) => i.severity === "error"),
           warnings: result.issues.filter((i) => i.severity === "warning"),
+          notices: result.issues.filter((i) => i.severity === "notice"),
           ...result.resolvedThrough ? { resolvedThrough: result.resolvedThrough } : {}
         });
       } catch (e) {
@@ -30404,7 +30449,7 @@ ${testsBlock}` : ""}`, deletion);
       inputSchema: {
         kind: import_zod11.z.enum(["system", "subsystem", "component", "interface", "implementation", "type"]).describe("The spec kind to update (system = the singleton L0 \u2014 vision, boundaries, globalRequirements, databases, and publicInterfaces: the project gateway surface, each entry {id, name, subsystem, component, type, details, audience: project|department|instance|partner|external}; id is informational)"),
         id: import_zod11.z.string().describe("The ID of the spec to update (namespaced if needed)"),
-        delta: import_zod11.z.record(import_zod11.z.any()).describe(`The partial fields to merge into the spec. ARRAYS UPSERT, they do not replace: an array whose elements carry an identity is merged element-by-element, so a delta naming ONE element leaves the others intact. Identity is "name" or "id" by default, and per field: dispatch by "capability", a listener's mounts by "portal", lifecycle by phase+component+method, emits/subscribesTo by topic+event, trustedLinks by "subsystem", a subsystem's publicInterfaces by component+interface (or type+details for an entry not yet bound to a component), invariants and patterns by "id", lint.allow by "code" AND "at" (an allow covers one occurrence, so several may share a code on one spec), an interface method's findings by "code", boundaries by "name", globalRequirements by "description", switch cases by "value", try catches by "error". Identity merging applies at EVERY depth, including an array INSIDE an element (a method's params, a step's catches). Add "action: 'delete'" (or "remove: true") alongside that identity to REMOVE an element \u2014 including a stale lint allow. Arrays of plain STRINGS (owns, dependsOn, guarantees) carry no per-element identity and are replaced wholesale; pass [] to clear any array outright. To REMOVE an optional field entirely, list it in "unset": e.g. {"unset": ["basePath", "variant"]} \u2014 passing null/undefined means "no change" (they are skipped), and writing "" would leave the field present but empty, which is a different and usually wrong spec. Unsetting a required field is refused by schema validation, which names it. For narrative steps, match by "stepNumber" and use "action: 'insert'" (shifts subsequent steps up) or "action: 'delete'" (shifts subsequent steps down and removes it). Step entries apply in ASCENDING stepNumber order, each against the numbering the earlier entries of the SAME delta left behind \u2014 delete step 3 and step 7 becomes step 6 \u2014 so prefer labels, and restate the step's "label" or "description" on a delete to have it checked against the step actually addressed. Renumbering RELOCATES every flow jump field (onTrueStep/onFalseStep/cases.step/defaultStep/endStep/catches.step/finallyStep/toStep) in the same narrative. A delete is REJECTED when the narrative has no such step, when a jump still targets it (retarget the referrers first), when a restated label/description does not match, or when it is a loop/try/parallel header whose body would be left standing (retype the header first to dissolve the region, then delete it). Changing a step's "type" REBUILDS it for the new type: its description and label are kept and every field the new type cannot carry is dropped (returned as a NOTICE); a delta that retypes AND sets such a field is refused. A step delta is also refused when it carries a marker the merge does not recognise: a non-boolean "remove", an "action" that is neither "insert" nor "delete", a "captureJumps" outside an insert, or no "stepNumber" to address. Inserting AT a jump target relocates those jumps past the inserted step by default (a NOTICE is returned) \u2014 add "captureJumps": true on the inserted step to retarget entry jumps onto it (loop/try endStep region tails always relocate with the body and are never captured). Every jump field has a "*Label" twin (toLabel, onFalseLabel, endLabel, \u2026, and "label" on a cases/catches entry) resolved against step labels AFTER the merge, so a delta may anchor on a label only pre-existing steps carry; a label the delta supplies REPLACES the stored number it twins, while setting the number and its label together in one delta is refused as a contradiction. Reference ids in deltas may use LOCAL names \u2014 they are qualified against the spec's namespace exactly as the loader would. Per-spec lint suppression: set "lint: { allow: [{ code, at, covers, reason }] }" to silence a WARNING code on this spec only (errors always surface; stale allows are flagged). An allow covers EXACTLY the occurrence it names: "at" is the site the finding names (a contract method, an import edge "from -> to", a declared edge "component -> target") and is REQUIRED for a code whose findings report one, while a finding that reports no site is covered only by an allow that names none; "covers" lists the units an aggregating finding reports, and the allow silences it only when every one is listed. This delta is deliberately OPEN below its top level \u2014 the shapes nest further than a schema here should restate \u2014 so a key that is not a field at its depth is not refused, it is NAMED BACK under NO EFFECT in the answer, together with any value the spec already held and any "unset" that removed nothing. Read that list: it is where a nested typo shows up.`),
+        delta: import_zod11.z.record(import_zod11.z.any()).describe(`The partial fields to merge into the spec. ARRAYS UPSERT, they do not replace: an array whose elements carry an identity is merged element-by-element, so a delta naming ONE element leaves the others intact. Identity is "name" or "id" by default, and per field: dispatch by "capability", a listener's mounts by "portal", lifecycle by phase+component+method, emits/subscribesTo by topic+event, trustedLinks by "subsystem", a subsystem's publicInterfaces by component+interface (or type+details for an entry not yet bound to a component), invariants and patterns by "id", lint.allow by "code" AND "at" (an allow covers one occurrence, so several may share a code on one spec), an interface method's findings by "code", boundaries by "name", globalRequirements by "description", switch cases by "value", try catches by "error". Identity merging applies at EVERY depth, including an array INSIDE an element (a method's params, a step's catches). Add "action: 'delete'" (or "remove: true") alongside that identity to REMOVE an element \u2014 including a stale lint allow. Arrays of plain STRINGS (owns, dependsOn, guarantees) carry no per-element identity and are replaced wholesale; pass [] to clear any array outright. To REMOVE an optional field entirely, list it in "unset": e.g. {"unset": ["basePath", "variant"]} \u2014 passing null/undefined means "no change" (they are skipped), and writing "" would leave the field present but empty, which is a different and usually wrong spec. Unsetting a required field is refused by schema validation, which names it. For narrative steps, match by "stepNumber" and use "action: 'insert'" (shifts subsequent steps up) or "action: 'delete'" (shifts subsequent steps down and removes it). Step entries apply in ASCENDING stepNumber order, each against the numbering the earlier entries of the SAME delta left behind \u2014 delete step 3 and step 7 becomes step 6 \u2014 so prefer labels, and restate the step's "label" or "description" on a delete to have it checked against the step actually addressed. Renumbering RELOCATES every flow jump field (onTrueStep/onFalseStep/cases.step/defaultStep/endStep/catches.step/finallyStep/toStep) in the same narrative. A delete is REJECTED when the narrative has no such step, when a jump still targets it (retarget the referrers first), when a restated label/description does not match, or when it is a loop/try/parallel header whose body would be left standing (retype the header first to dissolve the region, then delete it). Changing a step's "type" REBUILDS it for the new type: its description and label are kept and every field the new type cannot carry is dropped (returned as a NOTICE); a delta that retypes AND sets such a field is refused. A step delta is also refused when it carries a marker the merge does not recognise: a non-boolean "remove", an "action" that is neither "insert" nor "delete", a "captureJumps" outside an insert, or no "stepNumber" to address. Inserting AT a jump target relocates those jumps past the inserted step by default (a NOTICE is returned) \u2014 add "captureJumps": true on the inserted step to retarget entry jumps onto it (loop/try endStep region tails always relocate with the body and are never captured). Every jump field has a "*Label" twin (toLabel, onFalseLabel, endLabel, \u2026, and "label" on a cases/catches entry) resolved against step labels AFTER the merge, so a delta may anchor on a label only pre-existing steps carry; a label the delta supplies REPLACES the stored number it twins, while setting the number and its label together in one delta is refused as a contradiction. Reference ids in deltas may use LOCAL names \u2014 they are qualified against the spec's namespace exactly as the loader would. Per-spec lint suppression: set "lint: { allow: [{ code, at, covers, reason }] }" to silence a WARNING or NOTICE code on this spec only (errors always surface; stale allows are flagged). An allow covers EXACTLY the occurrence it names: "at" is the site the finding names (a contract method, an import edge "from -> to", a declared edge "component -> target") and is REQUIRED for a code whose findings report one, while a finding that reports no site is covered only by an allow that names none; "covers" lists the units an aggregating finding reports, and the allow silences it only when every one is listed. This delta is deliberately OPEN below its top level \u2014 the shapes nest further than a schema here should restate \u2014 so a key that is not a field at its depth is not refused, it is NAMED BACK under NO EFFECT in the answer, together with any value the spec already held and any "unset" that removed nothing. Read that list: it is where a nested typo shows up.`),
         dryRun: import_zod11.z.boolean().optional().describe("Ask what this delta WOULD do instead of doing it. The whole write runs, the candidate gate included, and the answer is the change report it would have produced \u2014 marked DRY RUN, with nothing stamped and not one byte of the stored file moved. Use it before a delta that renumbers a long narrative.")
       },
       outputSchema: specChangeReportOutput