docs: add CHANGELOG for the new management commands

[Fermionic-Lyu]

Summary

Adds a CHANGELOG.md (Keep a Changelog format) covering the two feature releases that built out the CLI's management surface:

• 0.1.93 — project lifecycle, billing/usage inspection, orgs & members, backups, secrets rotate, storage S3 keys (#175)
• 0.1.94 — billing checkout/portal management and projects transfer (#176)

Documents user-facing features only; internal telemetry coverage (#177) is omitted.

🤖 Generated with Claude Code

---

Summary by cubic

Adds CHANGELOG.md for @insforge/cli, documenting 0.1.93 and 0.1.94 in Keep a Changelog format.
Highlights new management commands: project lifecycle, billing (checkout/portal, status/credits/cycles/history), organizations and members, backups, secrets rotation, storage S3 keys, projects transfer, and --help updates.

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

Note

Add CHANGELOG entries for releases 0.1.93 and 0.1.94

Adds a CHANGELOG.md documenting the new management commands introduced in releases 0.1.93 and 0.1.94, with links to the corresponding GitHub release tags.

^{Macroscope summarized afd8ca0.}

Summary by CodeRabbit

• Documentation
  • Updated release notes and changelog guidance.
  • Added entries for recent CLI releases covering billing, project transfers, project lifecycle actions, organization and member management, backups, secret rotation, and storage key operations.
  • Noted that the orgs and projects command groups now appear in help output.
  • Added release-tag reference links for the latest versions.

[coderabbitai]

Walkthrough

CHANGELOG.md now includes standard changelog guidance plus release notes for @insforge/cli versions 0.1.94 and 0.1.93, covering billing, project transfer, lifecycle, org/member, backup, secret rotation, and storage commands.

Changes

CHANGELOG updates

Layer / File(s)	Summary
Introduction and 0.1.94 notes CHANGELOG.md	Adds the changelog title and standard Keep a Changelog/SemVer guidance, then records 0.1.94 notes for billing and project transfer commands.
0.1.93 notes and links CHANGELOG.md	Records 0.1.93 notes for project lifecycle, billing/usage, org/member, backup, secrets, and storage commands, plus a --help visibility change and release-tag links.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A tiny changelog hop, hop, hop 🐇
Two shiny releases make the page not stop
Billing, backups, secrets, and keys
The rabbit nods: “All noted with ease!”

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main change: adding a changelog entry for new CLI management commands.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/changelog

---

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Greptile Summary

Adds a new CHANGELOG.md in Keep a Changelog format, documenting the two feature releases (0.1.93 and 0.1.94) that introduced the CLI's management surface.

• 0.1.93 documents project lifecycle commands, billing/usage read commands (billing status, billing credits, usage), orgs & members, backups, secrets rotation, and storage S3 key management, plus the orgs/projects help-visibility change.
• 0.1.94 documents billing management (billing upgrade, billing manage), billing inspection (billing history, billing cycles), and projects transfer; however, the placement of billing inspection here conflicts with the PR description that attributes it to 0.1.93 — the correct version should be confirmed against the source PRs.

Confidence Score: 4/5

Safe to merge after confirming the correct version for the billing history/billing cycles entries.

The only substantive concern is a potential version misattribution: billing history and billing cycles are documented under 0.1.94, but the PR description places billing/usage inspection in 0.1.93. If that's wrong, users reading the changelog to understand what shipped in which release will get incorrect information. Everything else — format, link anchors, wording — looks correct.

CHANGELOG.md — specifically the 'Billing inspection' bullet under 0.1.94.

Important Files Changed

Filename	Overview
CHANGELOG.md	New CHANGELOG.md in Keep a Changelog format covering v0.1.93 and v0.1.94; billing history/billing cycles appear under 0.1.94 but the PR description attributes billing inspection to 0.1.93.

_{Reviews (1): Last reviewed commit: "docs: add CHANGELOG covering the new man..." | Re-trigger Greptile}

[greptile-apps]

Billing inspection commands may be misattributed to 0.1.94

The PR description explicitly states that 0.1.93 (PR #175) covers "billing/usage inspection," while 0.1.94 (PR #176) covers only "billing checkout/portal management and projects transfer." The "Billing inspection" bullet (billing history, billing cycles) is placed here under 0.1.94 but looks like it belongs in 0.1.93 alongside billing status and billing credits. If these commands were actually shipped in #176 this is fine, but it conflicts with the description above — worth verifying against the source PRs.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[jwfing]

Summary

Docs-only PR adding a new CHANGELOG.md (Keep a Changelog format) for releases 0.1.93 and 0.1.94; I verified every documented command, flag, guard, date, and version attribution against the source tree and git tags — all accurate.

Requirements context

No matching spec/plan found under a /docs/superpowers/ directory (it doesn't exist in this repo). The repo keeps specs in docs/specs/, but the three present (diagnose-command, db-migrations) are unrelated to a changelog. Assessed against the PR description, the referenced PRs (#175, #176), and the actual shipped CLI surface.

Findings

Critical

(none)

Suggestion

• Software engineering / accuracy — CHANGELOG.md:43-44: the version links point at releases/tag/v0.1.9x. Both tags exist, so the links resolve, but the Keep a Changelog convention this file declares it follows (CHANGELOG.md:3-5) uses compare/<prev>...<this> diff ranges for the link reference section. Switching to compare links (or keeping tag links deliberately) is a minor consistency call — non-blocking.

Information

• Accuracy (verified, no action needed) — Spot-checked the full surface; all of it is correct:
  • billing upgrade <plan> / manage — both open the hosted Stripe URL via open() and, under --json, print the session object and skip the browser (src/commands/billing/index.ts:157-205). Matches the description exactly.
  • billing history / cycles are correctly attributed to 0.1.94 — they were introduced in f0c0755 (#176) and are absent from the v0.1.93 tag, which only carries status/credits. Good version split.
  • projects transfer <targetOrgId> and projects delete both force an explicit --project (resolveProjectId(opts, true)) and gate on a confirm prompt (src/commands/projects/manage.ts:118-200) — the "requires an explicit --project and is guarded for human approval" wording is accurate.
  • projects update-version --wait and backups create --wait flags exist as described (src/commands/projects/manage.ts:219-222, src/commands/backups/index.ts:95-99).
  • secrets rotate <api-key|anon-key> validates the key against ['api-key','anon-key'] and exposes --grace-hours (the "optional grace period") — src/commands/secrets/rotate.ts:10-31.
  • The Changed entry is real: at v0.1.92 both groups were program.command('orgs'/'projects', { hidden: true }); the hidden flag was dropped in v0.1.93, so they now appear in --help.
  • Dates are correct: v0.1.94 tagged 2026-06-24, v0.1.93 tagged 2026-06-23 — matching the ## [0.1.94] - 2026-06-24 / ## [0.1.93] - 2026-06-23 headers.
• Security — No security-relevant changes; this is documentation only, no secrets or tokens introduced.
• Performance — No performance-relevant changes; documentation only.
• Scope — Clean, single-file, additive (+45/-0). Explicitly scopes out internal telemetry (#177), which is the right call for a user-facing changelog.

Verdict

approved (informational — a human still gives the explicit GitHub approval). Zero Critical findings; the lone Suggestion is an optional link-format consistency tweak. Accurate, well-scoped documentation.