Published to npm on the `latest` channel, so the install command is
`npx rigorrun`. Early Access describes how finished it is; `latest`
describes which channel it installs from, and those are different
claims.

The tarball published from this commit:
  shasum    ccdc8a49a9b28154f97e0a6941dc0f25f0c1e8dc
  integrity sha512-MhR5cycSOerBtUOa5fu5QvGLcWrmuJerzkO6yE9qZ7DNUuhr6Ad5amCk5R39h+GAXWKOPei+5XFekyyTDIAV6w==

Verified after publishing, against the registry artifact rather than a
local build: a clean machine with an empty HOME and an empty npm cache
runs `npx rigorrun`, connects an MCP system nobody here wrote, learns
its rule from one demonstration, runs an external agent, and returns a
verdict — then catches the regression when that agent changes.