@unotest/viewer 0.10.0 → 0.12.0

package/CHANGELOG.md

@@ -2,6 +2,124 @@
 
 All notable changes to `@unotest/viewer` are documented in this file.
 
+## [0.12.0] - 2026-08-14
+
+### Patch Changes
+
+- 479aa25: Feedback batch from a real-world integration (bot-service): shell()
+  safety, run diagnostics, boolean-attribute probes, linter ergonomics.
+
+  **BREAKING — `shell()` fails the step on a non-zero exit code.**
+  Previously a non-zero exit resolved silently and a forgotten `res.code`
+  check produced false-green tests. Migration: calls where non-zero is
+  expected (probes, `grep -q`) pass `{allowNonZero: true}` as the last
+  argument and keep checking `res.code`; calls that asserted
+  `assertTrue(out.code == 0, ...)` can drop the assert. More shell()
+  hardening: a missing binary is a distinct "failed to start" error (was a
+  fake `code: 1`), output over 10 MiB fails loudly (was silent
+  truncation), and every call has a wall-clock budget
+  (`sandbox.shellTimeoutMs`, default 120 s, or per-call `{timeoutMs}`) —
+  a detached grandchild holding the stdio pipes no longer hangs the
+  scenario forever; the timeout error explains the detach recipe.
+
+  New capabilities:
+
+  - `waitForFile(path, pattern?, {timeoutMs})` — poll a file until it
+    exists / contains a substring or regex; the file-side `waitForText`
+    for background processes. Returns the content.
+  - `sandbox.exportSecrets: [names]` — explicit allowlist of `.secrets*`
+    variables exported into `shell()` subprocess env (still masked in
+    logs). Secrets stay out of `process.env` otherwise.
+  - `isDisabled(loc)` / `isEnabled(loc)` — honest disabled probe (native
+    `:disabled` incl. fieldset inheritance, or `aria-disabled`);
+    `hasAttribute(loc, name)` — presence probe for boolean attributes
+    (`getAttribute` reads `""` for present and absent alike).
+  - Generators: `randomWord(len)` (letters only — digit-free markers),
+    `nowMs()`, `today()`, `daysFromNow(n)` (previously documented in the
+    skills but not implemented).
+  - Failed runs report the enclosing step: `✗ test: … in step "…"` in the
+    console, `stepLabel` in the failure bundle and `inspect_runtime`.
+  - Every CLI run prints a one-line header: active environment, layer
+    files (missing ones flagged) and effective `baseUrl`; `run_test` /
+    `explore_start` replies echo `baseUrl` next to `environment`.
+  - `run_test` accepts per-call `env` — the spawned runner child gets
+    `UNOTEST_ENV=<env>` for that run only.
+  - Linter: `// lint-ok: <reason>` silences warning/info diagnostics on
+    its line (reason required; errors never suppressible); new
+    `lint:echo-assert` warns when `waitForText`/`assertText` overlaps a
+    value the scenario itself filled (chat echo trap);
+    `lint:goto-concat` / `lint:regex-invalid` are now configurable in
+    `linter.rules` (they were emitted but missing from the config schema).
+  - A `_helpers` file that fails to parse is reported as the root cause in
+    `unotest-web lint` (and explore replies list `unparsableHelperFiles`)
+    instead of silently cascading into "Unknown function" at every call
+    site. The viewer logs the same condition (patch).
+
+- 5dd59af: The Steps tree renders on the editor (canvas) background, matching the
+  Code mode next to it — previously it sat on the panel chrome color. The
+  snapshot tab's read-only source view gets the same canvas background.
+- 7069d24: Panels no longer blend together: the shell adopts a JetBrains-new-UI
+  "islands" layout. The sidebar tree, the main content area, the terminal
+  tool window and the run-view inspector dock are rounded cards floating
+  on a darker shell background; the gap channels between them are the
+  separators (with rounded corners at every seam), replacing the old
+  flat 1px borders. Works in both light and dark themes via a new
+  `shell` design token.
+- Updated dependencies [40300d3]
+  - @unotest/dsl@0.12.0
+  - @unotest/protocol@0.12.0
+
+## [0.11.0] - 2026-08-13
+
+### Minor Changes
+
+- a195713: Failure artifacts are always on, and steps can carry screenshots.
+
+  - On any scenario failure the runner writes `screenshot.png` +
+    `page.html` (runtime DOM, open shadow roots included, secrets
+    redacted) to `unotest/.runs/<runId>/failure/` — no `UNOTEST_DEBUG`
+    needed. The `.unotest/failures/` bundle gains the same `page.html`;
+    its screenshot keeps honouring `failureBundle.tier2`.
+  - New env flag `UNOTEST_STEP_SCREENSHOTS=1` captures a PNG after every
+    executed step into `unotest/.runs/<runId>/screenshot/`.
+  - Protocol: `screenshot` events may carry the step's `file`/`line`/`col`.
+  - Viewer: a step row with a captured screenshot shows a camera icon and
+    toggles an inline preview on click (both `screenshot()` DSL captures
+    and per-step ones).
+
+- c01b72f: Step screenshots open full-screen instead of expanding inside the steps
+  tree. Clicking a row with a capture opens a viewer over the whole
+  window — dimmed, blurred backdrop, the frame scaled to fit — with
+  arrows on both sides (and `←`/`→`) walking every capture the run
+  produced, disabled at each end. Under the image sits the frame's
+  identity: the enclosing `step("…")` label and the statement itself with
+  its line number, plus a position counter. `Esc` or a click outside
+  closes; the row you were last looking at stays marked in the tree and
+  scrolled into view, so closing the viewer lands you where you left off.
+
+  The inline preview under the row is gone — it made the tree jump on
+  every capture and showed the screenshot at a size nothing could be read
+  at.
+
+### Patch Changes
+
+- dea90e9: Straightens the scenarios tree indentation. A folder's children were
+  indented by less than the chevron column they nest under, so a
+  scenario's status dot landed to the LEFT of its parent folder's name and
+  sibling folders and scenarios sat on two different grids. One level now
+  costs exactly one chevron column: a nested folder's chevron sits under
+  its parent's folder icon, and a scenario's dot sits where its parent's
+  name starts — the alignment every file tree uses. Scenario rows reserve
+  the chevron column they don't have, and their dot occupies the same
+  box as a folder icon, so names line up across both row kinds.
+- Updated dependencies [a195713]
+- Updated dependencies [ce25926]
+- Updated dependencies [5a8e92b]
+- Updated dependencies [d0ae620]
+- Updated dependencies [2a68997]
+  - @unotest/protocol@0.11.0
+  - @unotest/dsl@0.11.0
+
 ## [0.10.0] - 2026-08-06
 
 ### Patch Changes