@qawolf/cli 1.19.1 → 1.19.2

package/dist/cli.js

@@ -326146,7 +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}, or export QAWOLF_RUNNER_ID=${launchedId}.`,
+  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}.`,
@@ -346136,7 +346136,7 @@ function startUpdateCheck(deps) {
 // package.json
 var package_default = {
   name: "@qawolf/cli",
-  version: "1.19.1",
+  version: "1.19.2",
   description: "Run and manage QA Wolf flows from the terminal, CI, or an AI agent",
   keywords: [
     "automation",
@@ -359030,4 +359030,4 @@ createProgram({ signals }).parseAsync().catch(() => {
     process.exitCode = 1;
 }).finally(() => flushAndExit(typeof process.exitCode === "number" ? process.exitCode : 0));
 
-//# debugId=F98A1DC596D4CF4664756E2164756E21
+//# debugId=3E751EC68D3A12B564756E2164756E21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@qawolf/cli",
-  "version": "1.19.1",
+  "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,