Changelog

0.10.0 — Qualified responsibility coverage

Contract authoring now requires demonstrated need, reuse of native verification and review of solution restraint. The workflow explicitly leaves necessity and restraint unresolved by executable checks; passing tests do not approve unnecessary machinery or premature abstraction.

Clarified requirement-to-entrypoint coverage, actual configured policy probes, normal precedence, current compiled-code evidence and distinct distributed compatibility boundaries. The workflow skill now challenges owner-using local overrides. The native shared-button example adds correct-looking surface overrides and theme-sharing component copies on both screens. Separate theme and component-rule probes retain configuration references, while actual qualification fixture bytes participate in review. Compact review format 2 stores a shared contract digest and rationale once; the native example and toolkit share one record. Research archives and study harnesses are kept outside the product repository. Installed-package verification exercises the expanded matrix. Existing valid wrappers and component behavior remain supported.

0.9.0 — Cross-repository adoption

Added an evidence-first distributed adoption guide and skill routing for external owners, legacy/current/candidate boundaries, provider exports, consumer compatibility, two-way delivery and third-party adapters. The new read-only inspect-system operation identifies missing owners, contract artifacts/pins, dependencies and check references. Its result explicitly does not evaluate conformance, authenticate provenance or establish deployments. A portable example and regression tests are included.

0.8.0 — Shared UI contracts

Rebuilt the public examples around a real Settings/Team app, a shared button and design tokens. Browser checks observe appearance, loading, disabled behavior, keyboard access and theme propagation; eight production variants test legitimate wrappers, correct copies and unused-owner decoys. Native and toolkit gates enforce two-way review obligations. The CLI quickstart now uses relative-time wording. Public evidence reports the complete UI subset of the prior full-application study with plain-language counts, while original unrelated fixtures and results remain unchanged in the private archive. No historical result is relabeled as a button experiment.

0.7.0 — Portable two-way enforcement

Added explicit provider/consumer change bindings, separate reviewed acceptance records, read-only identity inspection, stale-binding verification and strict workflow coverage. The packaged workflow example adopts the strict gate. Native regressions distinguish semantic disagreement from review freshness, including changed contract examples with fresh records. The propagation observer compares actual JSON consumer values before/after a provider substitution, and strict production matrices cover every declared consumer. Production-variant qualification applies reviewed overlays to real source and runs the same checker as delivery, preventing a different fixture-label classifier from qualifying a live check. Agent guidance requires executable examples and current qualification after requirement changes.

0.6.0 — Two-way change contracts and auditable evidence

The specification explicitly requires contract changes to invalidate affected conformance bindings and covered implementation changes to require contract review. The native example now enforces stale bindings alongside its existing qualified checks. Generic CLI reconciliation remains impact information; use an adopted native gate to enforce review completion. A reviewed evidence report links historical comparisons, failed witnesses and source-backed runnable checks without exporting private conversations. Earlier studies did not evaluate the new binding gate.

0.5.3 — MIT licensing

Code and documentation now use the MIT license. Package and distribution metadata identify MIT, and the versioned preview archives include the full license notice. Repository access remains private; npm and plugin-directory publication remain disabled.

0.5.2 — Adopter preview preparation

• Added deterministic guidance and source archives with file integrity manifests and local marketplace catalogs.
• Added a Codex compatibility manifest while keeping portable and Claude plugin metadata derived from the package release.
• Added distribution regression tests and excluded private research/history from the source export.
• Included the catalog examples needed by the exported CLI/MCP tests.
• Added example dependency locks, offline recipe links, preview installation/update/removal instructions and support guidance.
• Clarified CSV serialization terminology.

This preview has not been published to a public plugin directory or npm. Read the included license before reuse. The CLI/library contract remains unchanged by these distribution improvements.