release: prepare v0.5.5

[mohanagy]

Summary

• prepare the compatible v0.5.5 patch for the task-first Console correction delivered in Console: lead with connections and named accounts #318
• align package, lockfile, README, feature guide, compatibility docs, and changelog on 0.5.5
• tighten the release contract around named account profiles, durable defaults, live miftah_use_profile availability, and collapsed authentication reference
• keep Miftah explicitly experimental and external validation incomplete under [Product] Validate the local multi-account MCP broker wedge with design partners #25, [Release] Validate Console/OAuth compatibility, recovery, and design-partner evidence #88, and [Product] Make trust controls and multi-account onboarding discoverable #202

Refs #319
Refs #202

Validation

• TDD red: release contract failed on package 0.5.4 and the missing 0.5.5 changelog section
• focused release/docs contracts: 27 passed
• npm test on supported Node 24.18.0: 1,808 passed, 33 platform skips
• npm run test:core: 425 passed, 26 platform skips
• npm run test:coverage on supported Node 24.18.0: 1,808 passed, 33 platform skips; 95.67% statements, 91.91% branches
• npm run lint
• npm run typecheck
• npm run build
• npm run smoke:cli
• npm run check:pack: 48 files
• npm run test:package: 26 passed
• npm audit --audit-level=moderate: 0 vulnerabilities
• exact merged development CI run 30604518633: green after one unchanged Windows Node 20 ACL-probe retry

Release boundary

This PR targets development. It does not publish. Publication remains restricted to an exact-main v0.5.5 GitHub Release and the protected trusted-publishing workflow. The three unaided evaluator sessions required by #202 are still missing and are not claimed here.

[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: 23 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: 779b9144-c4bf-4b65-8b61-ae64b3923c38

📥 Commits

Reviewing files that changed from the base of the PR and between deed1d4 and a1ef74b.

⛔ 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.}

[mohanagy]

Independent exact-head review completed because CodeRabbit was rate-limited and supplied no substantive review.

• Initial review found the release contract did not fully enforce durable-default wording, conditional live-switch availability, collapsed authentication reference, or the exact [Product] Validate the local multi-account MCP broker wedge with design partners #25/[Release] Validate Console/OAuth compatibility, recovery, and design-partner evidence #88/[Product] Make trust controls and multi-account onboarding discoverable #202 external-validation trackers.
• Corrective commit a1ef74b46309bc68d9f8fcbe472cb0895c7a3336 tightened only tests/release-version.test.ts; focused release contracts and lint pass.
• Independent re-review of exact head a1ef74b46309bc68d9f8fcbe472cb0895c7a3336: clean, no remaining findings.
• Seven-file release-only scope remains unchanged; no source, public API, workflow, dependency, or security-control change.

Current-head Linux/macOS/Windows/quality/package CI remains required before merge.