@go-to-k/cdkd 0.79.0 → 0.81.0

package/README.md

@@ -498,17 +498,19 @@ Lambda Runtime Interface Emulator (RIE). Modeled on `sam local invoke`
 but reusing cdkd's synthesis / asset / construct-path plumbing — no
 `template.yaml` to maintain, no `cdk synth | sam ...` round-trip.
 
-Requires Docker. Supports Node.js, Python, Ruby, Java, and .NET runtimes
+Requires Docker. Supports every current AWS Lambda runtime
 (`nodejs18.x` / `nodejs20.x` / `nodejs22.x` / `nodejs24.x` / `python3.11` /
 `python3.12` / `python3.13` / `python3.14` / `ruby3.2` / `ruby3.3` /
-`java8.al2` / `java11` / `java17` / `java21` / `dotnet6` / `dotnet8`);
-other runtimes (Go / `provided.*`) are not yet supported. Java and .NET
-Lambdas are **asset-backed only** — the Handler shape names a compiled
-artifact (`package.Class::method` for Java's JVM class;
-`Assembly::Namespace.Class::Method` for .NET's CLR assembly), so use
-`lambda.Code.fromAsset(<dir>)` with a directory containing the compiled
-output (`.class` hierarchy / `.jar` / `.dll`); inline `Code.ZipFile` is
-rejected with a clear routing message.
+`java8.al2` / `java11` / `java17` / `java21` / `dotnet6` / `dotnet8` /
+`provided.al2` / `provided.al2023`). The deprecated `go1.x` runtime is
+rejected with a migration pointer to `provided.al2023`. Java, .NET, and
+`provided.*` Lambdas are **asset-backed only** — the Handler shape names
+a compiled artifact (`package.Class::method` for Java's JVM class;
+`Assembly::Namespace.Class::Method` for .NET's CLR assembly; an
+arbitrary `bootstrap` binary for the OS-only `provided.*` runtimes), so
+use `lambda.Code.fromAsset(<dir>)` with a directory containing the
+compiled output (`.class` hierarchy / `.jar` / `.dll` / native binary);
+inline `Code.ZipFile` is rejected with a clear routing message.
 
 **Container Lambdas** — `lambda.DockerImageFunction(...)` /
 `Code.ImageUri` is supported alongside ZIP Lambdas. cdkd reads the
@@ -582,12 +584,16 @@ containers `cdkd local invoke` uses. Modeled on `sam local start-api`
 but reusing cdkd's synthesis / route-discovery plumbing.
 
 ```bash
-# Auto-allocate a port (printed at startup) and serve every discovered route
+# Auto-allocate one port PER discovered API (printed at startup)
 cdkd local start-api
 
-# Pin to port 3000 (SAM-parity / curl muscle memory)
+# Pin the FIRST server to port 3000; subsequent APIs get 3001, 3002, ...
 cdkd local start-api --port 3000
 
+# Restrict to a single API by its CDK logical id (HTTP API / REST API logical
+# id, or the backing Lambda's logical id for Function URLs)
+cdkd local start-api --api MyAdminApi
+
 # Pre-warm one container per Lambda at server boot — eliminates first-request cold start
 cdkd local start-api --warm
 
@@ -604,6 +610,13 @@ cdkd local start-api --watch
 cdkd local start-api --stage prod
 ```
 
+**One server per API** (since v0.81): every discovered API surface gets its
+own HTTP server on its own port, so authorizers, CORS configs, and stage
+variables stay scoped to the owning API and never bleed across APIs that
+happen to share a path. `cdkd local start-api` prints one
+`Server listening on http://<host>:<port>  (<API> (<kind>))` line per
+server at startup; pass `--api <id>` to launch only one of them.
+
 Scope: REST v1 + HTTP API + Function URL with AWS_PROXY integrations.
 Authorizers (Lambda TOKEN/REQUEST + Cognito User Pool + HTTP v2 JWT),
 VPC-config Lambda warnings, CORS preflight, hot reload, and stage