@unotest/web 0.54.0 → 0.56.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (48) hide show
  1. package/.claude/skills/write-e2e-test/SKILL.md +30 -7
  2. package/.claude/skills/write-e2e-test-ground/SKILL.md +6 -5
  3. package/CHANGELOG.md +160 -3
  4. package/README.md +24 -6
  5. package/dist/config/schema.d.ts +25 -19
  6. package/dist/config/schema.js +1 -1
  7. package/dist/driver/index.d.ts +8 -2
  8. package/dist/driver/index.js +1 -1
  9. package/dist/dsl/index.d.ts +29 -82
  10. package/dist/dsl/index.js +1 -1
  11. package/dist/dsl/v8/scenario-worker.js +1 -1
  12. package/dist/dsl/web-dsl-language-service.d.ts +30 -3
  13. package/dist/dsl/web-dsl-language-service.js +1 -1
  14. package/dist/inspection/page-inject.d.ts +31 -7
  15. package/dist/inspection/page-inject.js +80 -19
  16. package/dist/{interfaces-BU-PQbt4.d.ts → interfaces-BiGd3BdD.d.ts} +29 -4
  17. package/dist/{linter-BpaIstU3.d.ts → linter-DIAb0JOB.d.ts} +8 -0
  18. package/dist/mcp/server.js +1 -1
  19. package/dist/runner/cli.d.ts +1 -1
  20. package/dist/runner/cli.js +1 -1
  21. package/dist/runner/init/chrome-probe.js +1 -1
  22. package/dist/runner/init.js +1 -1
  23. package/dist/runner/install-chromium.js +1 -1
  24. package/dist/runner/prepare-fix.js +1 -1
  25. package/dist/runner/scaffold-workspace.js +1 -1
  26. package/dist/runner/serve-fixture.js +1 -1
  27. package/dist/runner/web-runner-adapter.js +1 -1
  28. package/dist/scenario-variables-B-ULUTHt.d.ts +88 -0
  29. package/examples/idioms/README.md +16 -0
  30. package/examples/idioms/animations-list.js +24 -0
  31. package/examples/idioms/api-call-timeout.js +14 -0
  32. package/examples/idioms/background-tab.js +24 -0
  33. package/examples/idioms/clipboard-paste.js +25 -0
  34. package/examples/idioms/computed-style.js +21 -0
  35. package/examples/idioms/image-size.js +20 -0
  36. package/examples/idioms/never-appears.js +20 -0
  37. package/examples/idioms/never-condition.js +24 -0
  38. package/examples/idioms/page-code-function.js +18 -0
  39. package/examples/idioms/select-by-label.js +22 -0
  40. package/examples/idioms/wait-enabled.js +21 -0
  41. package/examples/idioms/wait-for-animations.js +16 -0
  42. package/examples/idioms/wait-until-value.js +32 -0
  43. package/guides/agent-integration.md +43 -5
  44. package/guides/dsl-reference.md +589 -34
  45. package/llms.txt +26 -6
  46. package/package.json +9 -8
  47. package/types/unotest-dsl.d.ts +36 -22
  48. package/types/unotest-lib.d.ts +5 -3
@@ -197,6 +197,27 @@ For each page state you traverse:
197
197
  CHANGED the address also carries `url` — that's where you are now,
198
198
  no `get_url` / `get_active_context` round-trip needed.
199
199
 
200
+ **A ref belongs to its snapshot, not to the URL.** A `goto` (or
201
+ `reload`, or a re-render) inside the batch loads a new document, and
202
+ the refs you read before it are stale there. Put a `snapshot` step
203
+ between the navigation and the first step that acts by ref — a login
204
+ is then still one call:
205
+
206
+ ```
207
+ explore_steps { explorationId, steps: [
208
+ {action: "goto", url: "<login URL>", section: "Sign in", description: "Open sign-in"},
209
+ {action: "snapshot", section: "Sign in", description: "Fresh refs"},
210
+ {action: "fill", locator: {kind:"locator", steps:[{kind:"ref", ref:"e4"}]},
211
+ value: "LOGIN", section: "Sign in", description: "Fill the login field"},
212
+ …
213
+ ]}
214
+ ```
215
+
216
+ Its reply carries `outline` — the `get_page_snapshot` text, refs live
217
+ from there on. The same page gives the same element the same ref, so a
218
+ ref read from an earlier snapshot of that page works after the step.
219
+ The snapshot step is never recorded and never in the saved test.
220
+
200
221
  **Record checks as assert steps** — `assert_text {locator, text,
201
222
  options?: {exact}}`, `assert_visible {locator}`, `assert_hidden
202
223
  {locator}`, `assert_value {locator, value}`, `assert_count
@@ -213,7 +234,8 @@ For each page state you traverse:
213
234
  reports `autoRun.status: "skipped"` + reason and the manual Phases
214
235
  4–5 apply.
215
236
 
216
- When recording, `description` and `section` are **required**.
237
+ `section` and `description` are **always required**; in
238
+ ad-hoc mode (no `explorationId`) they only label the debug log.
217
239
  Adjacent same-section entries are wrapped in one `step("...", () => { … })`
218
240
  block in the generated test, so the `section` must read
219
241
  like a line in a human test PLAN — the user-facing GOAL of the block
@@ -240,7 +262,8 @@ For each page state you traverse:
240
262
 
241
263
  **Ad-hoc probes** — to try a click or fill without polluting the
242
264
  recording, **omit `explorationId`**. Refs forwarded as-is to the
243
- driver, no resolve/verify, nothing written.
265
+ driver, no resolve/verify, nothing written. `section` and
266
+ `description` are still required — here they only label the debug log.
244
267
 
245
268
  ### Phase 4 — stop, generate, save
246
269
 
@@ -611,9 +634,8 @@ the old browser context, then `run_test` again.
611
634
  | `exit_frame` | | |
612
635
  | `screenshot` | | `name`, `fullPage`, `locator`, `outline`, `evidenceOnly` |
613
636
 
614
- When recording (`explorationId` present): `description` + `section`
615
- are required. Ad-hoc (no `explorationId`): no description/section,
616
- no recording.
637
+ `description` + `section` are always required. Ad-hoc (no
638
+ `explorationId`): nothing is recorded, and they only label the debug log.
617
639
 
618
640
  `screenshot` is the **evidence** step: it files a PNG under the session
619
641
  (`.unotest/explorations/<explorationId>/screenshots/<NNN>-<name>.png`,
@@ -628,8 +650,9 @@ do not write throwaway scenarios just to get a picture.
628
650
 
629
651
  ## Failure modes you will hit
630
652
 
631
- - **`StaleRefError`** — ref no longer in the DOM. Re-`get_page_snapshot`
632
- and use the new ref.
653
+ - **`StaleRefError`** — ref no longer in the DOM: the page changed since
654
+ the snapshot it came from. Re-`get_page_snapshot` and use the new ref;
655
+ inside a batch, a `snapshot` step after the navigation does the same.
633
656
  - **`RefResolveError`** — element has no stable identifier (testId /
634
657
  role+name / aria-label / placeholder / alt / title / text / href /
635
658
  stable id / name attribute). Best fix: ask the app team to add
@@ -344,7 +344,8 @@ batch):
344
344
  reports `autoRun.status: "skipped"` + reason and the manual Phases
345
345
  4–5 apply.
346
346
 
347
- When recording, `description` and `section` are **required**.
347
+ `section` and `description` are **always required**; in
348
+ ad-hoc mode (no `explorationId`) they only label the debug log.
348
349
  Adjacent same-section entries are wrapped in one `step("...", () => { … })`
349
350
  block in the generated test, so the `section` must read
350
351
  like a line in a human test PLAN — the user-facing GOAL of the block
@@ -371,7 +372,8 @@ batch):
371
372
 
372
373
  **Ad-hoc probes** — to try a click or fill without polluting the
373
374
  recording, **omit `explorationId`**. Refs forwarded as-is to the
374
- driver, no resolve/verify, nothing written.
375
+ driver, no resolve/verify, nothing written. `section` and
376
+ `description` are still required — here they only label the debug log.
375
377
 
376
378
  ### Phase 4 — stop, generate, save
377
379
 
@@ -742,9 +744,8 @@ the old browser context, then `run_test` again.
742
744
  | `exit_frame` | | |
743
745
  | `screenshot` | | `name`, `fullPage`, `locator`, `outline`, `evidenceOnly` |
744
746
 
745
- When recording (`explorationId` present): `description` + `section`
746
- are required. Ad-hoc (no `explorationId`): no description/section,
747
- no recording.
747
+ `description` + `section` are always required. Ad-hoc (no
748
+ `explorationId`): nothing is recorded, and they only label the debug log.
748
749
 
749
750
  `screenshot` is the **evidence** step: it files a PNG under the session
750
751
  (`.unotest/explorations/<explorationId>/screenshots/<NNN>-<name>.png`,
package/CHANGELOG.md CHANGED
@@ -1,5 +1,162 @@
1
1
  # Changelog
2
2
 
3
+ ## [0.56.0] - 2026-10-30
4
+
5
+ ### Minor Changes
6
+
7
+ - 7ec07ca: New: `lint --json` prints one JSON document instead of text, for tools that read lint results: every diagnostic as `{file, line, column, severity, rule, message, source}`, including a scenario or a helper that does not parse, plus `advice`, `skipped`, `missing` and `totals`. The exit code is unchanged. Lines about the setup, such as the editor typings hint, are in `advice` with a `kind`, never among the diagnostics; the text output stays as it was. Example: `npx @unotest/web lint --json`. replaces: parsing the text output of `lint`
8
+
9
+ Fixed: `e2e` given a folder of `unotest/e2e/` no longer says the scenario was not found and suggests `init`. It says the argument is a folder, how many scenarios it holds, how to run one (`e2e <folder>/<name>`) and how to run them all as a collection. `run_test` over MCP answers the same.
10
+
11
+ - 8f0d1bc: New: `// @env local, dev` marks a test that belongs to some environments only. `e2e --env <name>` and a collection on that environment leave a test whose marker does not name it out as skipped, with the reason (`@env local, dev: not run on prod`), without starting a browser for it. `lint --env <name>` leaves out a file whose tests are all outside. The marker sits where `// @expect-fail` does: in the file's leading comments for every test, or directly above one `function` line for that test, which wins over the file's. Without `--env`, or without the marker, every test runs as before. `lint` warns about an `@env` name with no `unotest/.env.<name>` or `.secrets.<name>` file. `@unotest/protocol`: `ScenarioAnnotations` gains `envs`. replaces: `if (env('X') === null) skip('…')` at the top of a test, which `lint` could not see
12
+ - f3f1d03: New: `npx @unotest/web upgrade-check [<from>]` prints every Migration note of `@unotest/web` and `@unotest/dsl` between `<from>` and the version that runs, oldest release first, each under its version and date. Without `<from>` it starts from the version the suite's lockfile holds (`unotest/package-lock.json` or a `pnpm-lock.yaml`); with neither, it says what to write. Run it as `cd unotest && npx @unotest/web@<new> upgrade-check` before you upgrade. `--json` prints the notes as data. replaces: reading the changelog by hand for every release since the one you are on
13
+ - 0c73ccb: BREAKING: `fill(locator, value, {force: true})` on a readonly, disabled or hidden field used to pass and leave the field as it was. The step now fails: `the field is readonly and does not hold the value — force skips the editable check, it does not make the field editable`. The value is not shown. A forced fill of an editable field works as before.
14
+
15
+ Migration: a step that forced a fill into a field the page does not let you edit now fails. Make the field editable first (the click or choice that enables it), fill another field, or drop the step if it never did anything.
16
+
17
+ - b8416ec: New: `pause(ms, reason)` for a wait the test means, such as a task that opens 20 minutes after the start. The reason is printed on the step, and `lint:pause-explicit` no longer reports the call. A bare `pause(ms)` is reported as before, and the warning now names the reason form. The DSL reference has a new section, "Waiting a fixed time", which links to `setTestTimeout` for the test's budget. Example: `pause(1260000, 'the hunt opens 21 minutes after the start')`. replaces: shell('sleep …') and a bare pause with a lint-ok comment
18
+ - f8472eb: New: `waitForRequest(glob, {method})` and `assertNoRequest(glob, {method})`. `waitForRequest` takes only a request of that HTTP method (any case); a request of another method is not taken and stays for the next wait, so a GET and a POST to one path no longer need an order of masks. `assertNoRequest` counts only stopped requests of that method. Without `{method}` both behave as before. Example: `waitForRequest('**/api/item', {method: 'POST'})`. replaces: ordering masks so that a GET and a POST to one path are told apart
19
+
20
+ Changed: `screenshot()` is evidence, not a check. A capture that runs out of time no longer fails the test: the call returns `null`, the step gets a warning line, and the reason is filed next to the pictures as `screenshot/<NNN>-<name>-screenshot-error.txt`. Any other capture failure still fails the step, and `assertScreenshot()` still fails on a timeout. New option `screenshot(name, {timeoutMs})`; the default is the context's `defaultTimeoutMs`.
21
+
22
+ - 20884bc: New: `lint:function-newer-than-suite`, a warning when a scenario calls a DSL function this `@unotest/web` knows but the suite's installed release does not. The message names both versions, for example `setTestTimeout() was added in 0.46.0, the suite runs 0.33.0`. The suite's own lint would report the call as an unknown function, and its run would refuse it. Example: `lint` in a suite that installs 0.33.0. replaces: grepping unpacked packages in the npx cache to learn when a function appeared
23
+
24
+ New: the DSL reference has a "Versions" section that lists the release that added each function, generated from the DSL contracts. A DSL function contract now carries `since`.
25
+
26
+ - 62da1f2: New: `hasCookie(name, options?)` says whether a cookie is there at all — the probe that tells a missing cookie from an empty value, as `hasAttribute` does for `getAttribute`. `getCookie` still reads `''` for both. Example: `assertTrue(!hasCookie('session'))` after a logout. replaces: `getCookie(name) == ''`, which an empty cookie also passes
27
+ - 62da1f2: New: `getCookie(name, {page: true})` and `hasCookie(name, {page: true})` read the cookies the page's script is given — `document.cookie` of the page, or of the frame entered with `enterFrame`. Without the option they read the browser context's jar as before: every domain and path, `httpOnly` too. With it, an `httpOnly` cookie or one for another path or domain reads as missing, as the app sees it. Example: `assertTrue(!hasCookie('session', {page: true}))` for an `httpOnly` session. replaces: `evaluate(() => document.cookie)`
28
+ - 62da1f2: BREAKING: `setCookie` now reads the cookie back after the write, and a cookie the browser does not keep fails the step instead of passing. The most common case is `sameSite: 'None'` without `secure: true`: `setCookie('cross'): the browser dropped the cookie — sameSite: 'None' requires secure: true`. The value is not shown. A cookie set with `expires` in the past is a deletion and passes as before.
29
+
30
+ Migration: add `secure: true` next to `sameSite: 'None'`. A step that relied on the cookie being dropped should delete it with `expires` in the past, or not set it.
31
+
32
+ - 0ae6af4: New: `dsl_lookup` answers a task that is a CLI command's, not a scenario's, with that command. The task is weighed against the commands `npx @unotest/web --help` lists as well as the DSL functions; when a command explains it best, the reply carries `command: {name, synopsis, summary, help}`, a `hint` that says it is a CLI command and not a scenario function, and an empty `functions`. Example: `set up a cron schedule for the suite` returns `schedules`, `log in to the cloud account` returns `login`. Replies for function tasks are unchanged. replaces: reading the `commands` pointer and searching `--help` for the command by hand
33
+
34
+ Fixed: `dsl_lookup` no longer offers `env` and `boundingBox` for "send only the staging environment to a new box", or `env` for "find a typo in a variable name": words that belong to the CLI's commands no longer count as evidence for a function.
35
+
36
+ - 992fb90: BREAKING: an empty value (`ADMIN_BASE_URL=` in `unotest/.env`, not set by the active `--env` overlay) now means the name is not set on that environment. A test that reads the name bare fails with an error that names the variable and the environment, instead of reading `""` — before, `goto(ADMIN_BASE_URL)` quietly opened `APP_BASE_URL` and the test passed. `env('ADMIN_BASE_URL', fallback)` returns the fallback, or `null` without one. A value set by the overlay or the shell is read as before.
37
+
38
+ Migration: a test that reads a name left empty on some environment now fails there. Skip it where the name is missing, at the top of the test: `skip('ADMIN_BASE_URL is not set here', env('ADMIN_BASE_URL', null) == null);` — this works with `--env` and without. A `// @env local, staging` marker above the test is enough only if every run passes `--env`: a run without `--env` ignores the marker and fails the same way.
39
+
40
+ - 83bda13: New: a `snapshot` step for `explore_step` and `explore_steps`, `{action: "snapshot", section, description}`. Its reply carries `outline`, the page outline in the `get_page_snapshot` format, and the refs in it are live for the steps after it. A ref belongs to the snapshot that listed it, so a batch that navigates and then acts by ref puts a `snapshot` step in between: a login with `goto`, `snapshot`, `fill`, `fill`, `click` is one call. The step is never recorded and never appears in the saved test. A server started with `UNOTEST_SNAPSHOT=0` refuses it and says how to locate elements instead. replaces: splitting the batch around a `get_page_snapshot` call
41
+
42
+ Fixed: a stale ref error names only the discovery tools the session has. With snapshots on, it points to `get_page_snapshot` or a `snapshot` step. With the grounder on, it points to the intent step or `ground_element`. With both off, it points to `find_element`. It used to suggest ground mode even when the grounder was off.
43
+
44
+ - 4e5a470: New: `init` writes the idioms to `unotest/e2e/examples/idioms/` — one scenario per habit the DSL has a typed step for (a pause before an absence check, page code for a CSS value, a guessed tab index…), each naming the habit and the step that replaces it, with a README. They ship with the package; a later `init` leaves your edits alone, and `init --force` keeps your version as `.bak`. `llms.txt` lists every idiom with where `init` writes it, and `api` without a word ends with the same pointer. Example: `npx @unotest/web e2e examples/idioms/never-appears`. replaces: nothing
45
+ - d48c5a6: New: each `check_locator` match now names the element the way the page snapshot and `find_element` do. `name` is the accessible name, so a field found by `getByPlaceholder` or labelled by a `<label>` carries its name instead of only `role: textbox`; it is `""` when the element has none. Form fields also report `placeholder` and their current `value`; a password field reports `valueHidden: true` and never its value.
46
+ replaces: a snapshot or a re-run of the test to see whether the locator found the right field
47
+
48
+ Fixed: `find_element` ancestors now carry a `label` with the region label `get_page_snapshot` prints. A form titled by its own heading showed as `form "Employees"` in the snapshot but as a form with an empty name in `ancestors`; it now has `label: "Employees"`, while `name` stays the accessible name that `find_element({ name })` matches.
49
+
50
+ ### Patch Changes
51
+
52
+ - b6f8876: Fixed: in a live debug run, a breakpoint toggled in the viewer reaches the run only after it has been saved. When the save is refused (a box whose breakpoint store is read-only), the mark goes back on screen and the run no longer stops on a line shown without one. The breakpoint store directory can now be set explicitly with `UNOTEST_STATE_DIR`; a box sets it for the viewer and every run. Without it, the directory is found as before. `@unotest/protocol`: `STATE_DIR_ENV`, `stateDirIn` and `runsTreeEnv`.
53
+ - 548aae6: Fixed: `bundle push` no longer refuses a scenario that names a system path such as `/proc/self/status`, `/etc/hosts` or `/dev/null`. The check used to look such a path up on the author's machine, so the same bundle was refused on Linux and accepted on macOS. Now only two places are judged: a file inside the project that the bundle does not carry is still an error, and a file in your home directory outside the project is a warning (the box will not have it). Any other path belongs to the machine and is not checked.
54
+
55
+ Fixed: editor typings now use JavaScript's own library (`"lib": ["es2023", "dom"]`), the one the `lint` type layer already checks against. A scenario runs as plain JavaScript, so `Date`, classes and `Map.prototype.keys` complete in the editor, and `sortBy`, which the scenario engine no longer has, no longer does.
56
+
57
+ Migration: run `npx @unotest/web types` in `unotest/`. A `jsconfig.json` an earlier `init` wrote is brought up to date; until then `lint` and runs remind you in one line. A jsconfig you edited by hand is never rewritten: drop `"noLib"` from `compilerOptions`, set `"lib": ["es2023", "dom"]`, and remove `unotest-lib.d.ts` from `include`. The `types/unotest-lib.d.ts` file still ships, frozen, for this release, so an old jsconfig keeps its completion; it will be removed in a later release.
58
+
59
+ - de4daff: Fixed: reading a declared variable as `globalThis.NAME` no longer hands a silent `undefined` to the next call (`goto(): argument 1 (url) must be a string value, got nothing`). Since 0.55.0 only a bare read reaches the project's variables; the step now fails at the read with `globalThis.NAME does not read the project's variable` and says what to write: the bare name `NAME`, or `env("NAME")` for a value that is not a secret. The value is not shown. A name the project does not declare, or one the scenario sets on `globalThis` itself, reads as before.
60
+ - 0ff8049: Fixed: the last two next steps `init` prints now start with `cd unotest &&`, like the others: `cd unotest && npx @unotest/web init --ci github` and `cd unotest && npx @unotest/web login && npx @unotest/web box create --ttl none`. From the repository root `npx` fetched the latest npm release instead of the version the suite pins.
61
+ - c1872ce: Fixed: the MCP server now says when it is not the `@unotest/web` version the suite installed (`unotest/node_modules`). The line comes in the server's instructions and once, in the first tool reply: `run_test`, `lint` and explore run on the server's version, and `cd unotest && npx @unotest/web init` pins `.mcp.json` to the suite's version. Running `init` again now pins an `npx @unotest/web mcp` entry that has no version. An entry you changed (a local binary, another pin) is kept. When the versions agree, nothing is added.
62
+ - 7e8ee03: New: `sandbox.database` and `sandbox.apiBaseUrl` take `'{{NAME}}'`: the value of `NAME` in the active environment's files (`unotest/.env*`, `unotest/.secrets*`, the shell), read when the run starts. One config now points each environment at its own database or API, with the password in `unotest/.secrets.<env>`. The value is masked in logs. The reference is the whole value; `postgres://u:{{PW}}@host` is refused. A name with no value stops the run before the browser starts, and `lint` reports it on the config file as `lint:external-variable-undeclared`. Under `--env`, an `apiBaseUrl` the overlay leaves to the base `unotest/.env` is refused, as for `goto(NAME)` (`lint:env-host-from-base`). A scenario still cannot point the run at another database. replaces: a script called through `shell()` that reads the connection string from the application's own `.env`
63
+ - 0c73ccb: Fixed: failed checks and timed-out actions now name the locator they were about, with its options. `assertCount`, `assertVisible`, `assertHidden`, `assertNeverAppears` and `waitForCount` end with `for getByRole("button", {name: "Save", disabled: false})`. A timed-out `click`, `fill`, `waitFor` and the other actions start with `click for getByRole(…): ` before Playwright's own words. In a step with several `getByRole` calls, the failure now says which one missed.
64
+ - 0c73ccb: Fixed: `assertText` on a locator that matches no element said "the page gave no answer … (its main thread is busy)". It now says `no element matches getByRole("button", {name: "Save", disabled: false}) within 1000ms`. A present element with other text still fails with `expected … got …`.
65
+ - afefcfb: Fixed: `lint` checks the option keys of `assertScreenshot('page', {…})`, `assertNoFile(path, {…})` and `waitForFile(path, {…})` when the options come second. A typo such as `{maxDifRatio: 0}` or `{withinMS: 100}` used to pass lint silently and is now reported as an unknown option, naming the keys that are supported.
66
+ - 7985139: Fixed: `shell(..., {timeoutMs})` longer than what is left of the test's budget now warns on the step before the command starts. The warning gives both numbers and the `setTestTimeout(…)` that fits the wait. The command still runs. Before, the test was cut off with a bare `testTimeoutMs budget exhausted` that did not name the wait. A literal `timeoutMs` that long was already reported by `lint:wait-exceeds-test-budget`.
67
+ - 7da3404: Fixed: `dsl_lookup` and `unotest-web api` lead from the habits `waitForResponse` replaces to it. "wait until the items request finishes instead of a pause" and "check what the server returned for the items request" now find `waitForResponse` first, and so do `api pause after click` and `api waitUntil networkEntries`, which found no function before. `api pause` and `api sleep` still find `pause` first.
68
+ - 2b9fdbd: Fixed: `lint` without `--env` no longer reports a variable that only `unotest/.env.local`, `unotest/.env.<name>` or `unotest/.secrets.<name>` declares. With no environment chosen, a name any `unotest/.env*` or `unotest/.secrets*` file declares counts. The error stays for a name no file declares. `lint --env <name>` reads the same files as that run, as before.
69
+
70
+ Fixed: `init` no longer ignores `unotest/.secrets.example`. It now writes `!unotest/.secrets.example` right after `unotest/.secrets*`, the same way it keeps `unotest/.env.example`. Running `init` again adds the line to an existing `.gitignore`. `lint` warns when git ignores either template: a fresh checkout would not know the names it declares.
71
+
72
+ Fixed: the `lint:external-variable-undeclared` message, and the "external variable not found" message of a run, now point at the committed template. A credential (a name some `unotest/.secrets*` file holds, or one ending in `_PASSWORD`, `_TOKEN`, `_SECRET` or `_KEY`) goes to `unotest/.secrets.example`, any other name to `unotest/.env.example`. The value still goes to `unotest/.secrets` or `unotest/.env`.
73
+
74
+ - 2009b14: Fixed: a recorded `goto` no longer pins the test to the stand it was recorded on. A URL under the session's base URL renders as a relative path, `goto("/login/")`. A URL under another `*_BASE_URL` variable of the session renders through it, `goto(ITR_BASE_URL + "/login/")`. The longest matching value wins. Two variables with the same value keep the URL literal and add an `AMBIGUOUS_BASE_URL` warning that names both.
75
+
76
+ Fixed: the `explore_step` description and the `write-e2e-test` skills now say that `section` and `description` are always required. In ad-hoc mode (no `explorationId`) they only label the debug log. The docs used to say ad-hoc did not need them, and the schema refused the call.
77
+
78
+ Changed: `lint:goto-concat` now flags only `goto(APP_BASE_URL + ...)`, the variable that feeds the browser's base URL. `goto(ITR_BASE_URL + ...)` for a second host is no longer reported.
79
+
80
+ - 07921d0: Fixed: a value recorded in an exploration started with `env` now renders as the variable it names. `fill(..., "ITR_FLEET")` typed the overlay's value live, but the generated test held the string `"ITR_FLEET"` and failed on its own assertion; it is now `fill(..., ITR_FLEET)`. A bare name that a project env file declares but the session has no value for still goes in as text, and is now said: the step reply carries a `variableWarnings` line naming the file, and the generated test a `VAR_AS_LITERAL` warning. Ad-hoc `explore_step` resolves against the base environment and warns the same way.
81
+ - 094b305: Fixed: `explore_start` now says why intent locators are off in a `grounder.cause` field: `off`, `unreachable`, `models-missing` (with the names in `missing`) or `misconfigured`. With `UNOTEST_GROUNDER_MODE=off`, a deliberate snapshot-only setup, the answer no longer offers the paid Picker or any other command. When a local ollama is running but the configured models are not pulled, the reason no longer says the grounder is unreachable and `orElse` is one `ollama pull` command for the missing models instead of `ollama serve`; the Picker stays in `next`.
82
+ - 48d3c0e: Fixed: `lint:shadows-dsl-function` no longer warns about every variable or parameter named like a DSL function. A variable such as a helper's `check` or `count` parameter is reported only when the code that sees it calls `check()` or `count()` bare, the call the variable takes away. A function of your own with a DSL name is still reported as before.
83
+
84
+ Fixed: `lint:env-host-from-base` no longer reports a host variable that the base `unotest/.env` sets empty (`ADMIN_BASE_URL=`) and the active overlay does not set. An empty value means the host does not exist in that environment, so the advice to list it under `env.shared` was the opposite of what the file says.
85
+
86
+ Docs: every `lint:*` rule now has its own section under "Linter rules" at the end of the DSL reference (`dsl-reference.md`, shipped in the package's `guides/`), moved there from the troubleshooting manual. This includes `lint:env-host-from-base`, in place since 0.43.0 and not named until now: what counts as a host, the three places a variable becomes one, `env.shared`, and what an empty value in the base file means.
87
+
88
+ - 175c2f3: Fixed: the MCP tool `cloud_box_create` now says in its description that a box rented without `ttl` lives for 24 hours by default, and that `ttl: "none"` keeps a CI box. Before, it said only that the cloud's default applies, so an agent renting a box for CI learned the number only from the approval or from `expiresAt`. The CLI plan of `box create` says the same in its own words.
89
+ - 4b713f5: Fixed: a run that just finished no longer goes missing from the viewer's run history until the page is reloaded. The history was read the moment the run ended and could come back before the run had been saved to it; the viewer now reads it again once the run is in, and the WebSocket stream carries a new `fs:run-indexed` message for that.
90
+ - b9edb1a: Fixed: when a test fails, the variables saved for the failed run and a debug pause (and shown in the viewer) no longer hold values of sensitive response headers. Values under credential-like keys, such as `authorization`, `cookie`, `x-csrf-token`, `x-api-key` or `x-auth-*`, are masked as `‹redacted›`; the key stays. The scenario itself still reads the real header value from `waitForResponse`.
91
+ - 1804b45: Fixed: in a narrow history panel, the tally of a collection or file run (`1 ✓ 2 ✗ (1 ‼) 1●`) is no longer cut off at the edge. When it does not fit beside the name, it moves to a second line of the row and stays whole.
92
+ - 8cd94f9: Fixed: `npm audit` in a project that installs `@unotest/web` no longer reports the fastify vulnerabilities the viewer used to bring in. The viewer now runs on NestJS 12 and validates requests itself instead of through `nestjs-zod`, which does not support NestJS 12. Its HTTP API answers as before: an invalid request gets the same 400 body, `{ "statusCode": 400, "message": "Validation failed", "errors": [...] }`.
93
+ - Updated dependencies [b6f8876]
94
+ - Updated dependencies [8f0d1bc]
95
+ - Updated dependencies [20884bc]
96
+ - Updated dependencies [d48c5a6]
97
+ - Updated dependencies [4b713f5]
98
+ - Updated dependencies [1804b45]
99
+ - Updated dependencies [8cd94f9]
100
+ - @unotest/viewer@0.56.0
101
+ - @unotest/protocol@0.56.0
102
+ - @unotest/dsl@0.56.0
103
+ - @unotest/grounder-client@0.56.0
104
+ - @unotest/core@0.56.0
105
+
106
+ ## [0.55.0] - 2026-10-25
107
+
108
+ ### Minor Changes
109
+
110
+ - 4c34192: New: `npx @unotest/web box repo add [url]` maps a repository to its project on a box that already exists, so `bundle push` stops warning that the repository "maps to no project on this box". `box create` has mapped the project's git origin since 0.54.0; a box rented earlier gets the same mapping from this one command, with no operator. The repository defaults to the checkout's git origin, credentials in a URL are never sent, and running it again changes nothing. It uses the project's push token, the one `bundle push` uses: the token decides the project, and a repository another project on the box already holds is refused with that project's name. The `bundle push` warning now ends with this command. The MCP tool `box_repo_add` takes `{url?}` and does the same. The box needs this release's image: an older box answers with the next step, Update in the dashboard.
111
+
112
+ replaces: asking the box's operator to add the repository to the box config by hand
113
+
114
+ ```sh
115
+ npx @unotest/web box repo add
116
+ # ✓ github.com/acme/app maps to project shop on this box
117
+ ```
118
+
119
+ - 0505386: BREAKING: a box rented without a lifetime is now deleted by itself after 24 hours, and charging for it stops then. This is the cloud's default for every client, `@unotest/web` 0.54.0 included: `box create` without `--ttl`, the MCP tool `cloud_box_create` without `ttl`, and the dashboard's create form with its default all rent a box that ends a day later. The owner gets a letter when a box's lifetime ends it. Boxes rented before this change have no lifetime and keep running while they are paid for.
120
+
121
+ Migration: for a box that has to keep running — one CI pushes to — rent it with `npx @unotest/web box create <name> --ttl none` (MCP: `ttl: "none"`; dashboard: Lifetime "No lifetime"), or take the lifetime off one you already rented with `npx @unotest/web box extend <name> --ttl none`.
122
+
123
+ - e8b257d: New: a rented box has a lifetime. `box create --ttl 8h` (or `2d`, up to `30d`) rents a box that is deleted by itself at the end of it, and charging stops there; without `--ttl` the cloud gives a new box 24 hours, and `--ttl none` keeps it until you delete it. `box extend <name> --ttl 4h` moves the end later (`--ttl none` takes the lifetime away); nothing is charged at once, the box keeps being charged by the hour while it runs. `box status` and `box list` show when a box ends, and within the hour before the end `box status` prints the command that extends it. A key that may not spend by itself asks a person for an extension, as it does for a create, and the request shows the lifetime next to the price. The MCP tool `cloud_box_create` takes `ttl`, and the new `cloud_box_extend` takes `{name, ttl}`. In the dashboard, the create form has a Lifetime select, each box shows when it ends next to its price, and Extend moves the end. Update every machine that uses the account: while an extension waits for approval, `box approvals` and the MCP list of waiting requests fail on 0.54.0, which cannot read that kind of request. From this version on, a kind of request the client does not know is listed by name instead.
124
+
125
+ ```sh
126
+ npx @unotest/web box create shop --ttl 8h
127
+ npx @unotest/web box extend shop --ttl 4h
128
+ npx @unotest/web box create ci-box --ttl none
129
+ ```
130
+
131
+ replaces: remembering to run `box destroy` when you are done
132
+
133
+ - 88e1199: BREAKING: a scenario reads a project variable only by its bare name, `APP_URL`, never as a member, `globalThis.APP_URL`. A test read the variable through `globalThis` while the list of variables a bundle reads (`readVariables`, the gaps `push` reports) did not name it, so a push let through a suite whose variable the box did not have. `globalThis.APP_URL` is now `undefined` unless the test also reads `APP_URL` itself; `lint` gives no error on the member form.
134
+
135
+ Migration: read the variable directly: `goto(APP_URL)` instead of `goto(globalThis.APP_URL)`. For a name only known at run time, use `env(name)`.
136
+
137
+ - 4023a82: New: `waitForResponse(glob, {status?, method?, since?, timeoutMs?})` waits for the answer to a request and returns `{url, method, status, ok, headers, json, text}`, so a test can check what an answer draws, or must not, without a `pause`: `click(load); waitForResponse('**/api/items', {status: 200}); assertHidden(item)`. It looks at requests sent from the start of the last call that acted on the page (a click, fill, press, goto, evaluate and the like): a log or an assertion in between moves nothing, the same GET the page made as it loaded is not taken after a later click, and an answer that came before the call is found. Each answer is returned once. `{status}` and `{method}` pass over other answers, and a request that failed is no answer. `{since}` (from `nowMs()`) sets the start instead, for when another action came between the one that sent the request and the wait. A timeout fails the test and names the answers it passed over and why. The answer is in but not yet drawn: to show an element never appears, follow with `assertNeverAppears`. The lint hint on `pause` now names `waitForResponse`. `networkEntries()` entries carry the response `headers` too. replaces: `pause` after a click, and `waitUntil` over `networkEntries`
138
+
139
+ ### Patch Changes
140
+
141
+ - 97be883: Fixed: `click`, `doubleClick` and `press` on a control that closes its own page (a button that runs `window.close()`) no longer fail with "Target page, context or browser has been closed" when the page goes away before the action returns. The action did its work, so the step goes on. An action on a page that was already closed is still an error.
142
+ - 60cea81: Fixed: `box create --help` no longer says the base `unotest/.env` is an environment of its own. Box environments are the `unotest/.env.<name>` overlays; the base file is only the layer they share, and it is the one environment, `default`, only when there is no overlay. When no environment has a public address, `box create` now says what to do: with a public address in `unotest/.env` next to a localhost overlay it explains the layering, and it names where the public `APP_BASE_URL` goes (e.g. `unotest/.env.staging`). `env set` refusing a loopback or private-network target and `cloud_box_create` (its `next`) give the same step.
143
+ - 07e9296: Fixed: the way to a CI box now says the box needs `--ttl none`. The hint `init` ends with reads `box create --ttl none`, `box create` without `--ttl` names the lifetime it rents for (`for 24 hours by default; --ttl none keeps it for CI`), and the docs on running on every push say to rent the box CI pushes to with `box create <name> --ttl none`, or to take the lifetime off one you already rented with `box extend <name> --ttl none`. Before, a box rented as the hint said was deleted a day later and the workflow's pushes failed.
144
+ - f98461f: Changed: the workflow `init --ci github` writes gives its token read access only (`permissions: contents: read`) and pins `actions/checkout` and `actions/setup-node` by commit, with the version in a comment; Dependabot's `github-actions` keeps the pins current. It still runs on every branch, and the file now says why and how to narrow it. A workflow you already have is not changed; `init --ci github --force` writes the new one and keeps yours as `.bak`.
145
+ - 0771c34: Fixed: a scenario that catches a stack overflow (deep recursion, or `JSON.stringify` of a deeply nested value) no longer gets the wrong answers afterwards. An overflow that landed inside a DSL call could leave that call's reply behind, so the next calls silently read the previous call's result, or the run failed with "the main thread raised its reply flag with no reply on the port". Each call now reads its own reply.
146
+ - e8d814f: Fixed: a value nested very deep (a loop that wraps a value in itself, `v = [v]`, fifty thousand times) no longer ends the whole `e2e` command with `Maximum call stack size exceeded` and no verdict. A DSL function handed a value nested deeper than 1000 levels (`log`, `note`, `assertEqual`, any other) refuses it by name, `log: value nested deeper than 1000 levels`, and the test is errored with that reason; the run prints its verdict and summary as for any other error. The Vars view and `inspect_runtime` show such a value cut at 1000 levels, marked `…`. `JSON.stringify` is the engine's own and throws its own `RangeError`, as in any JavaScript. `@unotest/dsl/value` exports the bound and the check, `MAX_VALUE_DEPTH`, `nestedDeeperThan` and `ValueTooDeepError`, and its snapshot cuts a value at that depth.
147
+ - 8eec55d: Fixed: `dsl_lookup` no longer answers a task the DSL has no function for with functions that share one word with it: "sort table rows" got `texts` and `openTerminal`, "run the suite in GitHub Actions on every push" got `clockRun` and `vmRun`. When the functions found hold too little of what the task's words say, the reply has no function, and the pointer to the CLI commands comes first, right after the task.
148
+ - f7385e9: Fixed: three hints `init` gives right after install. The `.bak` that `init --ci github --force` keeps of `.github/workflows/unotest.yml` is now in the `.gitignore` lines `init` writes, so `git status` no longer lists it. The hint to download the bundled Chromium reads `cd unotest && npx @unotest/web install-chromium`, like the other next steps: from the project root, npx takes the npm package, not the version your suite pins. And `unotest/.env.example`, like the `dbQuery` error for a missing driver, installs the database driver into the suite with npm (`cd unotest && npm i -D pg @types/pg`) instead of `pnpm add -D`, which needed pnpm and put the driver in your application.
149
+ - 9dd70f5: Fixed: with `UNOTEST_JUDGE_MODE=local`, the judge now finds its provider key (`GEMINI_API_KEY`, `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`) in `unotest/.secrets` or `unotest/.secrets.<env>`, the files the run header already reported as loaded; an exported variable still wins. Before, a key kept there was ignored and every run that reached `assertJudge` was refused with "requires GEMINI_API_KEY". The same holds for a collection's preflight. The key is handed to the judge only: it is not added to the environment a scenario's `shell()` or a child process inherits. When no key is found, the refusal names every place it looked.
150
+ - 0ff4150: Fixed: `login` on a machine whose key was granted less than a sign-in asks for today — a key from 0.51.0 or earlier, or one with `billing:read` unticked on the approval page — no longer answers "already signed in" and leaves the balance invisible for good. It says what the key is missing, runs the sign-in again, and revokes the old key once the new one is saved; whatever is granted this time is kept as granted. A key set through `UNOTEST_CLOUD_TOKEN` is left alone as before. `whoami` and the price line of `box create` / `box picker on` now say what to do when a key cannot see the money: run `npx @unotest/web login`, or, for a key from the environment, create one with `billing:read` in the cabinet.
151
+ - Updated dependencies [4c34192]
152
+ - Updated dependencies [e8b257d]
153
+ - Updated dependencies [e8d814f]
154
+ - @unotest/protocol@0.55.0
155
+ - @unotest/dsl@0.55.0
156
+ - @unotest/viewer@0.55.0
157
+ - @unotest/core@0.55.0
158
+ - @unotest/grounder-client@0.55.0
159
+
3
160
  ## [0.54.0] - 2026-10-24
4
161
 
5
162
  ### Minor Changes
@@ -2500,7 +2657,7 @@ picker on` fetches this project's own access and writes the three grounder
2500
2657
 
2501
2658
  That screen named one command:
2502
2659
 
2503
- npx @unotest/web bundle push --run --env ENVIRONMENT
2660
+ npx @unotest/web bundle push --run --env ENVIRONMENT
2504
2661
 
2505
2662
  In a project that has just been created, the command refuses with `no box
2506
2663
  address` before it does anything: the project holds neither the box's address
@@ -2509,8 +2666,8 @@ address` before it does anything: the project holds neither the box's address
2509
2666
 
2510
2667
  The screen now names both steps, in the order they have to happen:
2511
2668
 
2512
- npx @unotest/web box access larch
2513
- npx @unotest/web bundle push --run --env ENVIRONMENT
2669
+ npx @unotest/web box access larch
2670
+ npx @unotest/web bundle push --run --env ENVIRONMENT
2514
2671
 
2515
2672
  The box's own name is filled in when its licence carries one. `box access`
2516
2673
  with no name refuses, and its refusal offers to create a box — to somebody who
package/README.md CHANGED
@@ -29,9 +29,9 @@ package; the full reference is at https://docs.unotest.com/reference/dsl/.
29
29
  - **Assertions** — `assertText`, `assertTexts`, `assertAttribute`, `assertVisible`, `assertHidden`, `assertNeverAppears`, `assertValue`, `assertCount`, `assertUrl`, `assertJudge`, `assertScreenshot`, `assertEqual`, `assertTrue`, `assertSchema`, `assertFileHas`, `assertFileLacks`, `skip`, `setTestTimeout`
30
30
  - **Reading the page and values** — `clipboardRead`, `assertClipboard`, `count`, `textContent`, `texts`, `inputValue`, `isVisible`, `isChecked`, `isDisabled`, `isEnabled`, `hasAttribute`, `computedStyle`, `getImageSize`, `hasAnimation`, `animations`, `randomFirstName`, `randomLastName`, `randomEmail`, `randomText`, `randomWord`, `json`, `textContains`, `textJoin`, `nowMs`, `today`, `daysFromNow`, `textMatches`, `parseJson`, `urlParam`, `toNumber`, `round`, `formatNumber`, `env`
31
31
  - **Page state** — `getAttribute`, `getInnerText`, `getInputValue`, `boundingBox`, `getTitle`, `getUrl`, `log`
32
- - **Storage and cookies** — `setLocalStorage`, `getLocalStorage`, `setCookie`, `getCookie`
32
+ - **Storage and cookies** — `setLocalStorage`, `getLocalStorage`, `setCookie`, `getCookie`, `hasCookie`
33
33
  - **Tabs, frames, contexts, extensions** — `setPage`, `waitForPage`, `bringToFront`, `setPageHidden`, `newPage`, `closePage`, `setViewport`, `emulateMedia`, `newContext`, `setContext`, `enterFrame`, `exitFrame`, `addVirtualAuthenticator`, `virtualCredentials`, `removeVirtualAuthenticator`, `grantPermissions`, `setOffline`, `waitForServiceWorker`, `extensionId`, `evaluateInServiceWorker`
34
- - **Data, files, network, processes** — `shell`, `waitForFile`, `assertNoFile`, `waitForJsonLine`, `assertNoJsonLine`, `readJsonLine`, `readJson`, `readFile`, `readFileInfo`, `waitForFileCount`, `assertFileCount`, `dbQuery`, `dbExec`, `apiCall`, `upload`, `mockRoute`, `unmockRoute`, `waitForRequest`, `waitForWebSocket`, `networkEntries`, `assertNoRequest`, `openTerminal`, `setTerminal`, `closeTerminal`, `terminalType`, `terminalClipboardWrite`, `terminalClipboardRead`, `terminalPress`, `terminalWaitForText`, `terminalWaitForExit`, `terminalAssertText`, `terminalResize`, `terminalText`, `terminalScreenshot`, `mcpStart`, `mcpCall`, `mcpWaitNotification`, `mcpStop`, `vmAvailable`, `vmClone`, `vmRun`, `vmIp`, `vmStop`, `vmDelete`
34
+ - **Data, files, network, processes** — `shell`, `waitForFile`, `assertNoFile`, `waitForJsonLine`, `assertNoJsonLine`, `readJsonLine`, `readJson`, `readFile`, `readFileInfo`, `waitForFileCount`, `assertFileCount`, `dbQuery`, `dbExec`, `apiCall`, `upload`, `mockRoute`, `unmockRoute`, `waitForRequest`, `waitForResponse`, `waitForWebSocket`, `networkEntries`, `assertNoRequest`, `openTerminal`, `setTerminal`, `closeTerminal`, `terminalType`, `terminalClipboardWrite`, `terminalClipboardRead`, `terminalPress`, `terminalWaitForText`, `terminalWaitForExit`, `terminalAssertText`, `terminalResize`, `terminalText`, `terminalScreenshot`, `mcpStart`, `mcpCall`, `mcpWaitNotification`, `mcpStop`, `vmAvailable`, `vmClone`, `vmRun`, `vmIp`, `vmStop`, `vmDelete`
35
35
  - **Diagnostics** — `screenshot`, `note`, `consoleEntries`, `pageErrors`, `assertNoConsoleErrors`
36
36
  - **Structure** — `step`, `teardown`, `waitUntil`, `assertNever`
37
37
  - **Page code (last resort)** — `evaluate`, `evaluateOnLocator`
@@ -47,8 +47,9 @@ npm install --prefix unotest
47
47
  ```
48
48
 
49
49
  Run once in your project — any stack (Node, Django, Rails, Go, …), no
50
- `package.json` required. `init` writes the config and a starter scenario,
51
- sets up the browser (it asks: bundled Chromium or your system Chrome;
50
+ `package.json` required. `init` writes the config, a starter scenario and
51
+ the idioms (`unotest/e2e/examples/idioms/`: one scenario per habit, with
52
+ the typed step that replaces it), sets up the browser (it asks: bundled Chromium or your system Chrome;
52
53
  without a terminal to ask in, as in CI, it takes the system Chrome when it
53
54
  finds one), and wires the MCP config so Claude Code / Cursor / Codex
54
55
  pick the server up automatically. Re-run anytime to update — it never
@@ -189,7 +190,9 @@ cd unotest && npx @unotest/web box create # rents a box named after the projec
189
190
  boxes — and keeps the key in `~/.config/unotest/credentials.json`
190
191
  (mode 0600). `box create` creates the box with the environments the
191
192
  suite already runs locally (each `unotest/.env.<name>` and its
192
- `APP_BASE_URL`), waits for the box, writes
193
+ `APP_BASE_URL`; the base `unotest/.env` is only their shared layer, and
194
+ an environment of its own, `default`, only when no overlay exists),
195
+ waits for the box, writes
193
196
  `UNOTEST_BOX_URL` to `unotest/.env` and the push and read tokens to
194
197
  `unotest/.secrets`, pushes the suite and prints the viewer's address.
195
198
  The tokens live thirty days; `bundle push` and `box …` re-mint them
@@ -199,11 +202,20 @@ one of them, and `box logs` the end of a box's own log without logging in to
199
202
  it; `box destroy` does what it says, and `whoami` and `logout` complete the
200
203
  set. In CI, export `UNOTEST_CLOUD_TOKEN` instead of signing in.
201
204
 
205
+ A box has a lifetime: at its end it is deleted by itself and charging
206
+ stops. `box create --ttl 8h` (hours or days, up to `30d`) sets it; without
207
+ `--ttl` the cloud gives a new box 24 hours, and `--ttl none` — what a CI
208
+ box wants — keeps it until it is deleted. `box extend <name> --ttl 4h`
209
+ moves the end later and charges nothing at once. `box status` and
210
+ `box list` show the end, and in the last hour `box status` prints the
211
+ command that extends it.
212
+
202
213
  A box runs only your tests: it does not start your app, which must be
203
214
  reachable at a public address. An environment whose `APP_BASE_URL` is
204
215
  `localhost`, a private network (`10.x`, `192.168.x`, …) or a local-only
205
216
  name (`*.local`, a compose service) stays behind with a note, and
206
- `box create` rents nothing when no environment is left.
217
+ `box create` rents nothing when no environment is left, and says where a
218
+ public address goes instead.
207
219
  `--env <name>` (repeatable) sends only the environments named.
208
220
 
209
221
  On a box the suite's files are read-only and a run may write in two places
@@ -343,6 +355,12 @@ reads a file outside `unotest/`, a missing `unotest/package-lock.json`,
343
355
  no `@unotest/web` pin. The bundle's id is a hash of its content, so
344
356
  pushing an unchanged suite is a no-op.
345
357
 
358
+ A push whose repository maps to no project on the box still lands, with
359
+ a `warning:` naming the project it went to. `box create` maps the git
360
+ origin itself; on a box rented before 0.54.0, map it once with
361
+ `npx @unotest/web box repo add` (the project's push token, the git origin
362
+ by default).
363
+
346
364
  From a CI job, push and run in one command:
347
365
 
348
366
  ```sh