@zenrows/cli 1.4.1 → 1.4.2

package/dist/src/cli/commands/fetch.js

@@ -26,8 +26,8 @@ export const fetch_ = {
         "  --js-render            render JavaScript (manual mode only)",
         "  --premium-proxy        use residential IPs (manual mode only)",
         "  --proxy-country <cc>   geo-target (auto mode; in manual mode needs --premium-proxy)",
-        "  --wait <ms>            fixed wait after load",
-        "  --wait-for <selector>  wait for a CSS selector",
+        "  --wait <ms>            fixed wait after load (needs --manual --js-render; auto mode may ignore it)",
+        "  --wait-for <selector>  wait for a CSS selector (needs --manual --js-render; auto mode may ignore it)",
         "  --js-instructions <j>  JSON instructions to run on the page",
         "  --session-id <n>       keep the same IP across requests",
         "  --original-status      return the target's original HTTP status",

package/dist/src/core/config.js

@@ -14,7 +14,7 @@ export const CONFIG_VERSION = "0.1.0";
  * entrypoint) so core modules — telemetry, signup provenance — can read it
  * without an import cycle. `VERSION` in `cli/index.ts` re-exports this.
  */
-export const CLI_VERSION = "1.4.1";
+export const CLI_VERSION = "1.4.2";
 /** The User-Agent on every request to a Zenrows API. The gateway reads the version from it. */
 export const CLI_USER_AGENT = `zenrows-cli/${CLI_VERSION}`;
 /** Env var to override the Fetch and Extract API base (local/staging testing). */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zenrows/cli",
-  "version": "1.4.1",
+  "version": "1.4.2",
   "description": "Open-source CLI, MCP, skills, templates, workflows, recipes, and evals layer for giving AI agents reliable access to protected web data through Zenrows cloud infrastructure.",
   "type": "module",
   "license": "MIT",

package/skills/trace-debug/SKILL.md

@@ -20,9 +20,10 @@ zenrows trace export <run-id>     # JSON for sharing
 
 ## Failure → action map
 - `FETCH_FAILED` / empty content → first retry in auto mode (`mode=auto`), which
-  escalates for you and bills only for what succeeds. For slow pages add
-  `--wait-for <selector>`. Only when auto mode has failed on its own, take
-  manual control with `--manual --js-render`, then `--premium-proxy`. Each step
+  escalates for you and bills only for what succeeds. Only when auto mode has
+  failed on its own, take manual control with `--manual --js-render`, then
+  `--premium-proxy`. For slow pages, add `--wait-for <selector>` to a
+  `--manual --js-render` run; auto mode may ignore it. Each step
   multiplies the cost of the request, and both together are the most expensive
   configuration available ([[cost-control]]).
 - `REQUEST_TIMEOUT` → the CLI stopped waiting; the API was reached. Raise