@kensio/yulin-aws-simulation 1.15.0 → 1.16.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "yulin-aws-simulation",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "How to test AWS code well with the @kensio/yulin in-process simulator.",
   "author": {
     "name": "Kensio Software",

package/README.md

@@ -67,6 +67,12 @@ ambiguous with the suffix Secrets Manager appends to an ARN and advised against
 already reached production. It caught a wrongly computed Cognito `SECRET_HASH` the stub had happily
 accepted.
 
+**Drive requests into the simulation with `SimAwsHttp`.** Reading state back covers the resources.
+`http.fetch("https://www.example.test/docs/x")` covers the path through them, with nothing listening
+and no port to add. One request resolves the hostname through simulated Route 53, finds the
+Distribution its alias records point at, and runs the deployed CloudFront Function at
+viewer-request. A template assertion over the same stack passes with every Route 53 record missing.
+
 **Match service errors by `name`.** The SDK exports its exception classes, which invites the wrong
 check. `instanceof` holds only while exactly one copy of the SDK is in play. It passes in production
 and fails against the simulator. `name` is what the wire carries, and is the check that is right in

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kensio/yulin-aws-simulation",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "How to test AWS code well with the @kensio/yulin in-process simulator.",
   "keywords": [
     "agent-skills",

package/skills/yulin-aws-simulation/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: yulin-aws-simulation
-description: Use the @kensio/yulin in-process AWS simulator well when testing AWS code, using it directly rather than building a harness around it, driving tests, local dev and production from one synthesized CDK template, deploying a whole cdk.out cloud assembly, intercepting SDK clients with SimSdk, controlling simulated time, matching service errors by name, and handling properties Yulin refuses to simulate. Use when writing or reviewing tests that touch AWS, when replacing aws-sdk-client-mock or hand-rolled AWS stubs, when a CDK stack needs testing, when test setup around Yulin is growing helper classes or wrapper functions, and when Yulin refuses a template property or an SDK command.
+description: Use the @kensio/yulin in-process AWS simulator well when testing AWS code, using it directly rather than building a harness around it, driving tests, local dev and production from one synthesized CDK template, deploying a whole cdk.out cloud assembly, intercepting SDK clients with SimSdk, driving HTTP requests into the simulation with SimAwsHttp, controlling simulated time, matching service errors by name, and handling properties Yulin refuses to simulate. Use when writing or reviewing tests that touch AWS, when replacing aws-sdk-client-mock or hand-rolled AWS stubs, when a CDK stack needs testing, when a CloudFront Distribution, its DNS records or its certificate need testing, when test setup around Yulin is growing helper classes or wrapper functions, and when Yulin refuses a template property or an SDK command.
 license: Apache-2.0
 metadata:
-  version: "1.15.0"
+  version: "1.16.0"
 ---
 
 # Testing with Yulin
@@ -213,6 +213,33 @@ scope has), so look on the other scope before concluding a service is missing. E
 plain `{ input: { ... } }` in place of a Command object. An assertion can therefore read a service
 back without adding an `@aws-sdk/client-*` package the production code has no use for.
 
+## Drive requests into the simulation
+
+Reading state back covers the resources. `SimAwsHttp` from `@kensio/yulin/serve` covers the path
+through them, by sending a request into the environment with nothing listening. It takes what the
+global `fetch` takes and answers with a `Response`:
+
+```typescript
+const http = new SimAwsHttp({ simAws });
+const response = await http.fetch("https://www.example.test/docs/x?a=1", { redirect: "manual" });
+
+// Then the apex redirect the CloudFront Function performs has been applied.
+expect(response.status).toBe(301);
+expect(response.headers.get("location")).toBe("https://example.test/docs/x?a=1");
+```
+
+A hostname simulated Route 53 answers for is requested by its own name, with no port to add and no
+`localUrl(...)` adapting (an `https` URL works with no certificate set up for it). That one request
+resolves the hostname, finds the Distribution its alias records point at, and runs the deployed
+CloudFront Function at viewer-request. The certificate, the Hosted Zone records, the Distribution's
+aliases and the function are covered together. A template assertion over the same stack passes with
+every Route 53 record missing.
+
+Reach for `serveSimAws` when the request comes from outside the process, such as a browser, `curl`
+or an SDK client pointed at a local endpoint. Both go through the same routing and service code, and
+`SimAwsHttp` leaves parallel test files no port to collide over. See
+[the serving docs](https://yulinsim.dev/serve/) for the API.
+
 ## Match service errors by name
 
 ```typescript