chore(release): 0.0.35

[Fermionic-Lyu]

Version bump shipping the feedback.instacloud.com default endpoint (#101). Tag v0.0.35 after merge → binaries + npm via OIDC.

🤖 Generated with Claude Code

---

Summary by cubic

Release 0.0.35 sets the CLI’s default feedback endpoint to feedback.instacloud.com. Previously the CLI used its prior default endpoint; now it targets feedback.instacloud.com by default. Users who explicitly set an endpoint are unaffected. This PR only bumps version fields in package.json and package-lock.json to publish the change introduced in #101.

• Rollout
  • Tag v0.0.35 after merge; publish binaries and the npm package via OIDC.
  • No migration needed; endpoint overrides remain supported.

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

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[jwfing]

Review — chore(release): 0.0.35

Summary: Clean, correctly-scoped version bump (0.0.34 → 0.0.35) touching only package.json and package-lock.json, shipping the feedback.instacloud.com default endpoint from #101.

Requirements context

No /docs/superpowers/ (or matching spec/plan) directory exists in this repo — assessing against the PR description, the version-release conventions, and the base branch state alone. The version-release skill governs the release flow this PR feeds into.

Findings

Critical — (none)

Suggestion — (none)

Information

• Functionality: Verified the bump is consistent — version is 0.0.35 in both package.json and the two package-lock.json locations (top-level + packages[""]); no dependency graph changes crept in.
• Functionality: Idempotency confirmed — the latest existing tag is v0.0.34; v0.0.35 does not yet exist, so the follow-up tag/release will not collide. The bump is a clean monotonic increment.
• Functionality: Release payload confirmed — the base commit (788d980) is the merge of #101 (feat: feedback posts to feedback.instacloud.com), and feedback.instacloud.com is present at src/commands/feedback.ts:42. The release genuinely ships what the body claims.
• Software engineering: No code changed, so no new tests are expected; scope is limited to release metadata. Per the version-release flow, tagging v0.0.35 after merge triggers the npm publish pipeline via OIDC — expected side-effect, worth an eyeball at tag time.
• Security / Performance: No security- or performance-relevant changes — no source, dependency, or lockfile-resolution changes beyond the self-version fields.

Verdict

approved (informational — no Critical findings). Standard release bump; ready to merge and tag v0.0.35. Human still gives the explicit GitHub approval via the approve flow.

[jwfing]

LGTM - approved.