@design.estate/wcctools 6.1.0 → 7.0.0

package/changelog.md

@@ -1,5 +1,46 @@
 # Changelog
 
+## 2026-10-06 - 7.0.0
+
+### Breaking Changes
+
+- `wcctools dev` listens on `127.0.0.1` by default instead of every interface. `--host <address>` (`0.0.0.0` or `::` for every interface) exposes it; `WccDevServer` takes the same as its `host` option.
+- The dev server answers only the hosts it serves: `localhost`, `127.0.0.1`, `::1`, the listen address (with a wildcard listen address, every address of the machine's interfaces) and the names given with `--allowed-host` (repeatable; option `allowedHosts`). Requests and WebSocket upgrades for any other `Host` are refused with `403` and a message naming the `--allowed-host` to add.
+- Typed requests and every other request but `GET`, `HEAD` and `OPTIONS`, and WebSocket connections (shell and preview), are admitted only from the server's own origin (`http://<allowed host>:<port>`); a request without an `Origin` header only from a loopback connection.
+- The preview surface no longer sends CORS headers (`Access-Control-Allow-Origin: *`): other origins can no longer read the catalogue bundle.
+- Because of that origin rule, the shell no longer works through a TLS-terminating reverse proxy, even for an `--allowed-host` name: its typed requests and WebSocket connections carry an `https:` origin and are refused. Reach the dev server over plain HTTP on its own port (for example through an SSH tunnel).
+
+### Features
+
+- `wcctools screenshot <item | section/item> --out <file.png|.jpg>` screenshots one demo in a headless Chrome: it bundles the catalogue, serves it on a free loopback port, renders the demo alone on the preview route at a named width (`phone` 400, `phablet` 600, `tablet` 1024, `desktop` 1600, from the dees-domtools breakpoints) or a width in pixels, a height, a theme and a scale, frames the rendered element, the viewport or the whole page, writes the image and stops. It waits only on the preview's own signals (the bridge, the render's completed updates, the fonts), never for a fixed time. `--demo` counts from 0.
+- The dev server's typed API takes captures: `captureScreenshot` (`IReq_CaptureScreenshot`) and `captureInteraction` (`IReq_CaptureInteraction`), which runs scripted steps (`click`, `hover`, `fill`, `press`, `waitFor`, `wait`; selectors pierce open shadow roots) on a rendered demo while recording its screencast and answers per-step results and at most `maxFrames` timestamped JPEG frames, optionally a final screenshot. One headless browser per dev server starts with the first capture, closes after a minute without one and closes with the server; two captures run at once, eight wait, more are refused as busy; every capture has a deadline (30 s for a screenshot, 135 s for an interaction; fire interactions with a matching `timeoutMs`, since `TypedRequest.fire()` gives up after 60 s by default), ends when its client goes away, waits while a bundle builds and is refused while one failed. A capture stays on the preview route: navigations that would replace the preview document (links, form submissions, `location` assignments, reloads, `about:blank` and `blob:` URLs) are cancelled as they start, with request interception as a backstop, and the step that started one fails with `navigation to <url> blocked`. Not covered: `javascript:` URLs that evaluate to a string, and demos that route by `intercept()`-ing cross-document navigations (see Known Limitations). The browser leaves process signals to the application, so `Ctrl+C` stops the server and closes the browser once.
+- The shell samples timestamped JPEG frames from a recording (`sampleVideoFrames` with mediabunny: count, range, maximum width, quality), and its recording panel hands out the finished recording with its trim range (`getRecording()`), for the coming assistant.
+- `@design.estate/wcctools/interfaces` exports the capture contracts (`IWccScreenshotRequest`, `IWccInteractionRequest`, `TWccInteractionStep`, `IWccImage`, `IWccTimedFrame`, …).
+
+### Maintenance
+
+- New dependency `@push.rocks/smartbrowser` ^5.1.0 (Puppeteer through its `/automation` entry).
+
+## 2026-10-06 - 6.2.0
+
+### Features
+
+- The dev server serves the project directory it is given (`cwd`) instead of reading the process's working directory: tswatch resolves the configuration, bundles, watchers and serve directory against it. `wcctools dev` passes its working directory.
+- The shell shows the catalog's bundle status: a failed bundle shows `bundle failed` with the bundler's message over the preview instead of an endlessly loading preview, and clears when the next run of that bundle finishes. The status (per bundle `started`/`finished`/`failed`, duration, error message) is the typed request `getBundleStatus` (`IReq_GetBundleStatus` in `@design.estate/wcctools/interfaces`), answered when the status changes; a request whose client goes away ends its wait at once, and a server that is stopping refuses the request with a typed error, so the shell backs off instead of asking again at once.
+
+### Fixes
+
+- `wcctools dev` installs the process lifecycle itself (smartexit's `ProcessLifecycle`, with tswatch's shutdown deadline), so `SIGINT` and `SIGTERM` stop the server and the watchers once.
+- The dev server registers its shutdown cleanup when it starts and releases it, its bundle-event subscription and everything tswatch registered when it stops: a constructed server registers nothing, a server started again after `stop()` is stopped by a process shutdown again, concurrent `stop()` calls share one stop, and `start()` is refused while the server runs or stops.
+- A shell context menu removed before its listener frame ran no longer leaves its `click`, `contextmenu` and `keydown` listeners on the document.
+- The package entry `dist_ts/index.js` exports only `runCli`; the dev server and API classes were not reachable through any package export.
+- The published package includes `ts_interfaces`, `ts_shared` and `ts_shell`, the sources the shipped source maps point at.
+
+### Maintenance
+
+- `@git.zone/tswatch` ^7.0.0: the dev server runs tswatch with an explicit project directory, falls back to the `element` preset explicitly when the configuration has no tswatch block, and no longer relies on tswatch for process signal handling.
+- The lockfile takes `@push.rocks/smartspawn` 3.0.5, whose lazy `threads` loading leaves `SIGINT`/`SIGTERM` to the CLI.
+
 ## 2026-10-06 - 6.1.0
 
 ### Features