@evident-ai/runner-cdk 3.5.2-dev.f258bd6 → 3.5.2-dev.f80111b

package/README.md

@@ -113,6 +113,7 @@ For the full end-to-end walkthrough for this construct, see
 | `gitUserName` / `gitUserEmail` | `string?` | Optional git identity for agent commits. |
 | `extraImageEnvironment` | `Record<string,string>?` | Non-secret values baked into every VM launched from the image version. |
 | `evidentApiUrl` / `evidentRunnerId` | `string?` | Supply both to report published image versions to Evident, or omit both. |
+| `imageVersionPruning` | `boolean?` | Opts into construct-owned pruning for this deployment's images. Uses the engine defaults; omitting it creates no pruning resources. |
 
 The `DoorbellSecret` CloudFormation logical ID remains stable for Evident's own
 default stack. It identifies the deployed secret resource, not the customer-facing
@@ -137,19 +138,27 @@ built from a `Dockerfile` you control. The generic runner image lives separately
 
 ### Prune image versions
 
-MicroVM image versions are quota-bound. `@evident-ai/lambda-microvm-cdk` ships the
-`prune-microvm-image-versions` CLI; enable it with one `package.json` script line:
+MicroVM image versions are quota-bound. Opt into construct-owned pruning with one
+property:
 
-```json
-"microvm:prune": "prune-microvm-image-versions --image-arn arn:aws:lambda:eu-west-1:000000000000:microvm-image:your-image"
+```ts
+new EvidentMicrovmConstruct(this, 'Runner', {
+  // ...other required MicroVM props
+  imageVersionPruning: true,
+});
 ```
 
-See the `@evident-ai/lambda-microvm-cdk` package README for the CLI flags and safety semantics.
+This bounds the per-image version quota (`L-F8BECE9C`) for this deployment's shapes only.
+Retention follows the engine defaults, and pruning runs before the image publish for the
+deploy that invokes it. The custom-resource Lambda writes per-image verdicts and a summary
+to CloudWatch Logs. Use the `prune-microvm-image-versions` CLI for deployments that do not
+use this construct or that need non-default retention; see the
+`@evident-ai/lambda-microvm-cdk` package README for its flags and safety semantics.
 
 `EvidentMicrovmConstruct`'s `buildContextPath` is a **local directory** holding the
 Dockerfile you control and everything it copies. `cdk deploy` zips and uploads that
 directory, and the Lambda MicroVM service builds the image in *your* account. Start the
-Dockerfile from a pinned `ghcr.io/sroze/evident-microvm-base:X.Y.Z` tag; the base image
+Dockerfile from a pinned `ghcr.io/sroze/evident-microvm-base:sha-3f3949d` tag; the base image
 contains the hook server, lifecycle hooks and common agent tooling.
 
 `stageMicrovmBuildContext()` combines your build-context directory with a full checkout