coatcheck 0.2.1

Contracts and a Playwright accessibility runner for Topcoat component workbenches.
Documentation
# Host contracts

Coatcheck 0.2 adds owned, Serde-compatible wire types without changing the
static 0.1 catalog API.

## Manifest v1

The host serves `ManifestV1` as JSON at the `host.manifest` path from
`Coatcheck.toml` (default: `/__coatcheck/manifest.json`).

Required coordination points:

- `manifest.version` is `1`.
- `manifest.frame.version` is `1`.
- story and scene IDs are stable and unique.
- an empty `story.scenes` means every manifest scene.
- unknown JSON fields are accepted for additive metadata.
- the runner rejects unknown contract versions.

Hosts can build the owned form with
`ManifestV1::from_catalog(catalog, FrameContractV1::default())`, then customize
scenes before serialization.

## Frame v1

The default frame URL is:

```text
/__coatcheck/frame?story=<story-id>&scene=<scene-id>
```

The manifest carries the path, query names, and selectors, so a host may use
different values without changing the runner.

The default DOM markers are:

```html
<main data-coatcheck-frame>
  <!-- isolated production component -->
  <span data-coatcheck-ready hidden></span>
</main>
```

If rendering fails, the host adds an element matching
`[data-coatcheck-error]`. The ready marker means the component has settled
enough for semantic inspection; it does not promise that every animation has
ended.

Coatcheck URLs story and scene query values before navigation. A host must
treat both values as untrusted input and return a visible error marker or a
non-success response for unknown IDs.