@oneharness/sdk 0.14.0 → 0.15.0

package/README.md

@@ -29,6 +29,8 @@ for await (const envelope of oneharness.historyWatch({
 }
 ```
 
+Every JSON-returning method passes `--format json --compact` itself, so the CLI's own default (a human-readable text view) never reaches the SDK. A `run` over several harnesses is a **fallback chain** by default — the first candidate that can run does, and the report's `fallback` block says which; pass `runMode: "parallel"` to run them all at once.
+
 Breaking or returning from either iterator terminates its oneharness subprocess. Every line is validated before it is yielded; malformed or unknown envelope variants fail the iterator. Additive fields within known output envelopes are accepted and preserved.
 
 `null` usage fields mean the harness did not report the value; zero remains a real measured zero. String-valued harness/model/event identifiers should be treated as open sets for forward compatibility. `history` and `historyWatch` raise the exported `HistoryNotFoundError` when a session, record, or watch cursor cannot be resolved.

package/dist/generated/config-report.d.ts

@@ -244,8 +244,9 @@ export interface Field31 {
     [k: string]: unknown;
 }
 /**
- * The configured run mode, if any. Unset falls back to `parallel` (the
- * built-in default) at run time.
+ * The effective run mode: a configured value, else `fallback` (the
+ * built-in default, attributed to [`DEFAULT_SOURCE`]) — the report says what
+ * a run would do, so an unset mode is never shown as `null`.
  */
 export interface Field9 {
     source: string | null;

package/dist/generated/schemas.json

@@ -4016,12 +4016,12 @@
                 "description": "How the selected harnesses are run. Accepted as a CLI value (`--run-mode`,\nparsed in the `oneharness` binary) and a config-file value (`run_mode`, via\n`Deserialize`); the CLI parsing lives in the binary so this core crate stays\nfree of `clap`.",
                 "oneOf": [
                     {
-                        "description": "Run every selected harness at once, each an independent subprocess, and\nreport them all. The default — the historical behavior.",
+                        "description": "Run every selected harness at once, each an independent subprocess, and\nreport them all. The opt-in (`--run-mode parallel`, `run_mode =\n\"parallel\"`, `ONEHARNESS_RUN_MODE=parallel`); it was the default before\nthe fallback chain became one.",
                         "type": "string",
                         "const": "parallel"
                     },
                     {
-                        "description": "Run the selected harnesses in priority order (the `--harness` / config\norder, else registry order under `--all`), stopping at the first that\nactually runs the task; fall through only the candidates that cannot run\nat all (see [`startup_failure_reason`]).",
+                        "description": "Run the selected harnesses in priority order (the `--harness` / config\norder, else registry order under `--all`), stopping at the first that\nactually runs the task; fall through only the candidates that cannot run\nat all (see [`startup_failure_reason`]). The default wherever a run mode\nis left unset — in the request, every config layer and the environment.",
                         "type": "string",
                         "const": "fallback"
                     }
@@ -15986,7 +15986,7 @@
                 "$ref": "#/$defs/Field"
             },
             "run_mode": {
-                "description": "The configured run mode, if any. Unset falls back to `parallel` (the\nbuilt-in default) at run time.",
+                "description": "The effective run mode: a configured value, else `fallback` (the\nbuilt-in default, attributed to [`DEFAULT_SOURCE`]) — the report says what\na run would do, so an unset mode is never shown as `null`.",
                 "$ref": "#/$defs/Field9"
             },
             "schema_file": {
@@ -16453,12 +16453,12 @@
                 "description": "How the selected harnesses are run. Accepted as a CLI value (`--run-mode`,\nparsed in the `oneharness` binary) and a config-file value (`run_mode`, via\n`Deserialize`); the CLI parsing lives in the binary so this core crate stays\nfree of `clap`.",
                 "oneOf": [
                     {
-                        "description": "Run every selected harness at once, each an independent subprocess, and\nreport them all. The default — the historical behavior.",
+                        "description": "Run every selected harness at once, each an independent subprocess, and\nreport them all. The opt-in (`--run-mode parallel`, `run_mode =\n\"parallel\"`, `ONEHARNESS_RUN_MODE=parallel`); it was the default before\nthe fallback chain became one.",
                         "type": "string",
                         "const": "parallel"
                     },
                     {
-                        "description": "Run the selected harnesses in priority order (the `--harness` / config\norder, else registry order under `--all`), stopping at the first that\nactually runs the task; fall through only the candidates that cannot run\nat all (see [`startup_failure_reason`]).",
+                        "description": "Run the selected harnesses in priority order (the `--harness` / config\norder, else registry order under `--all`), stopping at the first that\nactually runs the task; fall through only the candidates that cannot run\nat all (see [`startup_failure_reason`]). The default wherever a run mode\nis left unset — in the request, every config layer and the environment.",
                         "type": "string",
                         "const": "fallback"
                     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oneharness/sdk",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "description": "Typed Node.js SDK for oneharness",
   "type": "module",
   "main": "dist/index.js",
@@ -19,7 +19,7 @@
     "node": ">=20"
   },
   "dependencies": {
-    "oneharness-cli": "0.14.0",
+    "oneharness-cli": "0.15.0",
     "zod": "^4.4.3"
   }
 }