@skrr-ai/cli 0.1.122 → 0.1.124

package/oclif.manifest.json

@@ -7207,8 +7207,17 @@
           "allowNo": false,
           "type": "boolean"
         },
+        "incremental": {
+          "dependsOn": [
+            "jsonl"
+          ],
+          "description": "With --jsonl, make `text.delta` a real delta: it carries only `delta`, the characters it adds, instead of the whole answer so far, and leaves out the envelopes that `session.output` already carries. A rewrite that is not an append arrives as `replace`, the new full text. `run.result` still holds the whole answer. Without it a long answer written as JSON lines grows with the square of its length.",
+          "name": "incremental",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "jsonl": {
-          "description": "Emit one JSON event per line while streaming. Every line is a complete JSON value. Assistant text arrives as `text.delta` whose `text` is the CUMULATIVE answer so far, not a delta — take the last one, or `run.result` at the end. The same text is mirrored inside `session.output` envelopes for consumers that want the raw stream, so folding both doubles the answer: pick ONE lane. A widget the agent wrote (a block of CSS, HTML and JavaScript the apps draw) is its text description in `text.delta` and `run.result`; the `session.output` lane carries the block itself. Inside a `session.output`, `envelopes[].__seq` is the dedupe key and the ordering key — the same envelope is delivered by more than one room, and a re-delivery repeats its `__seq`. A `stream.gap` event means envelopes in that seq range never arrived and replay from the server could not recover them; a hole replay fills, or one that held only invisible envelopes (`service`, `status`), emits nothing. When the persisted message could be checked, `verified` is true and `missing` names what the stream is short of (`text`, `tool`), and the event arrives just before the terminal event; `verified: false` means it could not be checked and the text MAY be short. `run.result` and the persisted message remain authoritative. Tool calls arrive as `tool.started` / `tool.completed`, once per `toolUseId`, on cloud and local-harness runs alike. A `session.notice` with `notice: \"harness-session-reset\"` means the local harness could not resume its previous session and started a new one, which does not see earlier turns of the conversation; `message` says why. A `permission.resolved` says how a local harness permission request was decided: `decidedBy` in words, and `basis` — `person` (with `surface`), `mode` (with `mode`), `policy` or `session-grant` — beside the wire `by`. When a platform update restarts the server relaying a turn your machine is still running, the run does not end at that failure: `run.handed_over` (`code: \"AGENT_WORKER_REPLACED\"`, `reason: \"worker_replaced_daemon_running\"`, `waitMs`, `deadlineAt`) says the CLI is waiting, then exactly one terminal event follows — `run.completed` with `repaired: true` and `result` (then `run.result` with `status: \"completed\"`, `repaired: true`, exit 0) when the machine finished; `run.failed` with `handover.outcome: \"machine_failed\"` and the machine's reason when it did not; or `run.failed` with `handover.outcome: \"expired\"` and the original failure when --repair-wait ran out (exit 1 for both). Ctrl-C during the wait emits `run.detached` with `handedOver: true` and exits 130.",
+          "description": "Emit one JSON event per line while streaming. Every line is a complete JSON value. Assistant text arrives as `text.delta` whose `text` is the CUMULATIVE answer so far, not a delta — take the last one, or `run.result` at the end. Each `text.delta` also carries `delta`, the characters it adds, when it only appends to the one before; with --incremental it carries nothing else of the text (see that flag). The same text is mirrored inside `session.output` envelopes for consumers that want the raw stream, so folding both doubles the answer: pick ONE lane. A widget the agent wrote (a block of CSS, HTML and JavaScript the apps draw) is its text description in `text.delta` and `run.result`; the `session.output` lane carries the block itself. Inside a `session.output`, `envelopes[].__seq` is the dedupe key and the ordering key — the same envelope is delivered by more than one room, and a re-delivery repeats its `__seq`. A `stream.gap` event means envelopes in that seq range never arrived and replay from the server could not recover them; a hole replay fills, or one that held only invisible envelopes (`service`, `status`), emits nothing. When the persisted message could be checked, `verified` is true and `missing` names what the stream is short of (`text`, `tool`), and the event arrives just before the terminal event; `verified: false` means it could not be checked and the text MAY be short. `run.result` and the persisted message remain authoritative. Tool calls arrive as `tool.started` / `tool.completed`, once per `toolUseId`, on cloud and local-harness runs alike. A `session.notice` with `notice: \"harness-session-reset\"` means the local harness could not resume its previous session and started a new one, which does not see earlier turns of the conversation; `message` says why. `notice: \"model-request-retrying\"` means the model rejected or could not answer a request and the harness is retrying it: `message` names the cause (for example the model rejecting the credentials on this machine, HTTP 403) and the attempt, a few times per retry episode, so a run that looks quiet is not. A `permission.resolved` says how a local harness permission request was decided: `decidedBy` in words, and `basis` — `person` (with `surface`), `mode` (with `mode`), `policy` or `session-grant` — beside the wire `by`. When a platform update restarts the server relaying a turn your machine is still running, the run does not end at that failure: `run.handed_over` (`code: \"AGENT_WORKER_REPLACED\"`, `reason: \"worker_replaced_daemon_running\"`, `waitMs`, `deadlineAt`) says the CLI is waiting, then exactly one terminal event follows — `run.completed` with `repaired: true` and `result` (then `run.result` with `status: \"completed\"`, `repaired: true`, exit 0) when the machine finished; `run.failed` with `handover.outcome: \"machine_failed\"` and the machine's reason when it did not; or `run.failed` with `handover.outcome: \"expired\"` and the original failure when --repair-wait ran out (exit 1 for both). Ctrl-C during the wait emits `run.detached` with `handedOver: true` and exits 130. Whenever a run fails, `run.failed` carries `message`, the reason in words as the platform gave it (the same sentence a terminal prints after `Error:`), beside the short `reason`.",
           "name": "jsonl",
           "allowNo": false,
           "type": "boolean"
@@ -142575,5 +142584,5 @@
       ]
     }
   },
-  "version": "0.1.122"
+  "version": "0.1.124"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skrr-ai/cli",
-  "version": "0.1.122",
+  "version": "0.1.124",
   "description": "Command-line interface for skrr",
   "license": "ISC",
   "author": "skrr",
@@ -636,6 +636,9 @@
       "store:admissions": {
         "description": "Review releases and listings awaiting capability-tiered admission (curators)"
       },
+      "store:gallery-admissions": {
+        "description": "Review frozen Store gallery revisions (curators): inspect the images, then approve or refuse the exact revision"
+      },
       "store:artifacts": {
         "description": "Publish and inspect dependency releases of your own skills and actions"
       },