@unotest/viewer 0.26.1 → 0.28.0

package/CHANGELOG.md

@@ -1,5 +1,80 @@
 # Changelog
 
+## [0.28.0] - 2026-09-01
+
+### Patch Changes
+
+- @unotest/core@0.28.0
+- @unotest/dsl@0.28.0
+- @unotest/protocol@0.28.0
+
+## [0.27.0] - 2026-08-31
+
+### Minor Changes
+
+- The server boots quietly: Nest's per-module / per-route boot log is
+  gone from normal runs — the launcher's one useful line is the URL.
+  `UNOTEST_DEBUG` brings the full boot map back.
+
+- The LOCAL schedule registry now shows the EFFECTIVE merged set too:
+  both store flavours read through one `EffectiveSchedulesReader`
+  (`schedules --json` across a process boundary), so config-declared
+  entries appear locally, stamped `source: "config"` and opened as a
+  read-only card ("declared in `unotest.config` — edit it there");
+  yaml entries stay editable. A PUT carries only the file half and
+  answers with the re-merged whole (`SchedulesView` for both verbs);
+  the envelope gains `driftedFromPush` — on a box, true when the set
+  read there hashes differently from the fingerprint recorded at push,
+  shown as a warning line in Home schedule mode. The local schedule
+  mode gets its own caption: "declared here — a box runs what you
+  push". Runners without a schedules command fall back to the yaml
+  half, unchanged.
+
+- The schedule registry on a deployed tree (a box environment) is now
+  the EFFECTIVE merged set, read-only. `GET /api/schedules` returns
+  `{ schedules, readOnly }`; on a box the entries come from the
+  project's own CLI (`schedules --json` via the runner adapter's new
+  `schedulesArgs()`), so config-declared schedules are no longer
+  invisible in the UI. The Schedule popup becomes a read-only card with
+  a provenance note ("declared in the repo — edit there and push"), the
+  Home schedule mode shows a matching badge, and `PUT /api/schedules`
+  is refused with 403: on a box that write used to land in a disposable
+  bundle copy nothing ever re-read. Local viewers are unchanged —
+  editing the file is still the workflow there.
+
+- c843d21: Schedules from the viewer — for collections and single tests.
+
+  Right-click a test or a collection in the viewer → **Schedule…**: a
+  human schedule builder (frequency select — every 5/15 min, hourly,
+  every 2/4/6/12 h, daily, weekly — plus toggle badges for minutes,
+  hours and weekdays; multi-select, so `04` + `16` × `00` + `30` runs
+  four times a day). Saved to `unotest/schedules.yaml`, versioned next
+  to the tests; a box applies it after commit & sync. The Home screen
+  gains a `last run | schedule` toggle: in schedule mode tiles are
+  tinted by how often a test runs (grey = not scheduled), with an
+  upcoming list and per-tile next-run times in your browser's clock.
+
+  Under the hood:
+
+  - `unotest/schedules.yaml` is a new schedule registry; `unotest-web
+schedules [--json]` prints it merged with the config's `schedules`
+    (the file wins on a duplicate target), so boxes pick both up
+    unchanged.
+  - A schedule entry may now target a single test: `scenario:
+<ref>` instead of `collection: <name>`.
+  - `unotest-web e2e <name> --scheduled[=index]` runs a test the way its
+    entry says (env + prepare, exit 94 when prepare fails) — the
+    per-test mirror of `collection --scheduled`.
+  - Viewer server: `GET/PUT /api/schedules` (validated by the same
+    parser the CLI reads the file with).
+
+### Patch Changes
+
+- Updated dependencies [c843d21]
+  - @unotest/protocol@0.27.0
+  - @unotest/core@0.27.0
+  - @unotest/dsl@0.27.0
+
 ## [0.26.1] - 2026-08-30
 
 ### Patch Changes