v0.2.0 — the release pipeline and Node 22+, never on npm

Released on GitHub only. Its publish run stopped before uploading
anything: no package on npm trusted publish.yml yet. Install
0.3.0, which
has the same package code, or 0.1.0.

Before you upgrade: sheetpane now needs Node 22 or later wherever it
runs in Node: SSR imports, tests, the MCP server, the CLIs. Node 20 is past
end of life. Browsers are unaffected.

Release and tooling

• Published from CI only, with provenance. A GitHub Release runs
  publish.yml, which publishes nothing unless CI is green on that commit,
  every version site agrees, and the tag matches the packages. It builds once,
  checks each tarball (no src/, no tests, README and LICENSE present) and
  publishes over npm trusted publishing (OIDC): no token, with signed
  provenance. See RELEASING.md.
• CI on Linux, macOS and Windows × Node 22 and the current LTS. Each run
  installs the built tarballs into an empty folder and imports every package
  from plain Node.
• @sheetpane/mcp on Windows: explain_code returns the full entry
  (cause, meaning, fix) when ERRORS.md has CRLF line endings.
• MIT LICENSE in every package.

The package code is 0.1.0's; its Changed and Added lists are under
0.1.0.