usedesign — how the pieces fit Diagram

What is compared with what

Cards vs the route inventory, the JUnit report, the live store and the files their evidence names; contracts vs real components rendered per state
Sources are never parsed — only what the system states about itself; in the package only scaffold reads an OpenAPI document, for drafts and never for verdicts; a route inventory may be made from one outside it

What the box holds

Six commands: validate and check run in the gates, conformance runs the corpus; scaffold drafts cards from an OpenAPI document, gen openapi writes one from the cards, preview draws contracts as a wireframe page
Six schemas: card and contract are read at run time by both checkers; the other four describe the config and the three inventories

Two readings, one corpus

TypeScript reference and Python prototype must report the same codes on 165 cases
A deliberately rotten repository must still fail, and CI compares what both checkers report on it

Where it runs

npx usedesign@<pin> in each product's CI — nothing installed, version frozen per repository; each gate runs validate, then check; the frontend gate reads the server's cards via a sibling checkout
Publish is green only when the registry actually serves the box
The starter kit (Russian) is the copy-and-go path: a sample config and gate, a script for the route inventory, a recipe test for the form inventory