@suss/intent-ir 0.21.0 → 0.22.0

package/README.md

@@ -81,7 +81,7 @@ transitions:
       - invokes: unit:lambda ArchiveWorker
 ```
 
-A run that reads the deployment template gives a unit its name, so the boundary a document declares is `unit:lambda ReportBuilder`. The callee on a `results` line is spelled the way the invoking code spells it, which for a function named through an env var is `unit:lambda {ARCHIVE_WORKER_FUNCTION}`. Collapsing that env-var chain is the checker's job today and nothing hands the answer back to a drafted document, so the two spellings stay apart until it does.
+A run that reads the deployment template gives a unit its name, so the boundary a document declares is `unit:lambda ReportBuilder`. The callee on a `results` line is spelled the same way, even when the invoking code reaches it through an env var: `deploymentOf` in `@suss/behavioral-ir` says which resource the template points that variable at, and the drafter and the intent checker both go through it, so a document says which function rather than which variable. A run with no template in it has nothing to put in, and then the line keeps the code's own spelling, `unit:lambda {ARCHIVE_WORKER_FUNCTION}`, and the document's header says which variable it is waiting on. A store the code reaches through a variable works the same way.
 
 A clause can go further, since the summary does. `fields` is the columns the access touches and `by` is what it picks the item out by:
 

package/dist/index.cjs

@@ -49,6 +49,8 @@ var IntentFindingKindSchema = import_zod.z.enum([
   // code produces a REST status the intent doesn't declare
   "unkeyableBoundary",
   // intent boundary can't be keyed, so it can't be checked
+  "renamedBoundary",
+  // a declared store vanished and an undeclared one of the same system appeared with the same outcomes
   // Outcome intent (kind: prd), scenario link coverage against system
   // intent. These concretise the proposal's "scenario not linked /
   // dangling / ambiguous" set (design/proposals/intent-specs.md);

package/dist/index.d.cts

@@ -7,6 +7,7 @@ declare const IntentFindingKindSchema: z.ZodEnum<{
     outcomeShapeMismatch: "outcomeShapeMismatch";
     undeclaredOutcome: "undeclaredOutcome";
     unkeyableBoundary: "unkeyableBoundary";
+    renamedBoundary: "renamedBoundary";
     unlinkedScenario: "unlinkedScenario";
     danglingScenarioLink: "danglingScenarioLink";
     ambiguousScenarioLink: "ambiguousScenarioLink";
@@ -51,6 +52,7 @@ declare const IntentFindingSchema: z.ZodObject<{
         outcomeShapeMismatch: "outcomeShapeMismatch";
         undeclaredOutcome: "undeclaredOutcome";
         unkeyableBoundary: "unkeyableBoundary";
+        renamedBoundary: "renamedBoundary";
         unlinkedScenario: "unlinkedScenario";
         danglingScenarioLink: "danglingScenarioLink";
         ambiguousScenarioLink: "ambiguousScenarioLink";

package/dist/index.d.ts

@@ -7,6 +7,7 @@ declare const IntentFindingKindSchema: z.ZodEnum<{
     outcomeShapeMismatch: "outcomeShapeMismatch";
     undeclaredOutcome: "undeclaredOutcome";
     unkeyableBoundary: "unkeyableBoundary";
+    renamedBoundary: "renamedBoundary";
     unlinkedScenario: "unlinkedScenario";
     danglingScenarioLink: "danglingScenarioLink";
     ambiguousScenarioLink: "ambiguousScenarioLink";
@@ -51,6 +52,7 @@ declare const IntentFindingSchema: z.ZodObject<{
         outcomeShapeMismatch: "outcomeShapeMismatch";
         undeclaredOutcome: "undeclaredOutcome";
         unkeyableBoundary: "unkeyableBoundary";
+        renamedBoundary: "renamedBoundary";
         unlinkedScenario: "unlinkedScenario";
         danglingScenarioLink: "danglingScenarioLink";
         ambiguousScenarioLink: "ambiguousScenarioLink";

package/dist/index.js

@@ -12,6 +12,8 @@ var IntentFindingKindSchema = z.enum([
   // code produces a REST status the intent doesn't declare
   "unkeyableBoundary",
   // intent boundary can't be keyed, so it can't be checked
+  "renamedBoundary",
+  // a declared store vanished and an undeclared one of the same system appeared with the same outcomes
   // Outcome intent (kind: prd), scenario link coverage against system
   // intent. These concretise the proposal's "scenario not linked /
   // dangling / ambiguous" set (design/proposals/intent-specs.md);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@suss/intent-ir",
-  "version": "0.21.0",
+  "version": "0.22.0",
   "type": "module",
   "description": "Intent IR for suss — the team-authored side of the loop. PRD (outcome) intent and system intent, in shapes that pair against derived behavioral summaries.",
   "keywords": [
@@ -47,7 +47,7 @@
     "zod": "^4.0.0"
   },
   "dependencies": {
-    "@suss/ir-core": "0.21.0"
+    "@suss/ir-core": "0.22.0"
   },
   "devDependencies": {
     "tsup": "*",