@qawolf/cli 1.19.0 → 1.19.2

package/dist/cli.js

@@ -325822,6 +325822,7 @@ var authMessages = {
     },
     request: {
       rejected401: (noun) => `QA Wolf API rejected the${noun ? ` ${noun}` : ""} request (HTTP 401). Check your API key.`,
+      rejected402: (noun) => `QA Wolf API refused the${noun ? ` ${noun}` : ""} request (HTTP 402): billing prevented it.`,
       rejected403: (noun) => `QA Wolf API rejected the${noun ? ` ${noun}` : ""} request (HTTP 403). Check that your API key has access to this environment.`,
       notFound404: (noun) => `QA Wolf API could not find ${noun ? `${noun} for that environment` : "that environment"} (HTTP 404). Check the --env value.`,
       failedWithStatus: (status, noun) => `QA Wolf API${noun ? ` ${noun}` : ""} request failed (HTTP ${status}).`,
@@ -326145,6 +326146,7 @@ var lifecycleMessages = {
   alreadyRunning: (id) => `Runner ${id} was already running.`,
   defaultNotRemembered: (id) => `Runner ${id} could not be written to .qawolf as this directory's default, so later commands will not find it on their own. Pass --runner ${id}, or set QAWOLF_RUNNER_ID=${id}.`,
   defaultNotForgotten: (id) => `Runner ${id} was terminated, but it could not be removed from .qawolf as this directory's default, so later commands will still be sent to it. Pass --runner, or launch a new runner.`,
+  envRunnerIdShadowsLaunch: (launchedId, envId) => `QAWOLF_RUNNER_ID=${envId} is still set, so commands that omit --runner will keep targeting it instead of the runner just launched. Pass --runner ${launchedId} to address this one.`,
   keptAlive: (id) => `Runner ${id} is alive, and its inactivity clock has been reset.`,
   launchFailed: (id, error) => `Launching runner ${id} failed. ${error}`,
   launchLost: (id, error) => `Launching runner ${id} failed. ${error}. The request may still have reached QA Wolf and started a runner, so relaunch the same id with qawolf runner launch --id ${id} to attach to it rather than start a second one, or terminate it with qawolf runner terminate --runner ${id}.`,
@@ -326381,7 +326383,8 @@ var exitCodes = {
   auth: 3,
   network: 4,
   config: 5,
-  timeout: 6
+  timeout: 6,
+  payment: 7
 };
 function exit(code, message, proc = process) {
   if (message !== undefined && message.length > 0) {
@@ -341065,6 +341068,12 @@ function describeRequestError(err, baseUrl, noun) {
         exitCode: exitCodes.auth,
         ...body
       };
+    if (err.status === 402)
+      return {
+        error: m.request.rejected402(noun),
+        exitCode: exitCodes.payment,
+        ...body
+      };
     if (err.status === 403)
       return { error: m.request.rejected403(noun), ...body };
     if (err.status === 404)
@@ -346127,7 +346136,7 @@ function startUpdateCheck(deps) {
 // package.json
 var package_default = {
   name: "@qawolf/cli",
-  version: "1.19.0",
+  version: "1.19.2",
   description: "Run and manage QA Wolf flows from the terminal, CI, or an AI agent",
   keywords: [
     "automation",
@@ -356707,7 +356716,7 @@ async function launchRunner(ctx, options) {
   if (!result.ok) {
     return {
       ...failureFields(result),
-      exitCode: exitCodes.network,
+      exitCode: result.exitCode ?? exitCodes.network,
       mayHaveArrived: result.mayHaveArrived ?? false,
       ok: false
     };
@@ -357347,7 +357356,10 @@ async function handleRunnerImportPackage(ctx, options, deps) {
     packageVersion
   }, runnerCallOptions);
   if (!result.ok) {
-    return { ...failureFields(result), exitCode: exitCodes.network };
+    return {
+      ...failureFields(result),
+      exitCode: result.exitCode ?? exitCodes.network
+    };
   }
   if (result.value.outcome === "failure") {
     const failure = result.value;
@@ -357758,7 +357770,10 @@ async function handleRunnerExec(ctx, options, deps) {
     ...scope.files === undefined ? {} : { files: scope.files }
   }, runnerCallOptions);
   if (!result.ok) {
-    return { ...failureFields(result), exitCode: exitCodes.network };
+    return {
+      ...failureFields(result),
+      exitCode: result.exitCode ?? exitCodes.network
+    };
   }
   if (result.value.outcome === "failure") {
     result.value.failureReason;
@@ -358082,6 +358097,10 @@ async function handleRunnerLaunch(ctx, options, deps) {
   if (!launched.ok) {
     return { ...failureFields(launched), exitCode: launched.exitCode };
   }
+  const envRunnerId = deps.env[runnerIdEnvironmentVariable]?.trim();
+  if (envRunnerId && envRunnerId !== launched.value.id) {
+    ctx.ui.warn(interactiveRunnerMessages.envRunnerIdShadowsLaunch(launched.value.id, envRunnerId));
+  }
   ctx.ui.output(launched.value, launched.value.alreadyRunning ? interactiveRunnerMessages.alreadyRunning(launched.value.id) : interactiveRunnerMessages.launched(launched.value.id));
   return;
 }
@@ -358796,7 +358815,10 @@ async function sendRunFlowRequest(ctx, options, delta) {
   }, runnerCallOptions);
   if (!result.ok) {
     return {
-      failure: { ...failureFields(result), exitCode: exitCodes.network },
+      failure: {
+        ...failureFields(result),
+        exitCode: result.exitCode ?? exitCodes.network
+      },
       type: "failed"
     };
   }
@@ -359008,4 +359030,4 @@ createProgram({ signals }).parseAsync().catch(() => {
     process.exitCode = 1;
 }).finally(() => flushAndExit(typeof process.exitCode === "number" ? process.exitCode : 0));
 
-//# debugId=C46D821567854FC564756E2164756E21
+//# debugId=3E751EC68D3A12B564756E2164756E21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@qawolf/cli",
-  "version": "1.19.0",
+  "version": "1.19.2",
   "description": "Run and manage QA Wolf flows from the terminal, CI, or an AI agent",
   "keywords": [
     "automation",

package/skills/qawolf-cli/references/runner.md

@@ -17,7 +17,7 @@ Commands that target a runner find one in this order: `--runner`, then
 `QAWOLF_RUNNER_ID`, then the runner stored for the current directory (which
 `qawolf runner launch` sets). Setting the environment variable once is the most
 robust for a harness whose working directory may not be stable, but it comes
-with two catches worth knowing before you rely on it.
+with three catches worth knowing before you rely on it.
 
 `qawolf runner launch` is not in that order: it takes its id from `--id` and
 never reads `QAWOLF_RUNNER_ID`. Bare `qawolf runner launch` invents a random id,
@@ -31,6 +31,13 @@ auto-launch described next: instead of starting `agent-1`, commands try to reach
 it and fail with exit code `4`, which reads as "retry" and never succeeds.
 Launch that id once yourself and the rest follows.
 
+And launching an id that differs from `QAWOLF_RUNNER_ID` prints a warning on
+stderr naming both ids: the variable still outranks the directory default, so
+commands that omit `--runner` keep going to whatever it names, not the runner
+you just launched. Expected when you are launching an additional runner on
+purpose — address that one with `--runner` rather than re-exporting the
+variable, which would repoint every other runner-less command too.
+
 If nothing names a runner, the commands that change something will launch one
 and say so on stderr, naming it: `run`, `act` and `exec`. **Read that
 announcement.** The browser it just started is fresh: nothing has been run on it,