@evident-ai/runner-synchroniser 3.2.0 → 3.2.1-dev.0fe02fb

package/README.md

@@ -15,10 +15,9 @@ the boot script gates on. It also renders the `litestream.yml` that covers the s
 database, so both halves read their bucket, prefix and paths from one config module
 instead of two.
 
-It is a CLI, not a library, invoked by two consumers that differ in how they get the
-binary: the Fargate runner image installs the published package and invokes it by name
-(`runner-synchroniser <command>`); the MicroVM still builds it from source and runs the
-bundle directly (`node cli.js <command>`).
+It is a CLI, not a library, invoked by two consumers — the Fargate runner image and the
+MicroVM image — both of which install the published package and invoke it by name
+(`runner-synchroniser <command>`).
 
 ## Install
 
@@ -46,11 +45,9 @@ overwrites it before every publish. This is why `latest` jumped straight from
 major-version story, and because npm publishes are immutable that jump is
 permanent.
 
-The two consumers still differ in how they get the binary: the Fargate runner
-image installs the published package
-(`ARG RUNNER_SYNCHRONISER_VERSION=dev`, resolved to a concrete version by the
-deploy workflow); the MicroVM still builds it from source and reads no npm
-version at all.
+Both consumers install the published package behind the same
+`ARG RUNNER_SYNCHRONISER_VERSION=dev`, resolved to a concrete version at image
+build time.
 
 ## Commands
 
@@ -434,10 +431,11 @@ pnpm lint
 From the repository root, prefix with `pnpm --filter @evident-ai/runner-synchroniser`.
 
 The bundle must stay a **single file**: both consumers need a self-contained
-`dist/cli.js` with no sibling chunks — the npm `files: ["dist"]` install ships
-whatever `dist` contains, and the MicroVM runs `dist/cli.js` directly with no
-`node_modules` alongside it. `tsup.config.ts` disables splitting and bundles the
-AWS SDK so neither consumer needs anything else.
+`dist/cli.js` with no sibling chunks — both the Fargate runner image and the
+MicroVM image install this package from npm as a `bin`, where `files: ["dist"]`
+ships whatever `dist` contains, with no `node_modules` alongside it.
+`tsup.config.ts` disables splitting and bundles the AWS SDK so neither consumer
+needs anything else.
 
 The restore/sync/CLI tests need neither AWS nor a real filesystem — rather than shimming
 a fake `aws` binary onto `PATH`, they inject two ports: `InMemoryObjectStore` (in

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evident-ai/runner-synchroniser",
-  "version": "3.2.0",
+  "version": "3.2.1-dev.0fe02fb",
   "description": "Restores and syncs the Evident runner's OpenCode credential stores (and litestream config) to an object store, so a runner survives task replacement with almost no state loss.",
   "type": "module",
   "main": "./dist/cli.js",