docs: version-reset note (1.x/2.x → 0.x)

[moomooskycow]

Summary

• Prepends a version-reset note to CHANGELOG.md explaining the fleet's move to pre-stable 0.x semantics (Powder landmark-016/017).
• No functional changes.

Agent-Task: landmark-017

[cursor]

PR Summary

Low Risk
Documentation-only CHANGELOG edit with no code, config, or release automation changes.

Overview
Prepends a version reset section to CHANGELOG.md documenting the fleet move from 1.x/2.x to pre-stable 0.x (Powder landmark-016/017).

The note explains Cargo-style bumps below 1.0.0, that versions do not auto-cross 1.0.0, that v0.18.0 is the same commit as v1.18.0, and that legacy 1.x/2.x changelog entries remain as historical record while old tags/releases were retired. No runtime or tooling changes in this PR.

^{Reviewed by Cursor Bugbot for commit 1fa3238. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_6657142d-dd4d-496a-a067-2e5561a4b073)

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 30 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 40ca47f0-1996-4329-a9ec-d1369622e796

📥 Commits

Reviewing files that changed from the base of the PR and between 49b3ab3 and af2be21.

📒 Files selected for processing (1)

• CHANGELOG.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch version-reset-note

---

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

[gemini-code-assist]

Code Review

This pull request updates the CHANGELOG.md to document a version reset from v1.18.0 to v0.18.0 due to a transition to pre-stable 0.x semantics. The reviewer identified an inconsistency where the subsequent release entry still references the old 1.x versioning and contains outdated comparison links, which should be updated to avoid confusion and broken links.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

There is an inconsistency between this version reset note and the release entry immediately below it (line 5). The entry below is still titled # [1.19.0] and compares v1.18.0...v1.19.0. Since the version was reset from v1.18.0 to v0.18.0 and the 1.x tags were retired, the 1.19.0 release should be renamed to 0.19.0 (or 0.18.1 depending on breaking changes) and its compare link updated to use the new 0.x tags to avoid broken links and confusion.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1fa3238528

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align the reset note with the latest release

This note is inserted as the newest changelog entry, but it says the reset maps v1.18.0 to v0.18.0 while the immediately following release is v1.19.0 with additional fixes/features. In this state, readers and release tooling that use the top of CHANGELOG.md as the current release history can map the current code to the wrong 0.x tag or treat the v1.19.0 changes as retired old-numbering history. Either place the reset note at the v1.18.0 point in history or update it to describe the current v1.19.0 equivalent.

Useful? React with 👍 / 👎.

[github-actions]

🎉 This PR is included in version 0.19.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀