@unotest/protocol 0.18.0 → 0.20.0

package/CHANGELOG.md

@@ -1,5 +1,88 @@
 # 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.
+
+## [0.19.0] - 2026-08-23
+
+### Minor Changes
+
+- dfb3991: Per-collection parallelism via a `workers:` field in the collection YAML.
+
+  - `workers: N` (integer ≥ 1) in `unotest/e2e/_collections/*.yaml` sets how
+    many scenarios of that collection run concurrently; omitted = serial.
+  - Precedence: CLI `--workers=N` flag > manifest `workers:` > 1.
+  - Viewer: the collection header shows an editable `workers` value; the
+    setting is stored in the YAML, so CLI and CI runs pick it up too.
+  - `CollectionMeta` (protocol) gains a `workers: number | null` field.
+
+- Run history scales: runs are filed under daily shards and the viewer stops
+  polling history it is not showing.
+
+  - New on-disk layout `unotest/.runs/<YYYY>/<MM>/<DD>/<runId>/` (UTC date the
+    run started). The shard is a pure function of the `runId`, which already
+    carries the timestamp — a direct link to a run keeps working even with the
+    index deleted. Existing flat `.runs/<runId>/` history is migrated
+    automatically (see the `runs migrate` entry).
+  - The viewer's watcher polls only LIVE runs; finished history never touches
+    it. Discovery watches the current day's directory with native `fs.watch`
+    and re-attaches at UTC midnight.
+  - A JSONL index per day and per scenario backs the history list. It is fully
+    rebuildable — rebuilt on start, non-blocking — so a corrupted or missing
+    index degrades the listing, never the runs themselves.
+  - `@unotest/protocol`: new `run-shard` and `run-index` modules (shard path
+    derivation, index record shapes) exported from the root entry.
+
+- Step screenshots are stored once and shared, and old runs expire on their
+  own — a long history stops growing without bound.
+
+  - Identical frames are content-addressed in `unotest/.runs/_blobs/` and
+    hardlinked into each run. `du` and ordinary copies see whole files;
+    `cp -a` / `rsync -H` preserve the sharing. On one dogfood suite: 45
+    frames, 2.04 MB by apparent size, 0.96 MB on disk.
+  - Reference counting is the filesystem's (`st_nlink`), so nothing to keep in
+    sync. Blob generations keep the dedup honest past ext4's 65 000-link
+    ceiling, and a fresh blob is untouchable for an hour so the window between
+    writing it and linking it is never mistaken for garbage.
+  - Retention: `UNOTEST_RUNS_RETENTION_DAYS` (whole days, default 180) sweeps
+    runs older than the window at the end of a collection run. It never
+    changes the exit code — a failed sweep is reported, not fatal.
+  - `@unotest/protocol`: new `run-blobs` module exported from the root entry.
+
+- `ScenarioLatestEntry` (`GET /api/runs/latest`) gains `lastDurationMs` and
+  `recent` — a window of the last 12 outcomes, oldest first. Both are folded by
+  the same `foldScenarioRun` the live path and `rebuild()` already share, so
+  the index stays fully derived from the run manifests. Feeds the viewer's
+  overview dashboard without a request per scenario.
+
+  `RUN_INDEX_SCHEMA_VERSION` → 2: an index file from the previous version is
+  discarded and rebuilt on start, as before. Nothing to do on upgrade.
+
 ## [0.18.0] - 2026-08-23
 
 ### Minor Changes