@trawlme/cli 3.12.6 → 3.12.7

package/README.md

@@ -220,7 +220,7 @@ Every command exits with one of these codes — scripts and agents driving the C
 | Code | Meaning                                                                 |
 |------|--------------------------------------------------------------------------|
 | `0`  | Success                                                                 |
-| `1`  | Unknown/generic error (an unmapped failure — API errors other than 401/404, an unhandled bug — or a business-logic refusal like `data`'s `run_failed`/`in_progress` states, or `trawl create`'s honest `success:false` first-run outcome). **Known overload:** `create`'s domain-level failure and an arbitrary unmapped bug both land on `1` — a script needs to read the `--json` payload's own `success` field (for `create`) to tell them apart; this is intentional (the REST contract's outcome states are a separate axis from the CLI's transport-error taxonomy) and documented here rather than "resolved" by inventing a new code that would only apply to one command. |
+| `1`  | Unknown/generic error (an unmapped failure — API errors other than 401/404, an unhandled bug — or a business-logic refusal like `data`'s `run_failed`/`in_progress` states, or `trawl create`'s honest `success:false` first-run outcome). **Known overload:** `create`'s domain-level failure and an arbitrary unmapped bug both land on `1` — a script needs to read the `--json` payload's own `success` field (for `create`) to tell them apart (and its `verified` field: `success: true` with `verified: false` exits `0` but the wizard never confirmed the script, so check the rows); this is intentional (the REST contract's outcome states are a separate axis from the CLI's transport-error taxonomy) and documented here rather than "resolved" by inventing a new code that would only apply to one command. |
 | `2`  | Usage error (bad flag/value, invalid ID, missing required argument, unknown option/command — including the [non-interactive rule](#non-interactive-rule) refusing to prompt) |
 | `3`  | Auth error (not logged in, the session token is expired/invalid, or a JWT-only command was run under an API key — see [Authentication](#authentication)) — run `trawl login` |
 | `4`  | Not found (no such resource, or — for `data` — no persisted payload to read) |

package/dist/commands/create.d.ts

@@ -1,6 +1,7 @@
 import { Command } from 'commander';
 export interface WizardResponse {
     success: boolean;
+    verified?: boolean;
     scrap?: {
         _id: string;
         title: string;

package/dist/commands/create.js

@@ -8,7 +8,12 @@ import { requireUrl, requireString } from '../lib/validate.js';
 import { UsageError, RefusalError, HUMAN_ERROR_MAX } from '../lib/errors.js';
 import { renderPinch, pinchEnabled } from '../lib/pinch.js';
 import { startPinchAnimation } from '../lib/pinchAnimation.js';
+function unverifiedSuccess(data) {
+    return data.success && data.verified === false;
+}
 function firstRunLabel(data, autoFixEnabled) {
+    if (unverifiedSuccess(data))
+        return 'succeeded — script not verified by the wizard, check the rows';
     if (data.success)
         return 'succeeded';
     if (!data.scrap)
@@ -169,7 +174,8 @@ export const create = new Command('create')
                 `Auto-fix is retrying in the background — do NOT re-run create; poll ${pollTarget}.`);
         }
         if (!opts.json && pinchEnabled()) {
-            console.log(data.success ? renderPinch('celebrating') : renderPinch('confused'));
+            const mood = !data.success ? 'confused' : unverifiedSuccess(data) ? 'idle' : 'celebrating';
+            console.log(renderPinch(mood));
         }
     }
     if (!data.success)

package/docs/agent-quickstart.md

@@ -101,7 +101,11 @@ first run, and auto-fix on failure (default on; `--no-autofix` disables it).
 `success` is an honest outcome of that first run, not "did the HTTP call
 succeed" — a failed first run is still a 200 response (the scrap was still
 created), and the CLI exits `1` in that case even though `--json` always
-prints the raw payload verbatim. The call legitimately runs many minutes
+prints the raw payload verbatim. A `success: true` with `verified: false` means
+the first run returned rows but the wizard never confirmed that exact script
+(it stopped before `finish`): check the rows before trusting it — human mode
+says "succeeded — script not verified by the wizard, check the rows", `--json`
+callers read `verified`. The call legitimately runs many minutes
 server-side (AI generation + a proxy-tier probe ladder + an iteration loop +
 a real run), so the CLI reads the wizard's NDJSON progress stream: human mode
 prints one short line per stage on stderr, `--json` prints only the final

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trawlme/cli",
-  "version": "3.12.6",
+  "version": "3.12.7",
   "description": "Trawl CLI — manage scraps from the terminal",
   "type": "module",
   "bin": {