chore(release): 0.2.2

[drewstone]

Why

main carries the canonical-digest fix from #32 — the view layer no longer calls a JSON string a digest, and {limit: NaN} no longer shares an identity with {limit: null}. package.json still reads 0.2.1, which is the version already on npm, so that fix cannot reach a consumer: the publish workflow refuses a version the registry already serves.

What

Version 0.2.1 → 0.2.2. No other change.

Proof

• pnpm run check:release — passes: 26 stable scripts, 12 required source artifacts, live checks explicitly external.

Note for anyone running that check on macOS: it fails on the default TMPDIR with Release file resolved through a symlink because /var/folders/... resolves through /private/var. That is the check working — it refuses a symlinked release path by design. Run it with a real path (TMPDIR=/private/tmp/...).

Simplification

None. A version bump so an existing fix can ship.

Net: +1/-1 lines, 1 file.
Not done here: nothing.

Tests

Tests: +0, -0. A test asserting a version string is a change detector; check:release and the publish workflow's registry-collision refusal already prove what matters.

[tangletools]

✅ Auto-approved drewstone PR — a533ebd5

This PR was opened by the trusted drewstone account.

This approval is provisional and was applied by the local stand-in because the pr-reviewer webhook host is unreachable (2026-08-21). CI on this head is fully green. The full PR reviewer audit re-runs via the resweep when the service returns and will publish findings if it detects issues.