@evident-ai/runner-synchroniser 0.1.0 → 0.1.1-dev.b352795

package/README.md

@@ -15,8 +15,10 @@ 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: the runner's `entrypoint.sh` invokes it as a single
-self-contained bundle (`node cli.js <command>`).
+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>`).
 
 ## Install
 
@@ -32,9 +34,9 @@ the AWS SDK is bundled at build time, so installing it pulls nothing else in.
 
 > Publishing is being rolled out (#612). The `dev` tag is published on every merge to
 > `main` that touches this package; the first publish is a human bootstrap (#694), and
-> the `latest`-on-release path is not wired up yet. Nothing in this repo installs the
-> package: the runner image and the MicroVM still build the bundle from source, and will
-> keep doing so until that flip lands.
+> the `latest`-on-release path is not wired up yet. The Fargate runner image installs
+> the `dev`-tagged package (`ARG RUNNER_SYNCHRONISER_VERSION=dev`); the MicroVM still
+> builds the bundle from source and is not expected to change.
 
 ## Commands
 
@@ -171,10 +173,11 @@ pnpm lint
 
 From the repository root, prefix with `pnpm --filter @evident-ai/runner-synchroniser`.
 
-The bundle must stay a **single file**: the runner image copies exactly one artifact out
-of its builder stage, so code splitting would ship a `cli.js` importing chunks that are
-not there. `tsup.config.ts` disables splitting and bundles the AWS SDK, and the
-Dockerfile asserts the output is one file.
+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.
 
 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": "0.1.0",
+  "version": "0.1.1-dev.b352795",
   "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",