@amaster.ai/employee-runtime-connector 0.1.0-beta.0 → 0.1.0-beta.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -21,6 +21,8 @@ Do not use `latest`, `^`, or `~` in a runtime image. The image tag and connector
21
21
 
22
22
  Immutable images should pin an exact package version as their baseline. The current connector does not download or replace runtime code while running; package upgrades and rollbacks belong to the image build and rollout.
23
23
 
24
+ The publish workflow verifies that npm records the publishing commit as the package `gitHead`, then updates the repository deployment pin. Remote deployment accepts that package only when its `gitHead` is an ancestor of the target source commit and the connector package path is unchanged between them. This path-only comparison is valid because the published connector is self-contained; if runtime code starts importing workspace source outside this package, expand the provenance scope and tests before release. After restart, deployment also verifies the package CLI version inside the container. Do not update the deployment pin manually to bypass either provenance check.
25
+
24
26
  ## Package Contents
25
27
 
26
28
  - `dist/amaster-runtime.mjs`: configuration, pairing, workspace, diagnostics, and daemon lifecycle CLI.
@@ -29,3 +31,10 @@ Immutable images should pin an exact package version as their baseline. The curr
29
31
  The source of truth lives under this package's `src/` directory. The package build copies the CLI and bundles the daemon modules into publishable output; do not edit generated files under `dist/`.
30
32
 
31
33
  Runtime code belongs in the container image. Persist only connector state, the result outbox, and workspaces under the configured state directory.
34
+
35
+ The AMaster remote stack derives its runtime image from the Pi base image with
36
+ `docker/Dockerfile.amaster-employee-pi-cli-runtime`. The build installs one exact
37
+ connector package version under `/opt/pi-cli-runtime` and sets
38
+ `AMASTER_RUNTIME_CLI_TARGET` to that package binary. Do not mount repository
39
+ scripts or previously installed runtime code from `/data` over this path;
40
+ `/data` is a state volume and must survive package upgrades and rollbacks.