# Verification

Release verification has four layers:

1. Unit tests cover template validation, deterministic A2UI compilation, replay reconstruction, required fields, session binding, action allowlisting, typed data, and exactly-once settlement.
2. Type checking and two production bundles verify the host and React 18 client halves.
3. `npm pack --dry-run` audits the public artifact.
4. A clean DeepSeek Harness profile installs the packed tarball, boots the web app, inventories the plugin, and exercises a real Tool call through the browser.

Mechanism tests prove the plugin boundary. They do not prove that every model will choose the right template or that an arbitrary third-party A2UI renderer supports this plugin's bounded Basic Catalog subset.

## Compatibility evidence

- Harness `0.1.0-rc.5` source checkout: exact v0.1.1 tarball installation, web boot, form rendering, required-field validation, pending-card recovery after reload, structured submission, model continuation, and 390 px responsive layout.
- Earlier Harness `0.1.1-rc.2` package contracts: unit, type, build, package, clean-profile, and browser verification from the v0.1.0 release.

The rc.5 test uses the deterministic replay adapter. It proves the Harness integration and interaction lifecycle, not live-provider model quality.