@evident-ai/runner-cdk 0.1.1-dev.04f2155 → 0.1.1-dev.15755a4

package/README.md

@@ -112,7 +112,7 @@ the construct's own dogfooding consumer.
 
 This construct never builds an image. Pass any `ecs.ContainerImage` — from a registry, or
 built from a `Dockerfile` you control. The generic runner image lives separately in
-`packages/runner-image`, so you can adopt the image, the construct, or both.
+`runner/docker-images/fargate`, so you can adopt the image, the construct, or both.
 
 ## The MicroVM image
 

package/dist/evident-scale-to-zero-construct.js

@@ -101,7 +101,7 @@ class EvidentScaleToZeroConstruct extends constructs_1.Construct {
             // --endpoint / --tunnel). The agent is resolved from EVIDENT_AGENT_KEY.
             EVIDENT_API_URL: evidentApiUrl,
             EVIDENT_TUNNEL_URL: evidentTunnelUrl,
-            // Litestream replica target (read by packages/runner-synchroniser, which
+            // Litestream replica target (read by runner/synchroniser, which
             // generates /etc/evident/litestream.yml at boot).
             LITESTREAM_BUCKET: replicaBucket.bucketName,
             LITESTREAM_PREFIX: this.replicaPrefix,

package/dist/microvm/constants.js

@@ -1,9 +1,8 @@
 "use strict";
 // Shared literals for the MicroVM controller and for the image it launches.
 // Every module imports from here rather than restating a value that must match
-// across them — including `microvm/image/hook-server.ts`, which runs inside the
-// image and is esbuild-bundled into the published build context by
-// `scripts/build.ts`, so these values reach the image as inlined constants.
+// across them. The image template pins matching copies, guarded by
+// `microvm/image/dockerfile.test.ts`.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.MICROVM_MAX_RUN_SECONDS = exports.SUSPENDING_POLL_INTERVAL_MS = exports.SUSPENDING_POLL_ATTEMPTS = exports.RUN_HOOK_PAYLOAD_MAX_BYTES = exports.HOOK_TIMEOUT_SECONDS = exports.HOOKS_DIR = exports.HOOKS_PORT = void 0;
 // The port the image's hook server binds, baked into the published Dockerfile

package/dist/microvm/controller/handle-doorbell.js

@@ -2,7 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.handleDoorbell = handleDoorbell;
 const node_crypto_1 = require("node:crypto");
-const webhook_signature_1 = require("@evident/webhook-signature");
+const sdk_1 = require("@evident/sdk");
 const constants_1 = require("../constants");
 const doorbell_1 = require("./doorbell");
 const throttle_retry_1 = require("./throttle-retry");
@@ -175,7 +175,7 @@ async function shouldRecreateForNewerImage(doorbell, shape, runningVersion, micr
     return compareImageVersions(running, latest) < 0;
 }
 async function handleDoorbell({ rawBody, signatureHeader, doorbellSecret, shapes, microvm, sleep, random, }) {
-    if (!(0, webhook_signature_1.verifyWakeSignature)(rawBody, signatureHeader, doorbellSecret)) {
+    if (!(0, sdk_1.verifyEvidentSignature)(rawBody, signatureHeader, doorbellSecret)) {
         return decide({
             statusCode: 401,
             action: 'rejected',

package/dist/microvm/controller/microvm-client.d.ts

@@ -49,7 +49,7 @@ export interface MicrovmClient {
      * (docs/spikes/lambda-microvms-phase0/README.md). AWS's own Claude-agents
      * guidance recommending `maxIdleDurationSeconds: 120` targets VMs reached
      * inbound and does not apply here. Idle is instead decided IN the VM by
-     * `evident run --idle-timeout` (packages/runner-cdk/microvm-image/hooks/common.sh's
+     * `evident run --idle-timeout` (runner/docker-images/microvm/hooks/common.sh's
      * `IDLE_TIMEOUT_SECONDS`), whose clean exit drives this
      * client's own `suspend()` via the `runner.suspend_requested` doorbell.
      */

package/dist/microvm-image-context/Dockerfile

@@ -204,9 +204,12 @@ RUN git reset --quiet
 # database stay per-VM (see entrypoint.sh's pre-warm in evident-runner).
 RUN if [ -f pnpm-lock.yaml ]; then \
       pnpm install --frozen-lockfile \
-      && pnpm run build --filter='./packages/*'; \
+      && pnpm run build --filter='./packages/*' \
+        --filter='./aws/runner-cdk' \
+        --filter='./aws/lambda-microvm-cdk' \
+        --filter='./aws/lambda-microvm-runtime'; \
     else \
-      echo "[workspace-prep] no pnpm-lock.yaml in the baked repository — skipping the dependency install and the packages build; the agent installs on first use."; \
+      echo "[workspace-prep] no pnpm-lock.yaml in the baked repository — skipping the dependency install and the workspace build; the agent installs on first use."; \
     fi
 
 # Data dir for the local dev Postgres cluster; listens on 5433 to match this

package/dist/microvm-image-context/hook-server.js

@@ -275,14 +275,10 @@ var require_dist = __commonJS({
   }
 });
 
-// src/microvm/image/hook-server.ts
+// ../../runner/docker-images/microvm/hook-server.ts
 var import_lambda_microvm_runtime = __toESM(require_dist());
-
-// src/microvm/constants.ts
-var HOOKS_PORT = 8080;
 var HOOKS_DIR = "/etc/evident/hooks";
-
-// src/microvm/image/hook-server.ts
+var HOOKS_PORT = 8080;
 var server = (0, import_lambda_microvm_runtime.createNodeRuntime)({ hooksDir: HOOKS_DIR });
 var port = Number(process.env.HOOKS_PORT ?? HOOKS_PORT);
 server.listen(port, "0.0.0.0", () => {

package/dist/microvm-image-context/hooks/common.sh

@@ -2,8 +2,8 @@
 # Sourced by every hook script. Nothing here runs at image build time.
 #
 # These hooks are the SECOND shell speaking the runner-synchroniser CLI contract
-# (packages/runner-image/entrypoint.sh is the first), so both are held to it by
-# packages/runner-synchroniser/src/shell-contract.test.ts — which derives what
+# (runner/docker-images/fargate/entrypoint.sh is the first), so both are held to it by
+# runner/synchroniser/src/shell-contract.test.ts — which derives what
 # `run_synchroniser` below must handle from the subcommands this shell calls.
 
 # Installed from npm by the image (docker/Dockerfile's ARG
@@ -57,7 +57,7 @@ error() { echo "[hook:$(basename "$0")] ERROR: $*" >&2; }
 # Returns the CLI's own exit code. Domain outcomes (nothing persisted yet, a
 # corrupt object) are LOGGED and exit 0, the predicates answer "no" with 10, and
 # `session-db-classify`'s three typed answers are 30 (fatal)/31 (replica
-# unusable)/32 (retry) — see `packages/runner-synchroniser/src/cli.ts`'s own
+# unusable)/32 (retry) — see `runner/synchroniser/src/cli.ts`'s own
 # comment for what each means, not restated here. Any OTHER non-zero status
 # means the tool itself broke, which is the only case worth an ERROR here —
 # EXCEPT 124/137 (a `timeout` deadline/SIGKILL) when the caller asked for one:
@@ -171,7 +171,7 @@ timed_synchroniser() {
 }
 
 # Exports what `runner-synchroniser` resolves its object-store location from
-# (packages/runner-synchroniser/src/config.ts). It treats either being empty as
+# (runner/synchroniser/src/config.ts). It treats either being empty as
 # "persistence disabled" and then reports every restore as a WARNING it still
 # exits 0 for — so an unset value has to be caught HERE, where it can still be
 # told apart from "the store is simply empty".
@@ -441,7 +441,7 @@ sync_credentials() {
 # Writes NOTHING to S3 itself; replication back to S3 is started separately by
 # `start_litestream` (below) from the `run`/`resume` hooks. `ensure_litestream_config`/
 # `restore_session_db` are the MicroVM side of the same contract
-# packages/runner-image/entrypoint.sh's inlined restore already speaks, going
+# runner/docker-images/fargate/entrypoint.sh's inlined restore already speaks, going
 # through the SAME runner-synchroniser CLI.
 
 # Reads the ~30 MB litestream binary into the page cache, in the background, so
@@ -624,7 +624,7 @@ restore_session_db() {
     return 0
   }
 
-  # #931's exact lesson, one shell over (packages/runner-image/entrypoint.sh):
+  # #931's exact lesson, one shell over (runner/docker-images/fargate/entrypoint.sh):
   # the `|| { ... }` above only catches a non-zero EXIT — an `env` that exits
   # 0 with an INCOMPLETE contract (a runner-synchroniser version/build skew)
   # would otherwise abort right here under `set -u` the moment
@@ -681,7 +681,7 @@ restore_session_db() {
   esac
 
   local classify_rc=0
-  run_synchroniser session-db-classify "${restore_rc}" 1 --on-unusable-replica=leave || classify_rc=$?
+  run_synchroniser session-db-classify "${restore_rc}" 1 --on-unusable-replica=leave --fresh-db-fallback || classify_rc=$?
   case "${classify_rc}" in
     0) ;; # restored, or no replica yet — the CLI already logged which
     31)
@@ -691,8 +691,8 @@ restore_session_db() {
       # half-restored DB, so the marker stays; a 31 is structurally guaranteed
       # to be a FRESH one, and replicating it starts a new backup chain instead
       # of leaving this boot with a zero-width backup window. Same reasoning,
-      # and same one-line change, as packages/runner-image/entrypoint.sh's `31)`.
-      warn "SESSION-DB-REPLICA-UNUSABLE: booting with a fresh opencode.db and starting a fresh backup chain this boot (see the WARNING above)"
+      # and same one-line change, as runner/docker-images/fargate/entrypoint.sh's `31)`.
+      warn "SESSION-DB-REPLICA-UNUSABLE: booting with a fresh opencode.db and replicating into the existing prefix this boot (see the WARNING above)"
       ;;
     32)
       # The CLI's own contract for 32 is "re-run litestream restore and ask
@@ -1122,7 +1122,7 @@ flush_session_db() {
 # returned its 200, so it is deliberately outside that arithmetic.
 #
 # EVIDENT_IDLE_TIMEOUT_SECONDS, deliberately the SAME env var name
-# packages/runner-image/entrypoint.sh uses for the ECS runner's own
+# runner/docker-images/fargate/entrypoint.sh uses for the ECS runner's own
 # idle-timeout flag, so an operator who knows one knows the other. A
 # non-numeric override must never silently DROP the flag — that degrades to
 # an always-on VM burning ~$2.40/day, exactly the bug this closes — so it
@@ -1161,7 +1161,7 @@ start_tunnel() {
   # into a MicroVM, so it is the ONLY way to seed model credentials on a runner
   # that is already up — the S3 credential store is read at /run and /resume,
   # never mid-life. The allow-list stays a single directory, as on ECS
-  # (packages/runner-image/entrypoint.sh): the flag is repeatable, but every
+  # (runner/docker-images/fargate/entrypoint.sh): the flag is repeatable, but every
   # extra entry widens what Evident can write into a VM that executes agent
   # code. ${HOME} is set by the image (ENV HOME=/home/runner) and `set -u` makes
   # an unset one abort rather than silently allow-list "/.claude".
@@ -1208,7 +1208,7 @@ CLI_SHUTDOWN_CEILING_SECONDS=32
 # everything else in the hook. 10 s is ~4x the measured shutdown and gives a
 # provable worst case of 10 + the 10 s `suspend` spends in sync_credentials
 # before us = 20 s, inside the ~55 s the in-VM server allows this script
-# (DEFAULT_TIMEOUT_SECONDS, packages/lambda-microvm-runtime/src/runtime.ts),
+# (DEFAULT_TIMEOUT_SECONDS, aws/lambda-microvm-runtime/src/runtime.ts),
 # itself inside AWS's 60 s (HOOK_TIMEOUT_SECONDS, src/constants.ts) —
 # overrunning that fails the whole lifecycle transition, which is worse than the
 # kill this replaces. The residual cost is a drain longer than 10 s being

package/dist/microvm-image-context/hooks/resume

@@ -61,7 +61,7 @@ start_litestream
 # measures in ~2 s (see the waker note in common.sh).
 #
 # Safe to leave running past the hook's own exit: the runtime waits on the
-# script's `'exit'`, not `'close'` (packages/lambda-microvm-runtime/src/
+# script's `'exit'`, not `'close'` (aws/lambda-microvm-runtime/src/
 # runtime.ts), so a lingering child never delays the HTTP response. Its stdio
 # is deliberately NOT redirected — that inherited fd is how the RUNNER-KEY-*
 # line reaches CloudWatch, which is the whole point of running it at all.

package/dist/waker/construct.js

@@ -56,7 +56,7 @@ class EvidentWaker extends constructs_1.Construct {
             runtime: lambda.Runtime.NODEJS_22_X,
             // Pre-bundled at PACKAGE build time (`pnpm --filter @evident-ai/runner-cdk
             // build`, see scripts/build.ts), not at synth time: esbuild inlines
-            // @evident/webhook-signature's HMAC verifier into
+            // @evident/sdk's HMAC verifier into
             // dist/waker-lambda/handler.js, so neither this package's published npm
             // artifact (which ships dist/ already built) nor a consuming app needs
             // that private workspace package, or esbuild, on synth's PATH. Requires

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evident-ai/runner-cdk",
-  "version": "0.1.1-dev.04f2155",
+  "version": "0.1.1-dev.15755a4",
   "description": "Reusable CDK constructs for an Evident agent runner: a single scale-to-zero Fargate runner (task + service + per-agent self-stop role + waker Lambda), or a per-session AWS Lambda MicroVM that boots on demand and suspends between messages. Instantiate once per agent from your own stack.",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -15,14 +15,14 @@
   ],
   "scripts": {
     "build": "pnpm run build-bundled-deps && ts-node scripts/build.ts",
-    "//build-bundled-deps": "scripts/build.ts esbuild-bundles src/microvm/image/hook-server.ts, which imports @evident-ai/lambda-microvm-runtime by its built `main`. @evident-ai/lambda-microvm-cdk is a workspace:* devDependency whose types resolve through its own dist/, so tsc --project tsconfig.build.json cannot compile src/microvm/{shapes,construct}.ts without it. Chained into `build` rather than left to turbo's `^build` because publish-runner-cdk.yaml and infrastructure/evident-runner's build-runner-cdk-dep invoke `pnpm --filter @evident-ai/runner-cdk build` directly, which bypasses turbo entirely.",
+    "//build-bundled-deps": "scripts/build.ts esbuild-bundles runner/docker-images/microvm/hook-server.ts, which imports @evident-ai/lambda-microvm-runtime by its built `main`. @evident-ai/lambda-microvm-cdk is a workspace:* devDependency whose types resolve through its own dist/, so tsc --project tsconfig.build.json cannot compile src/microvm/{shapes,construct}.ts without it. Chained into `build` rather than left to turbo's `^build` because publish-runner-cdk.yaml and infrastructure/evident-runner's build-runner-cdk-dep invoke `pnpm --filter @evident-ai/runner-cdk build` directly, which bypasses turbo entirely.",
     "build-bundled-deps": "pnpm --filter @evident-ai/lambda-microvm-cdk build && pnpm --filter @evident-ai/lambda-microvm-runtime build",
     "typecheck": "tsc --noEmit",
     "test": "node --test --require ts-node/register 'src/**/*.test.ts'",
     "format": "prettier --write 'src/**/*.ts'",
     "lint": "eslint 'src/**/*.ts' --max-warnings=0"
   },
-  "//peerDependencies": "@evident-ai/lambda-microvm-cdk is a registry range here, never workspace:*: publish-runner-cdk.yaml ships this package with `npm publish`, not `pnpm publish`, so pnpm's workspace-protocol substitution never runs and a workspace: range would reach npm literally, breaking every external install. Enforced by infrastructure/evident-runner/src/runner-cdk-published-surface.test.ts. The matching devDependency is workspace:* so this monorepo's own build compiles against packages/lambda-microvm-cdk's source.",
+  "//peerDependencies": "@evident-ai/lambda-microvm-cdk is a registry range here, never workspace:*: publish-runner-cdk.yaml ships this package with `npm publish`, not `pnpm publish`, so pnpm's workspace-protocol substitution never runs and a workspace: range would reach npm literally, breaking every external install. Enforced by src/published-surface.test.ts. The matching devDependency is workspace:* so this monorepo's own build compiles against aws/lambda-microvm-cdk's source.",
   "peerDependencies": {
     "@evident-ai/lambda-microvm-cdk": "^0.1.1",
     "aws-cdk-lib": "^2.240.0",
@@ -34,14 +34,15 @@
     "@aws-sdk/client-secrets-manager": "^3.682.0",
     "@evident-ai/lambda-microvm-cdk": "workspace:*",
     "@evident-ai/lambda-microvm-runtime": "workspace:*",
-    "@evident/webhook-signature": "workspace:*",
+    "@evident/sdk": "workspace:*",
     "@types/node": "^22",
     "aws-cdk-lib": "^2.240.0",
     "constructs": "^10.5.0",
     "esbuild": "^0.25.2",
     "prettier": "^3.3.3",
     "ts-node": "^10.9.2",
-    "typescript": "^5.6.3"
+    "typescript": "^5.6.3",
+    "runner-microvm-image": "workspace:*"
   },
   "publishConfig": {
     "access": "public"
@@ -49,7 +50,7 @@
   "repository": {
     "type": "git",
     "url": "https://github.com/sroze/evident.git",
-    "directory": "packages/runner-cdk"
+    "directory": "aws/runner-cdk"
   },
   "homepage": "https://evident.run",
   "author": "Evident <hello@evident.run>",