chore(release): 0.0.25 — limits commands

[tonychang04]

Version bump for the limits release (#72 merged). After merge: git tag v0.0.25 <merge-sha> && git push origin v0.0.25 — the tag push runs binaries + npm (the complete path, per the 0.0.24 lesson).

Hold the tag until insta-platform's deploy carrying #156 is live in prod — the new commands 404 against an undeployed platform.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JQ9NX4AN5XEmb3sjBHvTzS

---

Summary by cubic

Bump the insta CLI to v0.0.25 to ship the new limits commands: insta compute limits and insta db limits.

• Migration
  • After merge: git tag v0.0.25 && git push origin v0.0.25
  • Hold the tag until the insta-platform deploy with #156 is live in prod (the new commands will 404 otherwise).
  • Tag push triggers GitHub binaries and npm publish.

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

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[jwfing]

Review: chore(release) 0.0.25 — limits commands

Summary: Clean, complete patch bump of 0.0.24 → 0.0.25 across package.json and package-lock.json to carry the just-merged #72 limits commands — no correctness, security, or performance concerns.

Requirements context

No /docs/superpowers/ spec/plan applies here — this is a release-mechanics PR, so I assessed it against the PR description and the project's version-release skill (which defines a version bump merged to main before tagging as the correct precursor step). This PR is exactly that step.

Findings

Critical — (none)

Suggestion — (none)

Information

• Software engineering: Bump is complete and consistent. All three version sites are at 0.0.25 — package.json:3, package-lock.json:3 (root) and package-lock.json:9 (packages[""]). No stale 0.0.24 remains anywhere in the tree, and the dependency graph is unchanged (commander ^12.1.0), so the lockfile delta is version-only — avoiding the common incomplete-bump mistake of updating only one lockfile site.
• Functionality: The version is the single source of truth — src/index.ts:51 resolves it dynamically from package.json for program.version(...), and src/observe/install.ts:11 reads the same file. No hardcoded version string exists to drift, so insta --version will correctly report 0.0.25. The release commit sits directly atop 6ab3a9b (Merge #72), so the limits commands (insta compute limits / insta db limits) are genuinely present in this branch — the bump is meaningful, not premature.
• Functionality (sequencing): The PR body's caveat to hold the v0.0.25 tag until insta-platform's deploy carrying #156 is live in prod is correct and important — the new commands 404 against an undeployed platform. This is an operational note for the tagger, not a code issue; nothing to change here.
• Security / Performance: No security-relevant or performance-relevant changes — version metadata only, no new/changed dependencies, no code paths touched.
• Testing: No tests needed. A version bump has no new behavior to cover; the dynamic-resolution path is pre-existing and unchanged.

Verdict

approved (informational — no Critical findings; posted as a COMMENT, human approval still via the approve flow). Reminder for the tagger, per the version-release skill: tag v0.0.25 on the main merge commit and confirm the tag doesn't already exist before pushing (npm publish is irreversible), and honor the platform-deploy hold noted above.

[jwfing]

LGTM - approved.

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[jwfing]

LGTM - approved.