chore: release 0.0.27

[tonychang04]

Version bump 0.0.26 → 0.0.27. First release shipping #76: project create|link no longer installs the neon-postgres agent skill (postgres is instadb-backed plain Postgres via DATABASE_URL); stack skills = insta + tigris + better-auth.

After merge: tag v0.0.27 → release workflow builds the 5 binaries + GH Release, publish-npm publishes via OIDC.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CxB7Ne388bqDU7C2zGv86a

---

Summary by cubic

Release 0.0.27 of the CLI. Ships #76: project create|link no longer installs neon-postgres; Postgres now uses instadb-backed plain Postgres via DATABASE_URL, and the default stack skills are insta, tigris, and better-auth.

• Migration
  • Set DATABASE_URL for Postgres and remove any reliance on the neon-postgres agent skill in create/link flows.
  • Update scripts or docs that assumed the agent was installed to use plain Postgres via DATABASE_URL.

^{Written for commit 3ecb41f. 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]

Summary

Clean, minimal patch release (0.0.26 → 0.0.27) that correctly ships #76 with the version bumped consistently in package.json and package-lock.json.

Requirements context

No docs/superpowers/ or docs/specs/ directory exists in this repo — assessing against the PR description and repo release conventions (.github/workflows/release.yml) alone. No requirements invented.

Findings

Critical

(none)

Suggestion

(none)

Information

Functionality — release claim verified. The PR body states this is "the first release shipping #76." Confirmed: the base commit 365dcfb is the #76 merge (fix(skills): stop installing the neon-postgres agent skill), and the prior release 0.0.26 (#75, cbb58d1) predates it — so #76 first reaches the registry with 0.0.27. Claim is accurate.

Software engineering — version bump is complete. No hardcoded version constant needs syncing: src/index.ts:51 resolves the CLI version dynamically from package.json at runtime, and the release binaries take their version from the pushed tag via --define INSTA_CLI_VERSION (release.yml). package.json:3 and both package-lock.json occurrences (root name/version and packages[""].version) were updated to 0.0.27; no stray 0.0.26 references remain anywhere in the tree. publish-npm runs npm ci, so lockfile↔manifest consistency matters here — and it holds, so npm ci won't break.

Functionality — channel routing is correct. 0.0.27 has no - prerelease suffix, so per release.yml it will be marked GitHub "Latest" and published to the npm latest dist-tag — the intended production channel for this release.

Process note (not a code issue). No source/test changes are expected for a version-bump release, and none are present; the repo keeps no CHANGELOG, and the release workflow uses --generate-notes, so nothing else needs hand-editing. The remaining step is the post-merge v0.0.27 tag that actually triggers the build + OIDC npm publish.

Verdict

approved (informational — no Critical findings; the GitHub green-check approval remains a separate human action). This is a correct, in-scope release PR.

[jwfing]

LGTM - approved.