@design.estate/wcctools 5.1.0 → 6.1.0

package/.smartconfig.json

@@ -52,10 +52,14 @@
   "@git.zone/tsbundle": {
     "bundles": [
       {
-        "from": "./html/index.ts",
-        "to": "./dist_bundle/bundle.js",
+        "from": "./ts_shell/index.ts",
+        "to": "./dist_shell/bundle.js",
         "outputMode": "bundle",
-        "bundler": "esbuild"
+        "bundler": "esbuild",
+        "production": true,
+        "includeFiles": [
+          "./ts_shell/index.html"
+        ]
       }
     ]
   },

package/changelog.md

@@ -1,5 +1,33 @@
 # Changelog
 
+## 2026-10-06 - 6.1.0
+
+### Features
+
+- [`docs/standard.md`](https://code.foss.global/design.estate/wcctools/src/branch/main/docs/standard.md) drafts the wcctools component standard (rule ids, severities and defaults may still change until it is declared stable): rules for layout, naming, elements, barrels, demos and properties (profile `base`), plus the theme, wording and component-index ratchets of the dees-catalog family (profile `dees`), with an exact allowlist and per-file baselines configured in `.smartconfig.json` under `@design.estate/wcctools` → `standard`.
+- `wcctools check [--json] [--verbose]` checks a catalog against the standard from syntax alone (TypeScript 6 `createSourceFile`, no type checker) and exits 0, 1 for failing error findings, or 2 for a configuration or usage error; `--json` prints one `IStandardReport`. `--init-baseline` records the current error counts as baselines, `--update-baseline` lowers them and refuses to raise any.
+- `wcctools fix [--rule <id>…] [--dry-run] [--json]` fixes findings with span edits that keep formatting and comments: missing exports, tag maps, `accessor` keywords, property `type`/`attribute: false`, demo-file exports, barrels and reachability, `demoGroups` (dees), the readme component index (dees), and file moves with `git mv` (element folders, `<tag>.ts`/`<tag>.demo.ts` names, lowercase names, `00` shared modules) that rewrite relative imports across the repository and move allowlist and baseline keys along. `props/reflect-primitive` and `demo/required` are fixed only when named with `--rule`. It refuses a dirty work tree and any plan with a path outside the repository root (validated before anything is written), never derives paths from a tag that is not a valid custom element name, and never commits.
+- `@design.estate/wcctools/interfaces` exports the standard's configuration and report types (`IStandardConfig`, `IStandardReport`, `IStandardFinding`, `IStandardFixResult`, …).
+
+### Changes
+
+- Usage errors of every `wcctools` command, `wcctools dev` included (an unknown command or option, a missing or invalid option value), now exit with code 2 instead of 1; other failures still exit with 1.
+
+## 2026-10-06 - 6.0.0
+
+### Breaking Changes
+
+- The catalogue UI moves into a prebuilt shell served by the new `wcctools dev` command, and the catalogue bundle runs as the preview document in a same-origin iframe as wide as the selected viewport. Catalogues replace their `watch` script with `wcctools dev`; `html/index.ts` and `html/index.html` stay as they are.
+- `setupWccTools()` sets up the preview document only: inside the shell's frame it installs the preview bridge, on `/wcctools-preview?…` it renders that one demo alone, and anywhere else (for example plain `tswatch`) it shows a notice naming `wcctools dev` instead of the catalogue UI.
+- `RecorderService`, `WccRecordButton` and `WccRecordingPanel` (with `IRecorderEvents`, `IRecordingOptions` and `TOutputFormat`) are no longer exported; recording lives in the shell, and `mediabunny` is no longer installed with the package.
+
+### Features
+
+- `wcctools dev [--port <port>]` bundles and watches the catalogue with tswatch (the project's `@git.zone/tswatch` configuration, or the `element` preset) and serves the shell on `/wcctools/`, its typed API on `/wcctools/typedrequest` and the catalogue from the serve directory on one port; `/` redirects to the shell, `--port 0` picks a free port, and a rebuilt bundle reloads only the preview frame.
+- Width `@media` queries of previewed elements follow the selected viewport, since the preview document is exactly that wide.
+- The properties panel reads and edits the rendered element through the preview bridge, classified in the preview's own realm, and waits for the render to settle instead of polling.
+- New `@design.estate/wcctools/interfaces` export: the catalogue manifest, the preview bridge (`IWccPreviewBridge`, installed as `window.wccPreview`) and the dev server's typed requests.
+
 ## 2026-10-06 - 5.1.0
 
 ### Features

package/cli.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+const cliTool = await import('./dist_ts/index.js');
+cliTool.runCli();