bump version to 0.0.22

[jwfing]

Summary by cubic

Bump insta version to 0.0.22 to prepare the next release. No code changes; version only.

^{Written for commit f10b20c. Summary will update on new commits.}

[jwfing]

Review — bump version to 0.0.22

Summary: Single-line version bump 0.0.21 → 0.0.22 in package.json; no code changes, exactly as described.

Requirements context

No matching spec/plan found — this repo has no docs/, docs/specs/, or docs/superpowers/ directory. Assessing against the PR description alone (a release-prep version bump). Verified the bump is consistent with the release mechanism in .github/workflows/release.yml: the publish-npm job runs npm publish, which publishes package.json's version, so bumping to 0.0.22 correctly preps a future v0.0.22 tag/release.

Findings

Critical — (none)

Suggestion — (none)

Information

• Software engineering: package-lock.json keeps a root version of 0.0.0 (package-lock.json:3) rather than tracking the package version. This is unchanged by this PR and is deliberate/harmless here — I ran npm ci against the bumped package.json and it succeeded (exit 0), so no lockfile desync is introduced and CI's npm ci step is unaffected. No action needed; noting only for completeness.

Dimension notes

• Software engineering: package.json:3 is the only changed line — tightly scoped, one concern. No tests are warranted for a version-string bump (nothing testable changed); CI gates (npm ci / tsc --noEmit / vitest run) are unaffected.
• Functionality: Monotonic increment 0.0.21 → 0.0.22. npm publish in release.yml derives the published version from package.json, so a subsequent v0.0.22 tag will publish a matching version. No gaps.
• Security: No security-relevant changes — no new inputs, dependencies, secrets, or auth surface touched.
• Performance: No performance-relevant changes.

Verdict

approved (informational — a human still gives the explicit GitHub approval via the approve flow). No blocking issues.

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[Fermionic-Lyu]

LGTM, Approved. (Relaying John-bot's approved verdict — approved with the maintainer account, since John-bot can't approve its own PR.)