release: prepare v0.5.7

[mohanagy]

Tracks #339

Summary

Prepare the compatible 0.5.7 patch release for the Console usability improvements merged in #335 through #338.

• reconcile current main ancestry before the next promotion, with an empty tree diff from the development parent
• bump package and lockfile metadata to 0.5.7
• move the four shipped Console changelog entries into the dated 0.5.7 section
• update the README and focused 0.5 documentation to install 0.5.7
• retain explicit pre-1.0 and incomplete external-validation language

Security impact

No runtime security boundary or dependency change is introduced by this release-only diff. Credential handling, routing, policy enforcement, redaction, audit behavior, no-shell subprocess execution, POSIX and Windows containment, and public APIs are unchanged.

TDD

The release-version contract was updated first and failed on package version 0.5.6 and the missing 0.5.7 changelog entry. It passes after the release-only metadata and documentation changes.

Validation

• npm test — 1,822 passed, 33 platform skips
• npm run test:core — 426 passed, 26 platform skips
• npm run test:coverage -- --maxWorkers=1 --maxConcurrency=1 — 1,822 passed, 33 skipped; 95.65% statements and 91.92% branches
• npm run lint
• npm run typecheck
• npm run build
• npm run smoke:cli
• npm run check:pack — 48 files verified
• npm run test:package — 26 passed
• focused release contract — 4 passed
• git diff --check
• current main is an ancestor of the PR head
• the ancestry-reconciliation merge has an empty diff from its development parent

The workstation currently reports Node 22.9 engine warnings for newer build tooling; all commands above still passed. Protected CI remains authoritative across supported Node 20/22/24 on Linux, macOS, and Windows.

Release boundary

No workstation publication is part of this PR. After merge to development, publication still requires a separate development-to-main promotion, exact-main GitHub Release v0.5.7, protected trusted publishing, and registry/provenance/fresh-install verification. External validation remains incomplete under #25, #88, #202, and #290.

[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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e3f71e6a-6744-422d-80d3-ec60bd88b3cf

📥 Commits

Reviewing files that changed from the base of the PR and between d2f37cf and ac2dbd5.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (6)

• CHANGELOG.md
• README.md
• docs/presets-and-clients.md
• docs/whats-new-in-0.5.md
• package.json
• tests/release-version.test.ts

---

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