@intentius/chant-lexicon-aws 0.0.18 → 0.0.24

package/dist/rules/ext001.ts

@@ -73,6 +73,10 @@ function matchesCondition(condition: unknown, properties: Record<string, unknown
       if ("enum" in s && Array.isArray(s.enum)) {
         if (!s.enum.includes(properties[propName])) return false;
       }
+      if ("pattern" in s && typeof s.pattern === "string") {
+        const val = properties[propName];
+        if (typeof val !== "string" || !new RegExp(s.pattern).test(val)) return false;
+      }
     }
   }
 

package/{src/skills/chant-eks.md → dist/skills/chant-aws-eks.md}

@@ -1,6 +1,6 @@
 ---
-skill: chant-eks
-description: End-to-end EKS workflow bridging AWS infrastructure and Kubernetes workloads
+skill: chant-aws-eks
+description: EKS end-to-end workflow — provision cluster, configure kubectl, deploy K8s workloads
 user-invocable: true
 ---
 
@@ -33,6 +33,9 @@ AWS Lexicon (CloudFormation)          K8s Lexicon (kubectl apply)
 # Build CloudFormation template
 chant build src/infra/ --output infra.json
 
+# See what changed since last deploy (compares current build against last snapshot's digest)
+chant state diff staging aws
+
 # Deploy
 aws cloudformation deploy \
   --template-file infra.json \

package/dist/skills/chant-aws.md

@@ -8,7 +8,7 @@ user-invocable: true
 
 ## How chant and CloudFormation relate
 
-chant is a **synthesis-only** tool — it compiles TypeScript source files into CloudFormation JSON (or YAML). chant does NOT call AWS APIs. Your job as an agent is to bridge the two:
+chant is a **synthesis compiler** — it compiles TypeScript source files into CloudFormation JSON (or YAML). `chant build` does not call AWS APIs; synthesis is pure and deterministic. The optional `chant state snapshot` command queries AWS APIs to capture deployment metadata (physical IDs, status, outputs) for observability. Your job as an agent is to bridge synthesis and deployment:
 
 - Use **chant** for: build, lint, diff (local template comparison)
 - Use **AWS CLI** for: validate-template, deploy, change sets, rollback, drift detection, and all stack operations
@@ -344,9 +344,9 @@ aws cloudformation describe-stacks --stack-name <stack-name> --query 'Stacks[0].
 
 ### Step 2: Branch on status
 
-- **`*_IN_PROGRESS`** → Wait. Do not take action while an operation is in progress.
-- **`*_FAILED` or `*_ROLLBACK_*`** → Read the events (Step 3).
-- **`*_COMPLETE`** → Stack is stable. If behavior is wrong, check resource configuration.
+- **`*_IN_PROGRESS`** — Wait. Do not take action while an operation is in progress.
+- **`*_FAILED` or `*_ROLLBACK_*`** — Read the events (Step 3).
+- **`*_COMPLETE`** — Stack is stable. If behavior is wrong, check resource configuration.
 
 ### Step 3: Read the failure events