chore: align package.json version with 2.1.1 and 2.2.0 releases

[gretzke]

Summary

package.json currently reports 2.1.0, including at the source revisions used for the 2.1.1 and 2.2.0 deployment releases. Align the package metadata and publishing workflow with the release versions.

Context

The Git tags identify the exact source revisions pinned by the deployments:

• 2.1.1 -> 999d561c3ad58fb5cab91b602911f3c75591a9c7
• 2.2.0 -> 020e1b786ad9a6bad924874752167934734ad1e1

Both revisions contain "version": "2.1.0" in package.json. This is harmless for GitHub-only releases but can publish incorrect npm metadata if the tags drive the package release workflow.

Proposed work

• Update the current package.json version to 2.2.0.
• Decide how the historical 2.1.1 package version should be represented without losing exact deployed-source provenance.
• Ensure the npm publishing workflow validates that the package version matches the intended release tag.
• Keep the lockfile/package metadata consistent if regeneration is required.

Acceptance criteria

• The package metadata for future 2.2.x publishing reports the correct version.
• The 2.1.1 release/package strategy is documented or implemented.
• CI fails clearly when a release tag and package.json version disagree.