A handoff fails quietly. The contract is there, the tokens are there, and the one thing nobody checked — the focus-visible screenshot, the anatomy note the usage doc links to, the token the component cites by a name that was renamed last month — is missing. The person who opens the package finds out, on a different machine, a week later.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+.
Run the checked-in example
node bin/design-handoff-packager.mjs --root examples/clean --jsonRead the result
A consumer that pipes stdout must handle an empty stdout on exit 2. A configuration error means the run never had a subject, so there is nothing to report about; evidence that could not be obtained means the run had a subject and failed to learn something about it, and the report says which input that was.
Scope
Every limit is enforced, overridable with --limit NAME=VALUE, and named in the finding when it is reached. Exceeding one is an incomplete result — never a quietly smaller package, and never a pass. An unknown limit name is an error.