@unotest/viewer 0.30.0 → 0.32.0

package/CHANGELOG.md

@@ -1,5 +1,136 @@
 # Changelog
 
+## [0.32.0] - 2026-09-05
+
+### Minor Changes
+
+- 442fadf: `npx @unotest/web box …` reads a box's results from a terminal: `box envs` lists the environments a read token may look at, `box runs` their history (`--latest` collapses it to one line per scenario with its failing streak), `box run <id>` explains one run — the failure, the soft steps, the judge's verdicts — `box queue` shows who is waiting, and `box screenshot` saves a frame the run captured.
+
+  `box run --download` fetches the run's `*.unotest.zip` into `.unotest/box/` and unpacks its failure bundle into `.unotest/failures/`, where `list_failures`, `get_failure_*` and `agent_fix` already look — so a run that failed on a box is debugged with the commands a local failure is. `--no-screenshots` asks the box itself to leave the step frames out (`GET /api/runs/:id/export?screenshots=0`), which is what makes the download smaller rather than only the disk.
+
+  Reading needs a personal read token in `UNOTEST_BOX_READ_TOKEN`; the project's `UNOTEST_BOX_TOKEN` still pushes bundles and values and cannot read runs.
+
+  The viewer publishes its archive reader as `@unotest/viewer/snapshot`, so the three places that open a `*.unotest.zip` — its server, its browser bundle and now the CLI — share one implementation and one message for a file that is not an archive.
+
+- 442fadf: `BoxReadClient` reads a box's runs — environments, run history, one run's whole journal, a collection's children, the queue, a run's export zip and its individual artifacts — over the same HTTP routes a browser uses, authenticated with the personal read token in `UNOTEST_BOX_READ_TOKEN`. Every refusal arrives as a typed `BoxReadError` whose `kind` says what to do next, so throttling is never mistaken for a rejected token and a live run's export says "wait" rather than looking like a broken box. Configuration mistakes surface when a read is attempted rather than at startup, so a stale token in a project's `.env` cannot stop a local run that never touches a box.
+
+  The viewer gains a `@unotest/viewer/wire` entry point exporting its HTTP contract types (the runs page, a run's full snapshot, the queue payload and the snapshot manifest), so a client can name the shapes it parses instead of keeping a second copy of them.
+
+### Patch Changes
+
+- 8aa0f30: Protocol contract for reading a box's run results with a personal read token: `UNOTEST_BOX_READ_TOKEN` (distinct from the project's `UNOTEST_BOX_TOKEN`, which stays a write credential for bundles and environment values), the `X-Unotest-Environment: <project>/<environment>` header every bearer request names its own environment with, the `/_guard/api/envs` listing and its `BoxReadEnvironment` entry, and typed refusals (`unauthorized`, `forbidden`, `unknown-environment`, `not-found`, `rate-limited`, `run-in-progress`, `unavailable`, `malformed`) with parsers that reject anything that is not a box answering. Throttling gets a code of its own rather than an `unauthorized` carrying `Retry-After`: a rejected token means mint a new one, a throttled one means wait and resend the same one. The viewer's `ViewerEnvOption` is now that same protocol type rather than a second copy of it. An environment whose viewer is still starting — the common state right after a bundle push — answers `unavailable` rather than looking like an unreachable box, so the advice is to wait rather than to check the address.
+- 8aa0f30: A run exported as `*.unotest.zip` now carries everything needed to diagnose it away from the machine that produced it: `stdout.log` and `stderr.log` (previously dropped, which left the one artifact that explains a runner crash outside the bundle), the failing page's `page.html` reachable through the manifest, and the run's step screenshots — declared in a new `manifest.screenshots` list, because an importer keeps only what the manifest names and a frame absent from it did not survive the round trip.
+- Updated dependencies [8aa0f30]
+- Updated dependencies [047ca68]
+- Updated dependencies [047ca68]
+- Updated dependencies [047ca68]
+  - @unotest/protocol@0.32.0
+  - @unotest/dsl@0.32.0
+  - @unotest/core@0.32.0
+
+## [0.31.0] - 2026-09-04
+
+### Minor Changes
+
+- b8e105b: Steps tree shows what a step attached to itself: a row that called
+  `note(...)`, `log(...)` or `assertJudge(...)` gets an `ⓘ N` chip, and the
+  list under it renders notes as `label → value`, log lines, and the
+  verdict as `judge ✓/✗ · rubric · text` — open by default under a failed
+  step and under a verdict that said no, with open/closed choices
+  remembered per scenario and step. A note from inside a helper lands
+  under the entry step that called it (the runner records the entry
+  position; older journals fall back to the step in flight). The error
+  card of a failed judge step carries the whole verdict. After the run the
+  System pane lists the scenario's `log(...)` lines with their time. The
+  server keeps `note` / `log` lines when it reads a finished run's journal.
+- 100ab9d: Steps view reads the `step-block:*` envelopes of a run: a block's duration
+  is now the whole block (a step wrapping a loop of three navigations shows
+  the loop's 4.8s, not the last statement's 66ms), a `{tag}` step shows its
+  evaluated tag as a chip (the source expression before the run), a
+  `step.soft` block is marked `soft`, and a group with soft descendants
+  rolls them up as "1 of 10 soft failed" and reads as failed. A run with
+  soft failures gets a card above the tree listing every one with its tag,
+  line and error. Journals recorded before 0.31.0 render as before. The
+  server keeps `step-block:*` and `judge:verdict` lines when it reads a
+  finished run's journal from disk (it used to drop every kind it did not
+  list, so a verdict never reached the page); the error card under a
+  failed step shows that step's own error, not the run's last one; the
+  status bar counts soft steps ("2 of 3 soft failed").
+- ad7c918: Trace view — the execution tree of a run, next to Steps and Code. Built
+  from the journal alone: a helper call opens into the helper's statements
+  and `step(...)` blocks (file named on the row), a loop into one group per
+  iteration (an iteration that ran nothing included), a block into its
+  envelope with tag and duration. Helper calls and passed iterations start
+  folded with a summary ("10 iterations · 1 failed"); the failed branch is
+  open down to the failing statement, which carries the error card.
+  Double-click opens the row's file — a helper too — at that line in Code.
+  Notes, log lines and verdicts sit under their statement; screenshots
+  open from the row, helper-frame captures included. The chosen view is
+  remembered across reloads (a debug session always opens in Code). The
+  inspector's flat event list is now the **Events** tab, so Trace names
+  one thing. The server keeps `loop:iteration` lines when it reads a
+  finished run's journal.
+
+### Patch Changes
+
+- e048334: The viewer's editor flags an undeclared external variable
+  (`lint:external-variable-undeclared`), the way `unotest-web lint` and the
+  pre-run lint already do: a bare `UPPER_SNAKE` identifier that no
+  `unotest/.env` / `.secrets` file of the active environment declares is an
+  error in the editor, naming the files searched. Protocol:
+  `DslValidateContext` gains `externalNames` / `externalSources`; the
+  viewer supplies them from the active target + environment's layer files
+  (the same files the variables panel shows) and `@unotest/web`'s language
+  service turns them into the linter's lookup.
+- dcf4c9e: Viewer editor: lint markers appear as soon as a file opens (or the page
+  reloads), not only after the first keystroke — the editor validates the
+  source it mounted with instead of waiting for a change event that a
+  reopened tab never fires.
+- 9ae6d59: A scenario that finished in the same instant the viewer looked at it is no
+  longer recorded as `interrupted` with a finish an hour before its start.
+  The runner ends a run by appending `run:finished` and then backdating the
+  heartbeat; the viewer read those two files in the opposite order, so a
+  steps snapshot taken a few milliseconds early could meet the backdated
+  heartbeat, and the provisional verdict stuck in the run index while the
+  collection reported the scenario passed. The heartbeat is read first now.
+  A viewer restart (which rebuilds the index from disk) already corrected
+  such records; runs indexed live are right the first time.
+- 13a2d51: Viewer, Home tab: the tile of a scenario that is running now breathes
+  through colour and shadow only — the scale pulse is gone. It moved the
+  tile's box every frame, so an automation driver never saw the tile as
+  stable and a click on it waited out its timeout. A tile that never ran
+  no longer carries `data-age="fresh"`: it has no age, so the attribute is
+  absent.
+- 91fb562: Viewer, Home tab: clicking a scenario tile opens the scenario's LAST RUN —
+  the run whose verdict the tile's colour is showing — instead of the test
+  file. A tile that has never run still opens the test (there is no run to
+  open), and so does every tile in schedule mode, where the schedule is
+  edited from the test. The legend now reads "hover for history · click to
+  open the last run".
+- dcf4c9e: Viewer, Home tab: the tile field no longer refits itself in a loop. The
+  header and legend take the grid's width; when the legend wrapped at one
+  width and not at the next, the field's height changed, the fit followed,
+  the width changed back — at 60 fps every tile's box moved every frame,
+  and an automation click on ANY tile ("element is not stable") waited out
+  its timeout unless forced. Header and legend now never wrap (they grow
+  past the grid instead), so the fit converges and tiles stay put. A run
+  opened from a tile is titled by its scenario, like one opened from the
+  Runs tree, instead of by its run id.
+- Updated dependencies [b8e105b]
+- Updated dependencies [b8e105b]
+- Updated dependencies [9ae6d59]
+- Updated dependencies [56784b3]
+- Updated dependencies [e048334]
+- Updated dependencies [100ab9d]
+- Updated dependencies [100ab9d]
+- Updated dependencies [100ab9d]
+- Updated dependencies [ad7c918]
+- Updated dependencies [ad7c918]
+- Updated dependencies [dcf4c9e]
+  - @unotest/core@0.31.0
+  - @unotest/protocol@0.31.0
+  - @unotest/dsl@0.31.0
+
 ## [0.30.0] - 2026-09-03
 
 ### Minor Changes