autoship

# Autoship ## Contract | Field | Bound contract | |---|---| | Trigger | release this, publish this package, autoship, cut a release, npm release flow | | Authority | Remote: pushes commits, merges the Version Packages PR, and publishes to npm; requires explicit human invocation. Invoking autoship is standing consent for the full release flow; gate risky steps on objective preconditions instead of pausing mid-flow. Force-push, history rewrites, and destructive git operations require explicit confirmation. | | Side effect | Writes a changeset file, runs quality-gate fixers, commits and pushes, merges the bot-opened Version Packages PR, and publishes to npm. Restricted to VCS-tracked targets and the npm registry. | | Done | New version is published on npm and confirmed by `npm view <package> version` matching the merged `package.json`. | ## Inputs - A changesets-based npm package with a release workflow in `.github/workflows/` using `changesets/action`. - Optional bump level: defaults to `patch`; `minor` or `major` only on explicit user instruction. - No new changeset is required if one already exists on the default branch and the intent is to watch or merge only. ## Procedure The release workflow runs twice. First, push a commit carrying a pending `.changeset/*.md` file. The workflow runs `changeset version` in CI and opens a "Version Packages" PR on branch `changeset-release/main`. Merge that PR; the workflow runs again and, with no pending changesets left, runs `changes...