The CLI the site is now allowed to mention
orchestkit@0.1.0 is live on npm with both binaries intact. The docs
claim it only now, because until the publish landed the claim would have been false.
Pick a command to see its real output.
Why the claim waited
The first publish attempt printed bin[orchestkit] ... was invalid and
removed. npm 11 deletes any bin value starting with
./, so the package would have installed cleanly and had no commands,
with npm publish exiting 0. Had the docs been updated on
the same schedule as the code, the site would have advertised
npx orchestkit against a package where that command did not exist.
| Claim | Verified by | Result |
|---|---|---|
| bin survives publish | registry manifest, not local pack | both present |
| npx orchestkit runs | clean install from registry | 0.1.0 |
| npx ork runs | same install, alias bin | emits config |
| zero dependencies | registry manifest | {} |
The guard
docs/site/__tests__/published-packages.test.ts ties the site's claim to
packages/cli/package.json: the linked npm name must match, and every
npx <name> the site advertises must correspond to a bin the package
actually declares. Renaming a bin without updating the docs now fails the suite
instead of shipping a command that does not exist.