Ship the deploy-kit command in the published package #229

Parent

#195

What to build

Ship the deploy-kit command in the published package, so npx --no-install deploy-kit works in a workflow, which is how both worked workflows (spec/v1/examples/workflows/compose.yml and project-publish-fragment.yml) already call it.

Today the package's files lists only docs/adr/ and spec/. The CLI (src/cli/index.ts) runs from a clone only, because Node does not strip types in files under node_modules. Shipping the command needs either a build step for the published package or a change to what it ships. Both touch publishing, so AGENTS.md puts this on the "ask first" list: the maintainer chooses the approach before anyone implements it.

Acceptance criteria

• The maintainer has chosen how the command is built and shipped, and the choice is recorded as an ADR.
• package.json declares a deploy-kit bin, and npm pack contains what it runs.
• A test installs the packed tarball into a scratch directory and runs deploy-kit validate against a worked example.
• The README's "The command" section stops saying the command runs from a clone only.

Blocked by

• Compose the estate: a compose use-case and CLI, pin annotations and fragment versions #197