Publish a release candidate from every pull request #34

Parent

#21

What to build

Opening or updating a pull request from a branch of this repository publishes <next patch>-rc.<pull request>.<run> to GitHub Packages under the rc dist-tag, so a consumer can try the change before it is released. Pull requests from forks, Renovate and Dependabot publish nothing. No git tag is created, and a plain install keeps resolving to the latest release. The workflow summary shows the exact version and the install command. Until the compiler lands, the package holds docs/adr and spec.

Acceptance criteria

• A pull request publishes a candidate whose version sorts above the current release and below any version release-please could choose next.
• npm view shows the candidate under the rc dist-tag, with latest unchanged.
• A Dependabot pull request publishes nothing.

Blocked by

• Run the suite on Vitest and make the tooling strict TypeScript #22
• Split CI into one job per gate under Pipeline Complete #23