@unotest/viewer 0.19.0 → 0.20.0

package/CHANGELOG.md

@@ -1,5 +1,58 @@
 # Changelog
 
+## [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