bump version to 0.0.20

[jwfing]

Summary by cubic

Bump insta version from 0.0.19 to 0.0.20 in package.json to prepare the next patch release. No functional changes.

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

[jwfing]

Review: bump version to 0.0.20

Summary: A single-line patch version bump in package.json (0.0.19 → 0.0.20) with no functional changes — clean and correct.

Requirements context: No matching spec/plan found — docs/specs/ and docs/superpowers/ are both empty in this repo, so this is assessed against the PR description alone. The PR is a routine release-prep version bump per the version-release convention (package.json → tag → GitHub release; tagging/release are separate post-merge steps, correctly out of scope here).

Findings

Critical
(none)

Suggestion
(none)

Information

• Software engineering — package.json:3: the bump to 0.0.20 is a correct patch increment. No tests are needed: the version is resolved dynamically at runtime (src/index.ts:46 reads version from package.json via readFileSync), there are no hardcoded 0.0.19/0.0.20 strings in src/, and no CHANGELOG file exists to keep in sync. Nothing else references the version.
• Software engineering — package-lock.json: the lockfile's root version field is "0.0.0" (lines 3 and 9) and its name is "insta-cli" while package.json name is "insta". Both are pre-existing — the lockfile was already out of sync at 0.0.19 (not 0.0.20), so this PR neither introduces nor regresses the drift. Out of scope for this PR; flagged only as an FYI in case the team wants a one-time npm install to resync the lockfile in a separate change.

Security: No security-relevant changes — metadata-only edit, no new user input, dependencies, auth, or logging touched.

Performance: No performance-relevant changes.

Verdict

approved — zero Critical findings. Metadata-only version bump; safe to merge. (Informational; the explicit GitHub approval is a separate human action.)

[Fermionic-Lyu]

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

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}