@colony2/c2j 0.0.71 → 0.0.73

package/README.md

@@ -57,8 +57,6 @@ c2j submit
 c2j run
 c2j run one
 c2j run with-lease
-c2j run any
-c2j run loop
 c2j ready
 c2j list
 c2j test
@@ -83,6 +81,31 @@ modified at build time.
 See [Execution tools](EXECUTION_TOOLS.md) for lazy pnpm, Nix, and uv tool dependencies and provider-owned cache storage.
 See [Extension ops](EXTENSION_OPS.md) for authoring, publishing, and invoking prebuilt Nix ops.
 
+## Nix package
+
+The Nix package contains only the `c2j` executable, with no Node/npm wrapper or
+bundled tool runtimes. Linux and macOS builds are published for x86-64 and ARM64
+to the `colony2` Cachix cache after the main-branch tests pass.
+
+```bash
+cachix use colony2
+nix run github:colony-2/c2j/main#c2j -- version
+# Install into your profile:
+nix profile add github:colony-2/c2j/main#c2j
+```
+
+For reproducible, download-only deployments, replace `main` with a commit whose
+Release workflow's Nix jobs have succeeded and use `--max-jobs 0`. A newly pushed
+commit may not be cached yet. `main` builds report `unstable-<commit>` as their
+version. Runtime tools such as Git, Nix, pnpm, and uv are supplied separately by
+the execution environment when needed.
+
+Maintainers: `nix build .#c2j` builds the executable; `nix flake check` also runs
+its installation checks. After changing Go dependencies, update `vendorHash` in
+`nix/package.nix` to the hash reported by a build with `lib.fakeHash`. CI checks
+all four platforms, pushes with `CACHIX_COLONY2_AUTHKEY`, verifies downloads into
+an empty store with builds disabled, and pins each commit's package in Cachix.
+
 ## Quick Start
 
 ### 1. Check current-cell resolution
@@ -551,56 +574,19 @@ the job becomes runnable or the wait timeout is reached.
 - `4`: job not runnable under the selected policy
 - `5`: invalid job identity or invalid run arguments
 
-## Worker Modes
-
-`c2j run loop` runs a long-lived worker for one tenant. It leases available jobs
-from a remote JobDB runtime and executes up to the configured local concurrency.
-
-Basic usage:
-
-```bash
-c2j run loop --jobdb http://localhost:9047/<tenant-id> --concurrency 4
-```
-
-Important behavior:
-
-- `--concurrency <n>` controls how many jobs this process can run at once
-- `--jobdb` must be a remote `http://host/tenant` or `https://host/tenant` URI
-- `--embed` is not available for `run loop`
-- `--jobdb embed:///` is rejected for `run loop`
-- `run loop` is non-interactive; use `run` or an ops surface for jobs that need input
+## Dispatching work
 
-### Loose scheduling with `ready` and `run any`
+Run a known job with `c2j run --job-id <id>`, or let a dispatcher such as Pulse
+claim a lease and launch [`c2j run with-lease`](GUIDE-Run-With-Lease.md).
+`run any` and `run loop` are no longer supported.
 
-`c2j ready` prints the number of currently ready recipe jobs for one tenant:
+`c2j ready` prints a read-only snapshot of the number of ready recipe jobs:
 
 ```bash
 c2j ready --jobdb http://localhost:9047/<tenant-id>
 ```
 
-`c2j run any` atomically polls for one available item of recipe work, leases it,
-runs it, and exits. If no lease is available, it exits successfully after
-printing `no jobs found`.
-
-```bash
-c2j run any --jobdb http://localhost:9047/<tenant-id>
-```
-
-These can be composed by an external scheduler:
-
-```bash
-count=$(c2j ready --jobdb http://localhost:9047/<tenant-id>)
-if [ "$count" -gt 0 ]; then
-  for _ in $(seq 1 "$count"); do
-    c2j run any --jobdb http://localhost:9047/<tenant-id> &
-  done
-  wait
-fi
-```
-
-`ready` is only a non-mutating snapshot and can become stale under competing
-workers. `run any` uses JobDB polling so finding available work and acquiring the
-lease happen in one runtime operation.
+The count is not a reservation and may change before a dispatcher claims work.
 
 ## Listing Jobs
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@colony2/c2j",
-  "version": "0.0.71",
+  "version": "0.0.73",
   "description": "c2j job system",
   "license": "Apache-2.0",
   "homepage": "https://github.com/colony-2/c2j",