@elaraai/east-c-cli 1.0.79 → 1.0.81

package/README.md

@@ -33,78 +33,33 @@ See [`docs/conventions/MAKEFILE_TARGETS.md`](../../../../docs/conventions/MAKEFI
 
 The CLI loads the standard platform from `east-c-std` by default. Custom platform functions can be linked at build time.
 
-### Streaming outputs and inputs
-
-A function whose trailing parameter is an emit capability writes its output
-incrementally instead of returning it; a large collection input can be fed
-lazily, one decoded segment at a time (`--stream` is repeatable):
-
-```bash
-# Emit a Dict (or array / set) through the trailing parameter, feeding
-# inputs 0 and 1 lazily from indexed beast2 blobs
-east-c run task.beast2 -i rows.beast2 -i more.beast2 --stream 0 --stream 1 \
-    --emit dict -o out.beast2 -v
-```
-
-Dict and Set emissions must ascend in East order. The sink writes one pass,
-segment by segment, with one open batch in memory whatever the size of the
-output, and a key below the previous one is an error naming both:
-
-```text
-beast2 v5: Dict key emitted out of order: 1 after 2 — Set/Dict emissions must ascend in East order
-```
-
-Equal keys are an error too unless the sink folds them:
-
-```bash
-# Dict: fold the values of adjacent equal keys with an East function (K, V, V) -> V
-east-c run task.beast2 --emit dict --merge merge.beast2 -o out.beast2
-
-# Set: keep the first of adjacent equal elements
-east-c run task.beast2 --emit set --union -o out.beast2
-```
-
-`--merge` takes an IR file in any format the program itself may use, compiled
-with the run's `-p` platforms; its signature must match the emit parameter's
-key and value types. Adjacent equal keys fold left in emission order,
-`acc = merge(key, acc, value)`, and the output is byte-identical to what the
-sink writes without the flag for the already-folded sequence.
-
-### Merging blobs
-
-`merge` combines sorted Set or Dict blobs of one type — the files `run --emit`
-writes — into one, in a single pass over the inputs: every input is read
-segment by segment, equal keys across inputs fold in input order (`--merge`
-on Dict inputs, `--union` on Set inputs; without a fold an equal key is an
-error), and the output is byte-identical to what `run --emit` writes for the
-same entries emitted ascending. This is how e3 assembles a partitioned task's
-keyed partials; all three runners write the same bytes.
-
-```bash
-# Dict partials: fold the values of equal keys, in input order
-east-c merge --merge merge.beast2 -i part-0.beast2 -i part-1.beast2 -i part-2.beast2 -o out.beast2 -v
-
-# Set partials: the first of equal elements stands
-east-c merge --union -i part-0.beast2 -i part-1.beast2 -o out.beast2
-
-# Only the keys in [from, to): range.beast2 holds a Struct{from: Option<K>,
-# to: Option<K>} over the inputs' key type, an absent bound open
-east-c merge --merge merge.beast2 --range range.beast2 -i part-0.beast2 -i part-1.beast2 -o out.beast2
-```
-
-With `--range` every input is sought to the segment owning `from` through its
-fences and read up to the first key at or past `to`, so a merge over one key
-range of large partials reads that range's share of each, plus at most one
-segment — how e3 merges a large output in parallel, one range per unit.
-
-An input of another type than the first, an Array input, an input whose keys
-do not ascend, a fold whose signature does not match the inputs, and bounds of
-another type than the inputs' key are refused, naming the input. With `-v` the
-merge prints its account:
-
-```text
-merge: 3 input(s), 31 entries, 13 fold(s)
-```
+### Running a unit (`exec`)
+
+`east-c exec <unit.beast2>` is the command e3 runs: the machine-facing twin
+of `run`. The unit file names the work — a program to run over its inputs, or
+the parts of an output to merge — with the platforms, the threads the runner
+may use, the output's kind (a value the program returns, or an array, set,
+dict or fold it emits into), and where to write the output and a typed
+result: the outcome (`ok`, or `failed` with the message and its source
+locations), the peak memory, and the time spent loading, compiling, executing
+and writing. Paths in a unit may be relative to its file, so a unit and the
+files it names replay wherever they are moved together. It exits 0 when the
+outcome is `ok` and 1 when the result records a failure; `-v` prints where the
+time went and the peak memory.
+
+### Large inputs
+
+An indexed beast2 collection input of `EAST_LAZY_INPUT_BYTES` bytes or more
+(64 MiB unless set; `0` turns it off) opens lazily: the file is mapped, and a
+read decodes only the segments it reaches. With `-v` the runner says which
+inputs opened lazily and how many of their segments it decoded.
+
+A collection input may also be a manifest directory, the form e3 stages a
+stored collection in: the input file holds a manifest, and each segment it
+names is a standalone blob in `<file>.segments/<sha256>.beast2`. It opens
+over those files — lazily, a read opening only the segments it reaches, or
+whole — and counts as the size of its segments when the runner decides
+whether to open it lazily.
 
 ### Exiting with the parent
 
@@ -116,7 +71,7 @@ the runner down with it when it dies, even while the body is computing.
 Without the flag, stdin is left alone.
 
 ```bash
-east-c run task.beast2 --exit-with-parent --emit dict -o out.beast2
+east-c run task.beast2 --exit-with-parent -o out.beast2
 ```
 
 On Windows the watcher reads a synchronous pipe or an overlapped one. Hand it
@@ -209,7 +164,7 @@ Business Source License 1.1 — see [LICENSE.md](LICENSE.md). Same terms as `eas
   - [@elaraai/e3](https://www.npmjs.com/package/@elaraai/e3): SDK for authoring e3 packages with typed tasks and pipelines
   - [@elaraai/e3-core](https://www.npmjs.com/package/@elaraai/e3-core): Object store, dataflow orchestrator, execution state
   - [@elaraai/e3-types](https://www.npmjs.com/package/@elaraai/e3-types): Shared type definitions for e3 packages
-  - [@elaraai/e3-cli](https://www.npmjs.com/package/@elaraai/e3-cli): `e3 repo`, `e3 package`, `e3 workspace`, `e3 start`, `e3 watch`, `e3 logs` commands
+  - [@elaraai/e3-cli](https://www.npmjs.com/package/@elaraai/e3-cli): `e3 repo`, `e3 package`, `e3 workspace`, `e3 dataflow run`, `e3 watch`, `e3 task logs` commands
   - [@elaraai/e3-api-client](https://www.npmjs.com/package/@elaraai/e3-api-client): HTTP client for remote e3 repositories
   - [@elaraai/e3-api-server](https://www.npmjs.com/package/@elaraai/e3-api-server): REST API server for e3 repositories
   - [@elaraai/e3-api-tests](https://www.npmjs.com/package/@elaraai/e3-api-tests): Shared API compliance test suites

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elaraai/east-c-cli",
-  "version": "1.0.79",
+  "version": "1.0.81",
   "description": "Provides the `east-c` bin. A tiny launcher resolves the native binary for your platform from the matching per-platform package (@elaraai/east-c-cli-<target>), pulled in via optional dependencies.",
   "bin": {
     "east-c": "bin/east-c.mjs"
@@ -32,14 +32,14 @@
     "node": ">=18.0.0"
   },
   "devDependencies": {
-    "@elaraai/east": "1.0.79"
+    "@elaraai/east": "1.0.81"
   },
   "optionalDependencies": {
-    "@elaraai/east-c-cli-linux-x64": "1.0.79",
-    "@elaraai/east-c-cli-linux-arm64": "1.0.79",
-    "@elaraai/east-c-cli-darwin-arm64": "1.0.79",
-    "@elaraai/east-c-cli-darwin-x64": "1.0.79",
-    "@elaraai/east-c-cli-win32-x64": "1.0.79"
+    "@elaraai/east-c-cli-linux-x64": "1.0.81",
+    "@elaraai/east-c-cli-linux-arm64": "1.0.81",
+    "@elaraai/east-c-cli-darwin-arm64": "1.0.81",
+    "@elaraai/east-c-cli-darwin-x64": "1.0.81",
+    "@elaraai/east-c-cli-win32-x64": "1.0.81"
   },
   "scripts": {}
 }