@suss/contract-aws-apigateway 0.0.1 → 0.1.0

package/README.md

@@ -4,9 +4,9 @@ Generate suss `BehavioralSummary[]` for AWS API Gateway resources (REST + HTTP A
 
 ## What this package is
 
-`@suss/contract-aws-apigateway` is a **resource-semantics stub**: it knows what an API Gateway endpoint *does* (status codes, authorizer behavior, CORS preflight, throttling) given a normalized configuration. It does **not** know how that configuration was authored — that's the job of a manifest reader (`@suss/contract-cloudformation`, future CDK/Terraform readers), which parses its source format and hands a normalized config to this package.
+`@suss/contract-aws-apigateway` is a **resource-semantics stub**: it knows what an API Gateway endpoint *does* (status codes, authorizer behavior, CORS preflight, throttling) given a normalized configuration. It does **not** know how that configuration was authored; that's the job of a manifest reader (`@suss/contract-cloudformation`, future CDK/Terraform readers), which parses its source format and hands a normalized config to this package.
 
-This separation means: configure your API in CloudFormation, CDK, SAM, or Terraform — the same resource semantics produce the same summary.
+This separation means: configure your API in CloudFormation, CDK, SAM, or Terraform, and the same resource semantics produce the same summary.
 
 ## Where it sits
 
@@ -21,7 +21,7 @@ packages/contract/
 
 ## Why configuration matters
 
-A handler that only returns `200` produces a *much* larger behavioral envelope once it's deployed behind API Gateway: an authorizer adds `401`/`403`, request validation adds `400`, throttling adds `429`, integration timeouts add `504`, CORS adds an `OPTIONS` preflight endpoint. Without modeling these, a consumer that handles `429` looks like it has a dead branch — when in reality the platform produces `429` even though the handler doesn't.
+A handler that only returns `200` produces a *much* larger behavioral envelope once it's deployed behind API Gateway: an authorizer adds `401`/`403`, request validation adds `400`, throttling adds `429`, integration timeouts add `504`, CORS adds an `OPTIONS` preflight endpoint. Without modeling these, a consumer that handles `429` looks like it has a dead branch, when in reality the platform produces `429` even though the handler doesn't.
 
 These transitions are emitted with `confidence.source: "derived"` and an opaque `Predicate` of the form `platform:apiGateway:<contract>`. Per-transition `metadata` carries attribution (which configuration field introduced this transition) for `inspect`/`diff` output, without forcing consumers to disambiguate platform causes.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@suss/contract-aws-apigateway",
-  "version": "0.0.1",
+  "version": "0.1.0",
   "type": "module",
   "description": "Generate suss behavioral summaries for AWS API Gateway resources (REST + HTTP API), independent of how they were deployed.",
   "keywords": [
@@ -45,7 +45,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@suss/behavioral-ir": "0.0.1"
+    "@suss/behavioral-ir": "0.1.0"
   },
   "devDependencies": {
     "tsup": "*",