@evident-ai/runner-cdk 3.4.1-dev.51df4de → 3.4.1-dev.c03b461

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

@@ -1,14 +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. The interval credential sync loop (#1868 WI-3) is the
-# same story one function over: /suspend stops it too, so a resumed VM that
-# never restarted it here would never sync credentials again for the rest of
-# its life.
+# 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
@@ -44,11 +41,9 @@ 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

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

@@ -52,24 +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. Same for the
-# aws CLI: step 4's runner-secret fetch is its first-ever invocation in this
-# VM's life, and #1997 measured that cold first touch alone blowing the whole
-# credential-restore deadline.
+# 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
@@ -77,49 +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"
-
-# 7 — integrity-check the restored DB (#1868 WI-4), after the config file
-# exists (verify_session_db reads it) and before anything opens the DB —
-# the only window in which that's true. The ONE step in this sequence that
-# can still fail /run past the runner-key gate: a 34 means the corrupt DB's
-# separation/disposal could not be proven safe (see verify_session_db's own
-# comment for why that's a deliberate exception to "nothing about the
-# session DB may ever fail /run").
-verify_session_db || exit 1
-
-# 8 — apply the overlay before OpenCode resolves its project configuration.
-apply_runner_opencode_config
-
-# 9 — configure git after credentials are restored and before agent shells start.
-configure_github_access
-
-# 10 — 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
-
-# 11 — 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
-
-# 11a — the interval credential sync (#1868 WI-3), matching ECS's own
-# post-litestream position. Bare for the same reason: every guard inside
-# start_credential_sync is its own `return 0`.
+# 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
 
-# 12 — 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
@@ -131,6 +89,6 @@ start_credential_sync
 # 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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evident-ai/runner-cdk",
-  "version": "3.4.1-dev.51df4de",
+  "version": "3.4.1-dev.c03b461",
   "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",