@evident-ai/runner-cdk 0.1.1-dev.da88f8e → 3.4.1-dev.0ef5061

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

@@ -1,11 +1,11 @@
 #!/usr/bin/env bash
 #
 # Re-dial with the identity /run left behind. There is no step that could fetch
-# a fresh runner key, so the one from /run is what resumes. Also restarts the
-# session-DB replicator /suspend stopped before the snapshot (#812 WI-4):
-# litestream does not survive a suspend/resume freeze on this design (Q2) —
-# /suspend stops it and /resume starts a fresh one, the same pattern already
-# proven for the tunnel.
+# a fresh runner key, so the one from /run is what resumes. The CLI delegated by
+# start_tunnel owns the session-DB replicator's post-resume start. The interval
+# credential sync loop (#1868 WI-3) stays here because /suspend stops it too, so
+# a resumed VM that never restarted it here would never sync credentials again
+# for the rest of its life.
 set -euo pipefail
 
 # shellcheck source=./common.sh
@@ -41,11 +41,10 @@ fi
 
 # Tolerant, never fatal: a resume that fails costs the user their whole
 # session, so a broken durable-state config degrades to "no session-DB
-# restart" rather than a failed resume (the same Q3 reasoning /run's
-# session-DB step follows). start_litestream's own guards (disabled/marker/
-# already-running) handle the rest — this needs no logic of its own.
+# replication" rather than a failed resume. The CLI's own guards handle the
+# rest — this needs no logic of its own.
 load_state_config || warn "could not resolve durable-state config; the session DB will not resume replicating"
-start_litestream
+start_credential_sync
 
 # Diagnostic-only, unlike /run's gate: a failed resume costs the user their
 # whole session, so this never exits — it only converts a silent "resumed but
@@ -61,7 +60,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/microvm-image-context/hooks/run

@@ -28,6 +28,7 @@ cleanup() {
   stop_tunnel || warn "stop_tunnel failed while cleaning up"
   stop_opencode || warn "stop_opencode failed while cleaning up"
   kill_litestream || warn "kill_litestream failed while cleaning up"
+  stop_credential_sync || warn "stop_credential_sync failed while cleaning up"
 }
 trap cleanup EXIT
 
@@ -51,20 +52,20 @@ regenerate_machine_id
 # reads it, and left behind for the hooks that flush back to the same prefix.
 printf '%s\n' "${state_prefix}" >"${STATE_PREFIX_FILE}"
 
-# 3 — start reading the litestream binary NOW so that read overlaps step 4,
-# which needs a different binary (node), instead of landing inside step 5, which
-# start_opencode has to wait for. Backgrounded and never waited on.
+# 3 — start reading the litestream and aws CLI binaries NOW. The reads run in
+# the background and overlap the CLI's own node startup and auth round trip,
+# keeping their cold first touches off the path to the first credential fetch.
 prewarm_litestream
+prewarm_aws_cli
 
-# 4 — credential stores, restored before anything that reads them starts. Fatal
-# only if persistence itself is unavailable (an unset bucket/prefix, or a broken
-# synchroniser bundle) — a VM with no model credentials yet still boots.
-restore_credentials
+# 4 — export the durable-state config before anything that reads it. Fatal,
+# because the CLI and the teardown hooks must agree on this runner's state prefix.
+load_state_config || exit 1
 
 # 5 — does the runner key in this payload actually authenticate against
-# Evident? Checked here, before opencode or the tunnel spend any of this boot's
-# SIGTERM budget on a key that cannot work, and before anything has started
-# that cleanup would need to tear down. Fatal ONLY on contrary evidence
+# Evident? Checked here, before the tunnel spends any of this boot's time on a key
+# that cannot work, and before anything has started that cleanup would need to
+# tear down. Fatal ONLY on contrary evidence
 # (check_runner_key's own contract, common.sh): a key the API actively rejects
 # cannot work regardless, and failing here costs ~5s against the ~10 minutes a
 # runner that can never connect would otherwise burn before the lifecycle cron
@@ -72,29 +73,11 @@ restore_credentials
 # it warns and this VM still boots.
 check_runner_key "${runner_key}" "${api_url}" || exit 1
 
-# 6 — the OpenCode session DB (#812 WI-2), restored before opencode opens it —
-# the only place this can happen. Bare, like restore_credentials above:
-# restore_session_db never returns non-zero (Q3 — nothing about the session
-# DB may ever fail /run), so there is deliberately no `||` here to catch.
-restore_session_db
-log "session DB restore done ${SECONDS}s into the hook"
+# 6 — the interval credential sync (#1868 WI-3). It stays before the context file
+# is written. Bare: every guard inside start_credential_sync is its own `return 0`.
+start_credential_sync
 
-# 7 — opencode. Started here, not at build time: a warm process in the shared
-# snapshot would carry its installation id and database into every VM. Not
-# waited on: a slow opencode boot is not a reason to fail /run (the tunnel CLI
-# auto-starts opencode when it finds none healthy,
-# apps/cli/src/commands/ensure-opencode.ts, and the api-worker lifecycle cron
-# reclaims a runner that never comes online).
-start_opencode
-
-# 8 — begin replicating the session DB (#812 WI-3), now that opencode has
-# opened it and before any work can arrive over the tunnel. Bare, like
-# restore_session_db above: start_litestream never returns non-zero (every
-# guard inside it is its own `return 0`), so there is nothing here for
-# `set -e` to abort on.
-start_litestream
-
-# 9 — the first per-VM identity on the wire. The subshell's umask makes the file
+# 7 — the first per-VM identity on the wire. The subshell's umask makes the file
 # unreadable to anyone else from the moment it exists, before the key is in it.
 (
   umask 077
@@ -106,6 +89,6 @@ start_litestream
 # attempt cap (apps/cli/src/lib/tunnel/connection.ts), and a control-plane
 # reclaim pass (the api-worker lifecycle cron) is what decides whether a
 # runner that never connects gets suspended.
-start_tunnel "${runner_key}" "${api_url}" "${tunnel_url}"
+start_tunnel "${runner_key}" "${api_url}" "${tunnel_url}" true true
 
 run_succeeded=true

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

@@ -8,6 +8,9 @@ set -euo pipefail
 # shellcheck source=./common.sh
 source "$(dirname "$0")/common.sh"
 
+# Stopped BEFORE the boundary flush (#1868 WI-3): the interval loop and this
+# flush must not race each other on the same credential stores.
+stop_credential_sync
 sync_credentials
 stop_tunnel
 

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

@@ -8,6 +8,9 @@ set -uo pipefail
 # shellcheck source=./common.sh
 source "$(dirname "$0")/common.sh"
 
+# Stopped BEFORE the boundary flush (#1868 WI-3): the interval loop and this
+# flush must not race each other on the same credential stores.
+stop_credential_sync
 sync_credentials
 stop_tunnel
 

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.da88f8e",
+  "version": "3.4.1-dev.0ef5061",
   "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,13 +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`. Chained into `build` rather than left to turbo's `^build` because publish-runner-cdk.yaml invokes `pnpm --filter @evident-ai/runner-cdk build` directly, which bypasses turbo entirely.",
-    "build-bundled-deps": "pnpm --filter @evident-ai/lambda-microvm-runtime build",
+    "//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 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",
@@ -31,16 +32,17 @@
     "@aws-sdk/client-ecs": "^3.682.0",
     "@aws-sdk/client-lambda-microvms": "^3.1095.0",
     "@aws-sdk/client-secrets-manager": "^3.682.0",
-    "@evident-ai/lambda-microvm-cdk": "^0.1.1",
+    "@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"
@@ -48,9 +50,9 @@
   "repository": {
     "type": "git",
     "url": "https://github.com/sroze/evident.git",
-    "directory": "packages/runner-cdk"
+    "directory": "aws/runner-cdk"
   },
   "homepage": "https://evident.run",
-  "author": "Evident <contact@evident.run>",
+  "author": "Evident <hello@evident.run>",
   "license": "MIT"
 }