release: v0.0.12

[tonychang04]

Ships to npm + binaries via the OIDC pipeline: optional project-create name (#34), next-action hints (#32), insta compute lifecycle commands, agents.instacloud.com docs (#31).

🤖 Generated with Claude Code

https://claude.ai/code/session_01GMbAe5K1RfwaAcge5inX7P

---

Summary by cubic

Publishes v0.0.12 of the insta CLI to npm and releases binaries via the OIDC pipeline. Adds next-step guidance, compute lifecycle commands, and smoother project creation with updated docs.

• New Features
  • Optional project-create name with a pasteable one-liner (fix: insta project create name optional (recommended one-liner was unrunnable) #34)
  • “Next:” hints to guide the next action after commands (feat(nextactions): send Insta-Hints and render Next: affordance #32)
  • Compute lifecycle: insta compute start|stop|suspend|status
  • Canonical docs at https://agents.instacloud.com (docs: agents.instacloud.com — canonical onboarding one-liner #31)

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

[jwfing]

LGTM - approved.

[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]

Summary

Release PR bumping package.json version 0.0.11 → 0.0.12; the bump itself is correct, but v0.0.12 has already been merged to main and already tagged on the remote, making this PR a stale duplicate that should not be merged.

Requirements context

No /docs/superpowers/ (or docs/specs/) directory exists in this repo, so there is no matching spec/plan — assessed against the PR description and the version-release process conventions. This PR matches the established release-PR pattern exactly: prior releases (e.g. v0.0.11 32d5166) are also single-line package.json version bumps with no CHANGELOG, so the change shape is correct.

Findings

Critical

Functionality — v0.0.12 is already released; this PR is a redundant/stale duplicate (package.json:3)

• The remote already carries refs/tags/v0.0.12, pointing at commit d445b2f (release: v0.0.12 (#36)), which is the current main HEAD and whose package.json is already at 0.0.12.
• This PR's branch head 4880bda shares parent 7507d32 with d445b2f but is not an ancestor of main. Its diff (0.0.11 → 0.0.12) is byte-for-byte identical to what already landed. Merging it against a main that is already at 0.0.12 is a no-op (or a same-line conflict) — it adds nothing.
• More importantly, re-running the release for v0.0.12 is a hard STOP under the project's release rules: an existing v<version> tag means the version must be bumped before releasing again (npm publishes and git tags are not safely re-writable). Proceeding here would either fail the idempotency check or, worse, attempt to overwrite a shipped release.
• Recommended action: close this PR rather than merge it. If a new release is intended, open a fresh PR that bumps to the next unused version (0.0.13) from current main.

Suggestion

(none)

Information

• Software engineering — no test changes required. A version-only bump needs no tests; the release is exercised by .github/workflows/release.yml (binaries via Bun + npm publish --provenance). Nothing to add here.
• Lockfile version is decoupled (pre-existing, not introduced by this PR). package-lock.json records "version": "0.0.0" at the root while package.json is 0.0.12. This is harmless for the pipeline — npm ci only enforces dependency sync (not the root version), and npm publish reads the version from package.json — and every prior release shipped with the same 0.0.0 lock. Worth aligning to the real version at some point for hygiene, but out of scope for a release PR.
• Security / Performance — no relevant changes. The diff is a single version string; no user input, secrets, dependencies, queries, or hot-path code are touched. npm publish uses OIDC trusted publishing (no token secret in the diff).

Verdict

request_changes — the version bump is correct in isolation, but v0.0.12 is already on main and already tagged v0.0.12 on the remote. This PR is a stale duplicate; it should be closed rather than merged, and any further release should target the next unused version.