@bentoai/cli 1.1.9 → 1.1.13

package/README.md

@@ -16,18 +16,17 @@ The CLI embeds that consumer skill so an installed release can install it withou
 repository access. Build steps derive its text-import inventory from the skill
 folder; the tree guard catches missing files and stale bytes. Successful CLI
 upgrades use the newly installed launcher to refresh the skill for saved agents,
-so the instructions match the executable. `bento skills --help` owns the command
-syntax; bare `bento skills` keeps its JSON discovery contract.
+so the instructions match the executable. `bento local skill --help` owns the command
+syntax; `bento local skill list` keeps its JSON discovery contract.
 
 npm installs a Node launcher and the compiled executable for the host; users need
 Node, not Bun. `bento --help` owns the command surface.
 
 Harness runtime and protocol ownership belong to the private
 [agent workspace](../agent/README.md). The CLI consumes that owner directly;
-it owns dispatch and user configuration. Local memory and training remain
-local unless --workspace explicitly selects a remote operation. A saved default
-selects remote operation targets and model billing; it never changes execution
-mode. Explicit file addresses and workspace flags must agree.
+it owns dispatch and user configuration. Operations over this computer’s stores
+live under `local`; workspace operations come from the shared contract. A saved default selects remote operation targets
+and model billing. A workspace flag never redirects a local store operation.
 
 The [HTML tool factory](src/cli/html-render-tools.ts) is a hosted composition
 boundary: it consumes gateway/session context and the contract's shared schema,
@@ -39,7 +38,9 @@ bindings and hand-written commands. Its `@bentoai/cli/command-table` export lets
 consume the same grammar without loading the agent runtime. Examples live with the shared
 customer operation inventory. Complete body input comes from a file or stdin; scalar body
 and query flags override file fields, while declared header inputs stay separate. JSON results retain
-API fields on stdout, while HTTP status and headers are NDJSON metadata on stderr.
+API fields on stdout. File receipts and empty results retain HTTP metadata on stdout;
+successful stderr stays quiet except for actionable recovery information. Failures
+retain their status, headers and diagnostics on stderr.
 Named binary writes stream a local file with `--in`, or stdin with `--in -`.
 CLI JSON body files also accept the shared
 [binary request representations](../contract/README.md#customer-adapter-representations)
@@ -52,7 +53,7 @@ inside `apiError`; a non-scope refusal keeps its own code. Local file handling a
 [Service calls](src/commands/services.ts) use named vendor operations rather than
 an arbitrary Bento REST caller. The API retains route admission, vendor
 credentials, funding and accounting. Calls preserve repeated query/form values,
-complete JSON and raw bytes; HTTP status and all returned headers go to stderr.
+complete JSON and raw bytes, following the same output and failure contract above.
 An output file can contain a vendor refusal, so callers must retain the exit
 status and metadata. Installed help owns the input flags.
 
@@ -71,24 +72,23 @@ The prompt convenience and native commands share SDK media and output owners.
 Remote conversations use durable input outcomes from the shared
 [session contract](../contract/README.md). Submission writes its recovery request
 identity to stderr before HTTP, then returns a terminal result or resumable handle.
-A pending result does not cancel work; result/wait only observe that input.
-`session start` returns on acceptance; use `--wait` or `--wait-ms` to observe its reply.
-For starts without waiting, exit 0 means accepted. For reply-waiting commands,
-exit 0 means successful completion, 1 means failed/cancelled, and 2 requires
-inspecting the body. Re-wait only on `status: "pending"`. A terminal `ask` needs
-an answer with a new input handle; other terminal outcomes, including `sleep`
-and `interrupted`, remain final for their handle. Transport closure cannot
-establish completion.
-
-`bento app credentials` manages external runtime keys for an already registered
+A running result does not cancel work; result/wait only observe that input.
+`session create` returns on acceptance; use `--wait` or `--wait-ms` to observe its reply.
+For creation without waiting, exit 0 means accepted. Reply-waiting commands also
+exit 0 while the turn is still running or asking; failed or cancelled turns exit
+1. Re-wait only on `status: "running"`. A terminal `ask` needs an answer with a
+new input handle; other terminal outcomes, including `sleep` and `interrupted`,
+remain final for their handle. Transport closure cannot establish completion.
+
+`bento app credential` manages external runtime keys for an already registered
 app using the same saved human login or process-provided VM key. Workspace and
-app selections are explicit. Export returns the complete API response on stdout, including the one-time
-plaintext key and deployment URLs; HTTP metadata goes to stderr. Capture the
+app selections are explicit. Creation returns the complete API response on stdout, including the one-time
+plaintext key and deployment URLs. Capture the
 key in memory and pass it through stdin to the host's server-side secret store.
 The command never saves exported keys or retries an ambiguous mint. Inspect the
-live inventory and revoke unwanted entries before explicitly exporting again.
-Rotation uses a second export, host deployment and verification, then revocation
-of the prior credential. `bento app credentials --help` owns the command surface.
+live inventory and revoke unwanted entries before explicitly creating another credential.
+Rotation uses a second creation, host deployment and verification, then revocation
+of the prior credential. `bento app credential --help` owns the command surface.
 
 Laptop-local state has one selected root for login, memory, training, sync
 identity, sessions, caches and logs. A fresh install creates `~/.bento`; an
@@ -126,3 +126,5 @@ Use the package scripts for builds, checks and disposable-container tests.
 
 [Mac sync](src/sync/README.md) keeps one computer identity across separate
 workspace transfer instances, with account removal independent of user login.
+
+Public commands follow the [contract naming rule](../contract/README.md#naming).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bentoai/cli",
-  "version": "1.1.9",
+  "version": "1.1.13",
   "description": "Bento CLI for local agents, workspaces and file sync",
   "type": "module",
   "license": "AGPL-3.0-only",
@@ -24,10 +24,10 @@
     "access": "public"
   },
   "optionalDependencies": {
-    "@bentoai/cli-darwin-arm64": "1.1.9",
-    "@bentoai/cli-darwin-x64": "1.1.9",
-    "@bentoai/cli-linux-x64": "1.1.9",
-    "@bentoai/cli-linux-arm64": "1.1.9",
+    "@bentoai/cli-darwin-arm64": "1.1.13",
+    "@bentoai/cli-darwin-x64": "1.1.13",
+    "@bentoai/cli-linux-x64": "1.1.13",
+    "@bentoai/cli-linux-arm64": "1.1.13",
     "@mariozechner/clipboard": "0.3.9"
   }
 }