@unotest/viewer 0.19.0 → 0.21.0

package/CHANGELOG.md

@@ -1,5 +1,129 @@
 # Changelog
 
+## [0.21.0] - 2026-08-25
+
+### Minor Changes
+
+- 174d27e: feat: environments are first-class in the viewer — a switcher, per-env run history
+
+  **Run artifacts are laid out per environment, as folders.** Each
+  environment's history lives in its own root, mirroring the env-file
+  scheme: `unotest/.runs` (base), `unotest/.runs.<env>` (e.g.
+  `.runs.staging` for `--env staging` / `UNOTEST_ENV=staging`); the axes
+  compose — `.runs-mobile.staging`. Indexes (`_day.jsonl`, `_latest.json`)
+  are per-env automatically: switching environments is a change of root,
+  not a filter and not a rebuild. Old runs stay in `.runs` (= base), no
+  migration needed. `runsDirFor` / `projectRunsRoot` / `projectRunDirFor`
+  gained an optional `envName` parameter; the run manifest carries `env`
+  for self-description. Make sure your `.gitignore` uses the wildcard
+  form — `unotest/.runs*/` (`init` already writes it that way for new
+  projects).
+
+  **The viewer knows about environments.** A new switcher sits at the top
+  of the Variables panel and in the status bar: base plus every
+  environment discovered from `unotest/.env.<name>` / `.secrets.<name>`
+  (`.env.example` and other templates do not count). The active
+  environment is server-side (`GET/POST /api/environments`), and all tabs
+  converge via the `env:changed` WS message:
+
+  - the Variables panel shows layers WITH the active environment's
+    overlay (previously base only); values coming from `.env.<name>`
+    carry a badge; an edit goes to the file where the key is defined; new
+    variables go to base;
+  - Overview and the Runs list show only the active environment — tiles
+    are colored by the latest run in that environment;
+  - a run started from the viewer gets the active environment's
+    `UNOTEST_ENV` (`RunRequest.env` is a per-request override);
+  - a run opened from another environment still resolves by runId across
+    all `.runs*` roots.
+
+  MCP: `run_test {env}` already switched the child process's environment;
+  its artifacts are now correctly found by the server in `.runs.<env>`
+  (inspect/step/attach/list_runtimes scan all roots).
+
+  Four fixes uncovered while shaking this down:
+
+  - **The `--env` overlay actually reaches the run.** Long-lived hosts
+    (viewer, MCP server) flattened the base `.env` into their own
+    `process.env` on `loadConfig`; children inherited it as ambient
+    (ambient beats files) — the overlay's `APP_BASE_URL` was silently
+    clobbered by the base value. The viewer now rolls its env back after
+    loading the config; MCP spawns children from a clean pre-flatten
+    snapshot.
+  - **Pause/Abort from the viewer work again.** Debug commands were
+    written to the flat `<root>/<runId>/commands.jsonl`, while runs have
+    lived in date shards since 0.19 — the write 404'd and abort was
+    silently ignored. Order fixed too: SIGTERM to the own process first
+    (tests AND collections), then the command file.
+  - **A collection no longer "dies" in the UI after 30 seconds.** The
+    parent run wrote no heartbeat — the monitor declared it interrupted,
+    the row vanished from ACTIVE and the tail detached. The orchestrator
+    now maintains the heartbeat (shared machinery in `@unotest/core`),
+    and the viewer additionally treats a flowing steps.jsonl as a sign of
+    life (compatibility with older runners).
+  - **No phantom `failed` after a clean exit.** The "child exited without
+    artifacts" check looked at the flat path and fired bogus
+    `run-finished: failed` events plus an error toast on every exit.
+
+### Patch Changes
+
+- Updated dependencies [174d27e]
+  - @unotest/protocol@0.21.0
+  - @unotest/dsl@0.21.0
+
+## [0.20.0] - 2026-08-24
+
+### Minor Changes
+
+- 7957469: A status of its own for tests that are supposed to fail, and tiles that fade with age.
+
+  **`// @expect-fail`.** A scenario can declare that failing IS its assertion.
+  The marker lives in the comment block before the first code — with the
+  mandatory header (right after the colour line) or without one. The parser is
+  `parseScenarioAnnotations` in `@unotest/protocol`; `ScenarioMeta` gains an
+  `expectFail` field.
+
+  Such a scenario carries its own status in the viewer (`expected`, purple):
+  it stays out of the FAILED counter, out of the "failing now" badge and out
+  of the "Failing now" section. The inverse case — a marked test that
+  **passed** — turns red: whatever it was guarding stopped breaking and nobody
+  found out. One rule (`scenarioHealthStatus`) drives the dashboard, the
+  scenario tree and the badge, so the three cannot drift apart.
+
+  The runner does not interpret the marker: exit code and run status are
+  unchanged. The run really did fail — it is the test itself that is fine.
+
+  **Fading.** An overview tile dims as its last result ages: four steps (hour /
+  day / week / older) set the strength of the fill itself — 46 / 30 / 19 / 11%
+  of the status colour. The 11% floor keeps an old red still red. The time of
+  the last run is now part of the tile's accessible name — colour is the one
+  channel a screen reader does not have.
+
+### Patch Changes
+
+- aab65a5: A failure in the first test of a file is no longer lost, and the dashboard no longer waits for F5.
+
+  **One run, one `run:finished`.** The event was written by the executor's
+  per-entry tap, so a file with four `test_*()` functions left four terminal
+  events in `steps.jsonl`. Every consumer reads the last one — so `collection`
+  reported a scenario green whenever the final function passed and the first
+  one failed. The runner now writes the event once, folding the outcomes of
+  every entry: `failed` > `interrupted` > `aborted` > `completed`. A run that
+  never got started (no entry function, browser failed to launch) writes a
+  terminal event too — its artifact used to read as "the process died".
+
+  **The viewer asks for the index again.** The first `load()` could land while
+  the server was still rebuilding the run index: the answer was "no runs", and
+  nobody asked again — WS only reports a run starting and finishing. On a
+  project with history the whole overview showed "never run" until a page
+  reload. `indexReady: false` now schedules a retry with a 0.5s → 30s backoff,
+  until the first ready answer.
+
+- Updated dependencies [7957469]
+- Updated dependencies [c6efd92]
+  - @unotest/protocol@0.20.0
+  - @unotest/dsl@0.20.0
+
 ## [0.19.0] - 2026-08-23
 
 ### Minor Changes

package/dist/server/main.d.ts

@@ -23,6 +23,9 @@ interface StartViewerOptions {
     /** Target id selected at boot (`web`/`mobile`/…). Defaults to the first
      *  available runner. */
     activeTarget?: string;
+    /** Environment name selected at boot (M-11 dot axis, `--env` /
+     *  `UNOTEST_ENV` of the launcher). Blank/unset = base. */
+    activeEnv?: string;
     /** Port to bind. `0` = OS picks a free port. Default 0. */
     port?: number;
     /** Host to bind. Default 'localhost' (loopback only). */