wicked-studio 0.4.1 → 0.4.2

package/README.md

@@ -80,6 +80,13 @@ The connection surface is deliberately small (`src/api/client.ts`):
 The daemon's loopback CORS admits any `http://localhost:*` / `http://127.0.0.1:*` origin, so a
 standalone studio on its own port can drive a local daemon out of the box.
 
+## Install
+
+You rarely install studio directly: **`npx wicked-crew serve` ships this UI bundled**,
+same-origin on one port. Or use the family installer — [`npx wicked-installer`](https://www.npmjs.com/package/wicked-installer)
+installs/updates the whole wicked-\* family (wicked-crew, which serves this skin, included).
+For a studio you build and host yourself, see [Standalone build](#standalone-build).
+
 ## Develop
 
 ```sh
@@ -116,6 +123,18 @@ absent). Installs from git get a fresh `dist/` via the `prepare` hook
 (`scripts/prepare-dist.mjs`); publishers run `npm run build && npm publish` so the tarball is
 built from the tagged source.
 
+### The data-testid contract (`testid-inventory.json`)
+
+`testid-inventory.json` (repo root, committed; emitted into `dist/testid-inventory.json` by the
+build) is the machine-readable inventory of every `data-testid` the UI declares — the selector
+contract that test generators and the model-free campaign runner build against, versioned with
+this package. `tests/testidInventory.test.ts` re-scans `src/` and fails CI on any drift, so a
+testid change (or a `package.json` version bump — the artifact carries `studioVersion`) ships
+only together with a reviewed `npm run manifest:testids` regeneration. The drift-handling
+doctrine downstream is embedded in the file's `$doc` header: a selector miss fails the
+deterministic run; the authoring agent re-authors against the live DOM; the runner re-records;
+the substitution lands in the spec diff. No agentic fallback inside the runner.
+
 ## Provenance
 
 Extracted from the wicked-crew monorepo (`packages/studio`) as its own product — the carve kept