@unotest/web 0.40.0 → 0.42.0

package/CHANGELOG.md

@@ -1,5 +1,434 @@
 # Changelog
 
+## [0.42.0] - 2026-09-24
+
+### Minor Changes
+
+- 8f319b2: `box status` now reports the box's version: what it runs, what its channel
+  offers and where it is between the two.
+
+  A box never updates itself. A new release is offered, not installed — the
+  box keeps running the version it is on until somebody presses **Update** in
+  the cabinet, or an agent calls `POST /api/v1/boxes/<name>/update` with the
+  version it was offered. `box status` prints the offer and says where the
+  decision is made; a cloud that reports no versions leaves the CLI silent
+  about them rather than guessing.
+
+  Migration: boxes that used to install a new release on their own stop doing so
+  with this release. To move a box to a newer version, press **Update** on its
+  card in the cabinet, or call the endpoint above.
+
+- 0c56c6d: Start the browser with a profile and extra arguments — what testing a browser extension needs
+
+  A new `launch` block in `unotest.config`:
+
+  - `launch.args` — extra browser command-line arguments, e.g.
+    `--load-extension=./ext` (extensions load in Chromium only);
+  - `launch.userDataDir` — a browser profile directory. The browser then starts
+    persistent: cookies, storage and installed extensions live in the profile.
+    `UNOTEST_USER_DATA_DIR` overrides it for a machine.
+
+  On a profile there is **no isolation between scenarios**: the browser has one
+  context, and every scenario of a run gets that same context. Each such run says
+  so in its log.
+
+  Refused with a message instead of being ignored: a profile together with
+  `storageState`, a profile in a collection of more than one worker, `launch`
+  on a box (its runs take no launch settings from the suite), and an extension
+  (`--load-extension`) on a headless run of bundled Chromium, whose headless
+  shell ignores extensions without an error. For headless runs with an
+  extension — CI — set the new `channel: "chromium"` (Chromium's new headless
+  mode, which loads them), or `UNOTEST_BROWSER_CHANNEL=chromium`; locally, run
+  headed. Without `launch` nothing changes.
+
+- 1f1dffb: `box envs` and `box run` show how a box installed the suite: how long it
+  took, and whether the packages came from the registry or the box's own
+  npm cache.
+
+  ```
+    acme/test   main@1a2b3c4
+        installed in 12.3s from this box's cache (252 of 252 from cache)
+  ```
+
+  The source is measured by the box, not read out of npm's output: before
+  an install it compares what the lockfile names against what its cache
+  already holds. On a fast registry a cold install and a warm one take the
+  same number of seconds, so the duration alone never said which had
+  happened — the counts are printed with the word so it can be checked.
+  `box run <id>` prints the same line for the bundle that run came from,
+  while the environment still serves it.
+
+  A box older than this contract says nothing about installs, and the
+  output is exactly what it was.
+
+- 7958c4a: Recording tools refuse a misspelled field instead of silently not recording
+
+  `explore_step` with `exploration_id` (instead of `explorationId`) used to run the
+  step ad hoc, answer success and record nothing — the empty session only showed
+  up at `explore_stop`. Every `explore_*` tool, `generate_dsl_from_exploration`
+  and `save_exploration_as_test` now refuse a field they do not declare, including
+  inside an `explore_steps` step, and the error names the field they accept
+  (`exploration_id (did you mean explorationId?)`).
+
+  Ad-hoc execution is unchanged: omit `explorationId`, and the step's reply says
+  `recorded: false`.
+
+  Migration: a client that sent extra, ignored fields to these tools now gets an
+  input error listing the accepted fields — drop the extra ones.
+
+- 92b446f: `box status` says until when the balance keeps a box, not when its paid hour ends
+
+  `box status` used to print `paid until` — the end of the hour already bought.
+  With credit left that read as "switched off within the hour". It now prints
+  `funded until <date> UTC`: the moment the box is deleted if nobody tops up,
+  computed by the cloud from the balance and every box on the account, each at
+  its own rate. A failed box prints neither.
+
+  The cloud API adds `fundedUntil` to each billed box and to `GET /balance` (absent
+  when nothing is billed); `paidUntil` stays, and means only the end of the paid
+  hour. The cabinet's box card and balance show the same date, and the low-balance
+  letter names it.
+
+  Migration: `box status` no longer prints a `paid until` line. A script that read
+  it should take `fundedUntil` from `box status --json` for the deadline, or
+  `paidUntil` there if it meant the end of the paid hour.
+
+- c99f849: The viewer on a box has no terminal panel instead of a dead one
+
+  A box's viewer could never start its docked terminal — the PTY addon is not in
+  the box image — yet it showed the panel and the button. A host that cannot give
+  the terminal a PTY now says so with `UNOTEST_VIEWER_TERMINAL=off`, and the viewer
+  then leaves the terminal out entirely: no panel, no button, no terminal socket,
+  for every session. A box sets it for its viewers.
+
+  Nothing changes locally: the terminal is on by default, and a machine missing
+  the addon still reports it when the panel starts.
+
+### Patch Changes
+
+- 784c10d: A pressed Update reaches the box within minutes, and a failed one is not retried on its own
+
+  A box now checks every five minutes whether it has been asked to move to
+  another version, instead of once an hour, so pressing **Update** in the cabinet
+  (or calling the update endpoint) takes effect within minutes.
+
+  The box also reports back what it runs and how its last update ended —
+  applied, rolled back, refused or failed, and why — which is what the cabinet
+  and `box status` show.
+
+  An update that did not succeed is not tried again by the box itself: rolling
+  back takes the box's stack down and up again, and repeating that unasked would
+  be an automatic update. It is tried again when **Update** is pressed again.
+
+- e0b822a: A reinstall no longer empties the tree a viewer is serving
+
+  A bundle whose tree already has packages is reinstalled in a copy while the
+  live tree waits aside; the viewer keeps serving it. A failed reinstall leaves
+  the live `node_modules` untouched instead of leaving the viewer answering 404
+  until an install succeeds. A tree a daemon left aside when it died mid-install
+  is put back by the next housekeeping sweep.
+
+- 96e4977: A box that names no environments is told so, instead of being sent a name
+  it cannot match.
+
+  `box runs`, `box queue`, `box run` and the rest used to pass the name on to
+  a box with an empty list, which answered 404 and advice about the form of a
+  name — spelling advice to somebody whose box has nothing to spell. They now
+  say what is true: the box names no environments yet, a run ordered a moment
+  ago may not be listed straight away, and a box that goes on naming none has
+  none configured. Agents get the same sentence through the `box_*` MCP tools.
+
+  The command exits 2, like the other refusals of an environment name (was 1).
+
+  Migration: a script that checked for exit code 1 on this refusal should check
+  for 2.
+
+  `bundle push --run` is unchanged: it uploads and lets the box decide, because
+  a box older than this contract names nothing until its first run. What
+  changed there is the hint after the box's own refusal, which no longer points
+  back at the list that was empty.
+
+- d1ecff6: A box lists its environments before the first suite arrives
+
+  The route table names every configured environment; one without a bundle is
+  listed without an address. `/_guard/api/envs` answers with it at once
+  (`note: "no suite yet"`), so an environment name can be checked before the
+  first push, and opening it in a browser shows a page with the commands that
+  send a suite instead of a bare 503.
+
+  Migration: the environment list a read token gets (`box envs`, the `box_envs`
+  MCP tool) now also names environments that have no suite yet, with the note
+  `no suite yet`. Reading one of them answers `unavailable` until a suite is pushed.
+
+- Updated dependencies [c99f849]
+  - @unotest/viewer@0.42.0
+  - @unotest/core@0.42.0
+  - @unotest/dsl@0.42.0
+  - @unotest/grounder-client@0.42.0
+  - @unotest/protocol@0.42.0
+
+## [0.41.0] - 2026-09-21
+
+### Minor Changes
+
+- e793fa2: `env push | set | rm`: the box and the token come from the project's own files
+
+  The values commands now resolve the box address and the project token
+  exactly the way `bundle push` does — a flag, then `UNOTEST_BOX_URL` /
+  `UNOTEST_BOX_TOKEN`, then `unotest/.env` and `unotest/.secrets`, where
+  `box create` and `box access` wrote them. A project set up with either of
+  those commands no longer answers "no box address" to `env push` while
+  `bundle push` works, and the two exports stop being typed in front of
+  every line.
+
+  `env set <env> <NAME> <value>` takes the value as an argument. Stdin
+  still works when there is none, and stays the way to pass a credential:
+  an argument is in the shell's history.
+
+  `env push --dry-run` now prints what the overlays resolved to, quoted, so
+  a value that kept its quotes or picked up a trailing space is visible
+  before it reaches a box. `--dry-run --json` carries the same under
+  `values`. A secret's value is still never printed: where it would be, the
+  mask used everywhere else (`‹secret:NAME›`) stands instead.
+
+  A push whose box lacks some of the suite's declared values no longer
+  claims the run "will stop at the first step that reads" one of them: the
+  names are what the suite DECLARES, and a declared name no scenario reads
+  costs a run nothing.
+
+- 41b0369: A box rented from the dashboard now says how to send it a suite
+
+  A box rented from the CLI arrives with the suite already on it: `box create`
+  pushes it and prints the command that runs it. A box rented from the dashboard
+  arrives empty, and the card said nothing about that. It showed the address, the
+  login and the password, and left the customer with a machine that answers, an
+  empty viewer, and no idea that anything else was needed. Everything they had to
+  do next lived in an email and on the box's own empty screen.
+
+  The card of a ready box now carries the three commands that take a project from
+  here to a first run: sign in, take the box's tokens, push the suite. Each is a
+  field that can be copied in one click, with the box's own name already in it.
+  The environment name is filled in when the box has exactly one, and left as
+  `<env>` when it has several — picking one for the customer would send the run
+  to a site they did not mean, and nothing would refuse it, because the name is
+  perfectly valid. The collection is named too: a box runs a collection, not a
+  single scenario, and a push that names none is turned away.
+
+  Those commands are now written in one place and printed by both the card and
+  the "your box is ready" letter. They used to be the letter's alone, and a
+  second copy on the card would have been a second piece of advice the first time
+  either was edited.
+
+  Once a project has taken the box's tokens, the card stops repeating the first
+  two commands and asks only for the push. That is the one thing the cloud can
+  honestly know about the far end of a box: the suite travels from the customer's
+  machine straight to it, and nothing reports back. So the card says nothing at
+  all about runs — not "no runs yet", not "0 runs". It cannot tell a box that has
+  been testing for a week from one nobody has touched, and a page that says
+  otherwise is inventing it.
+
+### Patch Changes
+
+- 36bc4b3: An empty list of environments says which kind of empty it is
+
+  `box envs` on a box that listed nothing said "This box serves no environments
+  you can read." — a sentence about the token, on a list that is not filtered by
+  the token at all. People whose box was simply new went looking for a stronger
+  credential, and the box's own journal had nothing to say either way.
+
+  The list now talks about the box:
+
+      This box serves no environments yet.
+        An environment appears once a suite has been pushed to it.
+
+  A token that really is not let in still answers in its own words, with its own
+  exit code, so the two are told apart by reading them.
+
+  Behind the list, the box now records which of five things happened when it
+  looked for its route table: there is no table yet, the table cannot be read,
+  it is not JSON, its shape is wrong, or it is honestly empty. Each is one line
+  in the box's journal, naming the file and never its contents — the table holds
+  internal addresses. A table that loaded says how many environments it found,
+  because "none" and "three" were otherwise the same silence.
+
+  Two fixes come with it. A line belongs to a state rather than to a request, so
+  a busy box writes one line and not one per proxied asset. And a table that
+  failed to parse is read again a second later instead of being remembered as an
+  empty box until its timestamp changes — which is why "I tried again and it was
+  the same" used to be true.
+
+  An empty list stays a successful answer, `200` with no entries: a box with
+  nothing on it yet is a normal box, not a service that is down.
+
+- 7bac819: A box installs a suite whose `npm ci` is slow, and stops retrying in a loop
+
+  A box could not install a suite whose dependency install went quiet for
+  more than five minutes — which is what a heavy lockfile does. The install
+  died on the 301st second, reported the runner as unavailable, and the box
+  started the whole install again in the second it failed. That repeated for
+  as long as the box existed: nothing ever ran on it, and the message blamed
+  the network rather than naming the timeout that caused it.
+
+  Three things change. The daemon no longer puts a ceiling of its own on
+  reading a run's output, so silence is not a failure; the run's deadline
+  remains the only clock that ends a run, and a backstop behind it covers a
+  connection that stops answering altogether. A run whose output stops
+  without an exit now takes its container with it — abandoned containers
+  used to fill the box's capacity while healthy environments waited for a
+  slot. And a failed install is followed by a pause that grows: 1, 2, 5, 15
+  and 30 minutes, capped there, never "never". Asking for that bundle
+  yourself — a switch or a repair — is tried at once and clears the count,
+  as does an install that succeeds, and the log says when the box will try
+  next by itself.
+
+  The pause is the box's own, never yours: a run you order by hand, and a run
+  a push to your repository orders, install the bundle at once and clear the
+  count. Only the box's unattended retry waits.
+
+- 7880b7d: Installs on a box share one npm cache, and a suite can never reach it
+
+  Until now every install on a box started with an empty npm cache: the
+  container that runs `npm ci` was thrown away with everything it had
+  downloaded, so the second box of the same account — and the same box
+  after a restart — paid the full download again for dependencies it had
+  already had twice.
+
+  Boxes now keep one npm cache and every install uses it. The second
+  install of a dependency is taken from disk instead of the network; how
+  much time that saves depends on your lockfile and your registry, and on a
+  fast registry it can be none at all — the promise here is only that
+  what has already been downloaded is not downloaded again.
+
+  The cache is mounted into the container that installs, and into no other.
+  A container running your suite gets no access to it under any name: the
+  cache is the directory that every later install of every project on that
+  box unpacks, and a test that could write into it would be writing into
+  the next install. That boundary is asserted as a pair — the install has
+  it, the run does not — rather than as two separate claims.
+
+  A substituted cache entry is never installed. npm verifies an entry's
+  checksum when it READS from the cache, not only when it writes one: an
+  entry whose content does not match is reported as corrupted and fetched
+  again (verified on the box's own image, npm 11.16.0 — with a registry
+  reachable the correct package is installed; without one the install fails
+  rather than using the substitute).
+
+  The box keeps the cache's size in hand. It is measured on each
+  housekeeping sweep and, over the ceiling (1 GB by default, and an
+  operator can raise it or turn it off), emptied whole with a line in the
+  log — losing a cache costs a download and nothing else.
+
+- d456001: Ordering a run in an environment now decides what that environment serves
+
+  Pushing a suite and asking for a run in a named environment is a
+  statement about that environment: it should serve the bundle you just
+  sent. Until now the box decided that separately, by matching the
+  bundle's branch — so a suite packed outside a git repository, which is
+  what `init` produces in a clean directory, matched nothing. The run
+  installed, executed and passed, while the environment kept pointing at
+  nothing: its viewer was never started, the guard was given no route for
+  it, `box envs` listed nothing, and `box runs --env <name>` answered that
+  the box does not serve that environment. Four different answers to one
+  question, after the client had been told the suite was accepted and
+  queued.
+
+  An explicit run request now selects the bundle for the environment,
+  through the same path a selection made in the viewer takes, recorded
+  against the token that pushed — so it survives a restart and the box
+  does not silently move the environment back on its next sweep. Branch
+  matching keeps deciding exactly one thing, the one it is right for:
+  which bundle the environment's SCHEDULES run.
+
+  An environment that may not be switched (`allowSwitch: false`) keeps
+  serving what its own branch deploys, and the answer now says so instead
+  of leaving it to be found out: the run goes ahead there, and the
+  acceptance names the branch the environment stays on — so it is clear
+  the result belongs to that environment's journal rather than to the
+  screen the environment shows.
+
+  The one case with nothing to show is refused out loud. An environment
+  that may not be switched and serves nothing yet has no viewer at all, so
+  a run ordered there could only end where this bug ended: executed, green
+  and invisible. The refusal names the branch to deploy to instead.
+
+  Migration note: that refusal is a new error code on the run endpoint.
+  A CLI older than this release does not know it and will report the
+  box's answer as "not a box" rather than as a refusal — the request is
+  still refused, and nothing runs. Upgrade the CLI to see the message.
+  The acceptance note is a new field on an otherwise unchanged answer, and
+  an older CLI ignores it.
+
+- 436b683: The box's own screen gives the same first-run command as everything else
+
+  A freshly rented box shows two commands: one that points the project at the
+  box, one that sends the suite and starts it running. The second was printed
+  without `--collection`, and a box runs a collection or a schedule — never a
+  scenario by name. Copied exactly as shown, into a project straight out of
+  `init`, it came back refused with nothing to run: an answer about a project
+  that had done nothing wrong, from the first screen a new box owner reads.
+
+  The screen now prints the whole command, and says where collections live:
+
+      npx @unotest/web bundle push --run --env ENVIRONMENT --collection examples
+
+  The command is no longer written out on each surface that shows it. The box's
+  screen, the last line of `box create`, and the collection `init` writes all
+  come from one place, so the next flag to change changes in one edit rather
+  than in three. `examples` is the collection `init` creates, and the screen
+  says so — it is an example of a name, not a claim about your project.
+
+  The cabinet half is unchanged in behaviour: with exactly one environment and
+  one collection it still prints a command that can be pasted as is, and
+  placeholders where it cannot know.
+
+- 3d8e45d: `unotest/.secrets` is now created owner-only (`0600`)
+
+  The file holds the box push and read tokens, and was created with the
+  default umask — on a shared machine any other user could read it. It is
+  now narrow from the moment it is created, and a file left wider by an
+  earlier version is narrowed the next time a command writes to it, with one
+  line saying what changed. `unotest/.env` is configuration rather than
+  secrets and keeps the width your project gave it.
+
+- 8a436b9: Exploration tools refuse an unknown `{{NAME}}` instead of typing it
+
+  A `{{NAME}}` the session could not resolve was passed through as text, so
+  `explore_run_flow {args:["admin","{{PASSWORD}}"]}` typed the placeholder
+  into the password field and the page answered with a normal login failure.
+  It now fails with a message that names the variable, says where to declare
+  it, and lists the names the session does have — so the value never has to
+  be pasted into the tool call by hand.
+
+  A bare `SHOUTY_NAME` is unchanged: a reference where it is registered, a
+  literal otherwise. A variable declared with an empty value still
+  substitutes as empty and is reported in `variableWarnings`; a name
+  declared as a secret with an empty value is refused with its own message.
+
+- a1b9eac: Editing a secret in the viewer's variables panel keeps `unotest/.secrets` owner-only
+
+  The panel writes a file by creating a temporary one beside it and renaming
+  it into place, and a rename replaces the target together with its
+  permissions. So a secrets file that was owner-only became world-readable
+  again after a single edit in the panel, with the box tokens inside it, and
+  adding the first secret to a project created the file wide in the first
+  place.
+
+  The temporary file is now created owner-only when the layer being written
+  holds secrets, which also narrows a file an earlier version left wide. A
+  leftover temporary file from an interrupted write is removed rather than
+  reused, so it cannot pass its own permissions on. `unotest/.env` is
+  configuration rather than secrets and keeps the width your project gave it.
+  On Windows there are no POSIX permission bits and nothing is narrowed
+  there.
+
+- Updated dependencies [436b683]
+- Updated dependencies [a1b9eac]
+  - @unotest/protocol@0.41.0
+  - @unotest/viewer@0.41.0
+  - @unotest/core@0.41.0
+  - @unotest/dsl@0.41.0
+  - @unotest/grounder-client@0.41.0
+
 ## [0.40.0] - 2026-09-19
 
 ### Minor Changes
@@ -389,7 +818,7 @@ picker on` fetches this project's own access and writes the three grounder
 
   That screen named one command:
 
-        npx @unotest/web bundle push --run --env ENVIRONMENT
+            npx @unotest/web bundle push --run --env ENVIRONMENT
 
   In a project that has just been created, the command refuses with `no box
 address` before it does anything: the project holds neither the box's address
@@ -398,8 +827,8 @@ address` before it does anything: the project holds neither the box's address
 
   The screen now names both steps, in the order they have to happen:
 
-        npx @unotest/web box access larch
-        npx @unotest/web bundle push --run --env ENVIRONMENT
+            npx @unotest/web box access larch
+            npx @unotest/web bundle push --run --env ENVIRONMENT
 
   The box's own name is filled in when its licence carries one. `box access`
   with no name refuses, and its refusal offers to create a box — to somebody who

package/README.md

@@ -34,6 +34,11 @@ self-installs on the first `lint` / `e2e` run after upgrading; refresh by
 hand with `npx @unotest/web types`. Details: the "Editor setup" section of
 `node_modules/@unotest/web/guides/dsl-reference.md`.
 
+Testing a browser extension? `launch` in `unotest.config` starts the browser
+with a profile (`userDataDir`) and extra arguments (`args`, e.g.
+`--load-extension=./ext`; Chromium only). On a profile every scenario shares
+one browser context — no isolation between them, and the run log says so.
+
 ## 2. Open the viewer
 
 ```sh
@@ -182,6 +187,27 @@ Picker is on — which models the cloud grounds with: `Our GPU` or
 `UNOTEST_GROUNDER_MODE`; a cloud that has not heard from its grounder
 prints nothing rather than a guess.
 
+**How a suite got installed is visible too.** `box envs` prints, under
+each environment, how long the box took to install its bundle and where
+the packages came from — `installed in 12.3s from this box's cache (252
+of 252 from cache)`. `box run <id>` prints the same line for the bundle
+that run came from, while the environment still serves it. The source is
+the box's own measurement (what its npm cache already held of what the
+lockfile names), not a reading of npm's output: on a fast registry a cold
+install and a warm one take the same number of seconds, so the time alone
+proves nothing. A box that says nothing about installs — one older than
+this — prints nothing extra.
+
+**A box never updates itself.** `box status` prints its version — what it
+runs, and what its channel offers when the two differ. A new release is an
+offer: the box keeps running what it is on until somebody presses **Update**
+on its card in the cabinet, or an agent calls
+`POST /api/v1/boxes/<name>/update` with the version it was offered (a
+version that has since been overtaken is refused, with the one that is on
+offer now). There is no `box update` command: the decision is a person's,
+and the cabinet is where it is made. A cloud that reports no versions leaves
+`box status` silent about them.
+
 **Without a box.** An account can have the Picker on with no box rented
 at all; the switch and the price for that live in the cabinet, and
 `picker on` connects THIS project to it — it fetches the project's own
@@ -253,13 +279,18 @@ run reads:
 
 ```sh
 npx @unotest/web env push dev                 # .env + .env.dev + .secrets + .secrets.dev
+npx @unotest/web env set dev REGION eu-west
 printf '%s' "$KEY" | npx @unotest/web env set dev API_KEY --secret
 ```
 
 `.env*` become the environment's variables, `.secrets*` its secrets,
-`APP_BASE_URL` its target; `UNOTEST_*` stay home. A value never prints.
-The token must be minted with `--values` on the box. Admins also see and
-change them on the box's admin page. Manual: [An environment's values on a
+`APP_BASE_URL` its target; `UNOTEST_*` stay home. A secret's value never
+prints; `env push --dry-run` shows what the other values resolved to. The
+box and the token come from the same places `bundle push` reads them
+from — flags, the environment, then `unotest/.env` and
+`unotest/.secrets` — and the token must be minted with `--values` on the
+box. Admins also see and change them on the box's admin page. Manual: [An
+environment's values on a
 box](https://docs.unotest.com/box/environments-and-values/).
 
 A run on the box happens inside the box's own container: nothing on your
@@ -309,6 +340,16 @@ file; `--box` and `--token` win over both.
 The token is never read from `unotest/.env` — that file travels inside a
 pushed bundle, and `.secrets` does not.
 
+`unotest/.secrets` is created owner-only (`0600`), so the tokens in it are
+not readable by other users of a shared machine. A file left wider by an
+earlier version is narrowed the next time a command writes to it, and the
+command says so once. Editing a secret in the viewer's variables panel
+keeps the same width. `unotest/.env` is configuration, not secrets, and
+keeps whatever width your project gave it.
+
+On Windows there are no POSIX permission bits, so nothing is narrowed there
+and no width is promised: protect the file with the tools your system has.
+
 Keeping it in the file is what lets your agent read runs: an MCP server is
 started by your editor, so a token that only exists in your shell is a
 token the agent never sees. A token added while the server is running is
@@ -320,7 +361,12 @@ hand you mint it for yourself on the box's guard, where it is shown once
 and can be revoked. Either way it is read-only whatever your role on the
 box — it cannot start a run or change a value. `UNOTEST_BOX_TOKEN` is the
 project's push credential and cannot read runs. `box envs` lists the
-environments a token may look at.
+environments the box serves — an empty list means the box has none yet,
+not that the token is too weak to see them. The commands that name one
+(`box runs`, `box queue`, `box run`, …) say the same thing rather than
+sending the name to a box that has nothing to match it against: a box
+that names none has none configured, which is ours to put right. A run
+you have just ordered may take a moment to appear.
 
 ## 5. Watch it run — the viewer
 

package/dist/config/schema.d.ts

@@ -10,7 +10,7 @@ type Browser = z.infer<typeof BrowserSchema>;
  *  Ignored for firefox / webkit browsers (Playwright has no system
  *  channel for those). Chosen at init time via the browser prompt;
  *  user can flip later in unotest.config.{mjs,js,ts}. */
-declare const BrowserChannelSchema: z.ZodOptional<z.ZodUnion<[z.ZodLiteral<"chrome">, z.ZodLiteral<"msedge">, z.ZodLiteral<"chrome-beta">, z.ZodNull]>>;
+declare const BrowserChannelSchema: z.ZodOptional<z.ZodUnion<[z.ZodLiteral<"chrome">, z.ZodLiteral<"msedge">, z.ZodLiteral<"chrome-beta">, z.ZodLiteral<"chromium">, z.ZodNull]>>;
 type BrowserChannel = z.infer<typeof BrowserChannelSchema>;
 declare const ViewportSchema: z.ZodObject<{
     width: z.ZodNumber;
@@ -260,7 +260,7 @@ declare const UnotestConfigSchema: z.ZodObject<{
         reuseExistingServer?: boolean | undefined;
     }>>;
     browsers: z.ZodArray<z.ZodEnum<["chromium", "firefox", "webkit"]>, "many">;
-    channel: z.ZodOptional<z.ZodUnion<[z.ZodLiteral<"chrome">, z.ZodLiteral<"msedge">, z.ZodLiteral<"chrome-beta">, z.ZodNull]>>;
+    channel: z.ZodOptional<z.ZodUnion<[z.ZodLiteral<"chrome">, z.ZodLiteral<"msedge">, z.ZodLiteral<"chrome-beta">, z.ZodLiteral<"chromium">, z.ZodNull]>>;
     viewport: z.ZodObject<{
         width: z.ZodNumber;
         height: z.ZodNumber;
@@ -271,6 +271,19 @@ declare const UnotestConfigSchema: z.ZodObject<{
         width: number;
         height: number;
     }>;
+    /** How the browser is started: a profile and extra arguments
+     *  (`config/launch.ts`). Unset → as before: a fresh browser, a fresh
+     *  context per scenario. */
+    launch: z.ZodOptional<z.ZodObject<{
+        userDataDir: z.ZodOptional<z.ZodString>;
+        args: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
+    }, "strict", z.ZodTypeAny, {
+        args?: string[] | undefined;
+        userDataDir?: string | undefined;
+    }, {
+        args?: string[] | undefined;
+        userDataDir?: string | undefined;
+    }>>;
     retry: z.ZodObject<{
         count: z.ZodNumber;
         on: z.ZodArray<z.ZodEnum<["transient", "network", "crash"]>, "many">;
@@ -454,6 +467,8 @@ declare const UnotestConfigSchema: z.ZodObject<{
         uploadDir?: string | undefined;
     }>;
 }, "strip", z.ZodTypeAny, {
+    defaultTimeoutMs: number;
+    defaultNavigationTimeoutMs: number;
     browsers: ("chromium" | "firefox" | "webkit")[];
     viewport: {
         width: number;
@@ -479,8 +494,6 @@ declare const UnotestConfigSchema: z.ZodObject<{
     dialogPolicy: "accept" | "dismiss" | "manual";
     testDir: string;
     helpersDir: string;
-    defaultTimeoutMs: number;
-    defaultNavigationTimeoutMs: number;
     linter: {
         enabled: boolean;
         rules: Partial<Record<"lint:deep-css" | "lint:xpath" | "lint:obfuscated-class" | "lint:pause-explicit" | "lint:disambig-by-index" | "lint:evaluate-discouraged" | "lint:scenario-in-root" | "lint:mustache-in-dsl" | "lint:goto-concat" | "lint:regex-invalid" | "lint:echo-assert" | "lint:api-call-file-body" | "lint:lint-ok-missing-reason" | "lint:flow-returns-value" | "lint:legacy-layout" | "lint:external-variable-undeclared" | "lint:one-test-per-file" | "validator:unknown-function" | "validator:arity" | "validator:arg-kind" | "validator:step-coverage" | "validator:step-shape" | "validator:meta-shape" | "validator:function-shape" | "validator:for-shape" | "validator:if-shape" | "validator:var-shape" | "validator:unsupported-statement" | "validator:unsupported-expression" | "validator:string-concat" | "validator:semantic-loss" | "validator:list-arg" | "validator:wrapped-format", "off" | "warn" | "error">>;
@@ -513,9 +526,15 @@ declare const UnotestConfigSchema: z.ZodObject<{
         command: string;
         reuseExistingServer: boolean;
     } | undefined;
-    channel?: "chrome" | "msedge" | "chrome-beta" | null | undefined;
+    channel?: "chrome" | "msedge" | "chrome-beta" | "chromium" | null | undefined;
+    launch?: {
+        args?: string[] | undefined;
+        userDataDir?: string | undefined;
+    } | undefined;
     storageState?: string | undefined;
 }, {
+    defaultTimeoutMs: number;
+    defaultNavigationTimeoutMs: number;
     browsers: ("chromium" | "firefox" | "webkit")[];
     viewport: {
         width: number;
@@ -541,8 +560,6 @@ declare const UnotestConfigSchema: z.ZodObject<{
     dialogPolicy: "accept" | "dismiss" | "manual";
     testDir: string;
     helpersDir: string;
-    defaultTimeoutMs: number;
-    defaultNavigationTimeoutMs: number;
     linter: {
         enabled: boolean;
         rules: Partial<Record<"lint:deep-css" | "lint:xpath" | "lint:obfuscated-class" | "lint:pause-explicit" | "lint:disambig-by-index" | "lint:evaluate-discouraged" | "lint:scenario-in-root" | "lint:mustache-in-dsl" | "lint:goto-concat" | "lint:regex-invalid" | "lint:echo-assert" | "lint:api-call-file-body" | "lint:lint-ok-missing-reason" | "lint:flow-returns-value" | "lint:legacy-layout" | "lint:external-variable-undeclared" | "lint:one-test-per-file" | "validator:unknown-function" | "validator:arity" | "validator:arg-kind" | "validator:step-coverage" | "validator:step-shape" | "validator:meta-shape" | "validator:function-shape" | "validator:for-shape" | "validator:if-shape" | "validator:var-shape" | "validator:unsupported-statement" | "validator:unsupported-expression" | "validator:string-concat" | "validator:semantic-loss" | "validator:list-arg" | "validator:wrapped-format", "off" | "warn" | "error">>;
@@ -569,7 +586,11 @@ declare const UnotestConfigSchema: z.ZodObject<{
         timeoutMs?: number | undefined;
         reuseExistingServer?: boolean | undefined;
     } | undefined;
-    channel?: "chrome" | "msedge" | "chrome-beta" | null | undefined;
+    channel?: "chrome" | "msedge" | "chrome-beta" | "chromium" | null | undefined;
+    launch?: {
+        args?: string[] | undefined;
+        userDataDir?: string | undefined;
+    } | undefined;
     storageState?: string | undefined;
     schedules?: {
         collection: string;