release: prepare v0.5.2

[mohanagy]

Summary

• bump package and lockfile metadata to 0.5.2
• add release notes for the configuration-discovery, Console reload-recovery, and environment-secret-readiness fixes
• update current install/version references in README and the 0.5 compatibility guides
• tighten the release contract so those fixes and the incomplete external-validation boundary cannot disappear

Security impact

This release-prep diff changes only version metadata, documentation, changelog text, and release contracts. It does not change credential handling, subprocess behavior, redaction, audit, containment, Windows behavior, configuration schema, or public APIs. The release notes explicitly preserve the security boundaries of PRs #302-#304.

Validation

• npm test — clean rerun: 1,797 passed; 33 conditional/platform skips
• npm run test:core — 425 passed; 26 conditional/platform skips
• npm run test:coverage — clean rerun: 1,797 passed; 33 skips; 95.67% statements
• 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

The first ordinary and coverage aggregates observed unchanged fixed-time subprocess failures during host contention. Every affected focused file passed unchanged, the ordinary aggregate rerun passed, and the coverage rerun passed after an unrelated concurrent Vitest workload ended. No timeout, skip, worker, coverage, runtime, or containment setting changed. Details are recorded on #305.

Tracks #305. Publication still requires a separate development to main promotion, exact-main GitHub Release, trusted publish, and registry/provenance verification.

Summary by CodeRabbit

• Bug Fixes

  • Improved Console configuration discovery reporting.
  • Preserved valid Console sessions across navigation and refresh, with recovery guidance.
  • Added clearer environment-secret readiness states and updated recovery guidance for CLI/Console handoff.
  • Updated handling of configuration changes to clear outdated completion guidance.

• Documentation

  • Updated installation instructions and all version references to 0.5.2.
  • Refreshed compatibility and “what’s new” content to reflect the corrective 0.5.2 release.

• Release

  • Published version 0.5.2.

[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: 48 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: 532139f5-829b-411d-bed6-cbe104f549d8

📥 Commits

Reviewing files that changed from the base of the PR and between 839ec3b and 7b261af.

📒 Files selected for processing (1)

• tests/release-version.test.ts

📝 Walkthrough

Walkthrough

Miftah is prepared for release 0.5.2. Package metadata, installation documentation, compatibility references, changelog content, and release-version tests now use the 0.5.2 version and dated release format.

Changes

0.5.2 release preparation

Layer / File(s)	Summary
Align 0.5.2 release metadata package.json, README.md, docs/whats-new-in-0.5.md, docs/presets-and-clients.md, CHANGELOG.md	Package version, installation commands, compatibility metadata, and changelog entries are updated for 0.5.2.
Update release validation tests tests/release-version.test.ts	Release tests now validate the 0.5.2 version, dated changelog headings, fixed-section content, and documentation references.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related issues

• [Release] Publish v0.5.2 Console onboarding recovery fixes #305 — Covers the 0.5.2 release preparation, version updates, changelog, documentation, and validation tests.

Possibly related PRs

• mohanagy/miftah#298 — Updates the same release artifacts and version-validation tests for the preceding patch release.
• mohanagy/miftah#162 — Modifies release-version assertions for release changelog content and project status.
• mohanagy/miftah#133 — Updates release-version tests and dated “Fixed” changelog expectations.

Poem

A rabbit checks the version line,
“0.5.2” now hops in time.
Changelog carrots neatly arrayed,
Docs and tests wear matching shade.
The release burrow’s tidy and bright—
Thump, thump, ship it right! 🐇

---

Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

• Ignore

❌ Failed checks (1 error)

Check name	Status	Explanation	Resolution
Docstring Coverage	❌ Error	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately reflects the v0.5.2 release-prep change.
Description check	✅ Passed	The description covers summary, security impact, and validation with concrete commands/results, matching the template well enough.
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.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/0.5.2

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@tests/release-version.test.ts`:
- Around line 73-76: Update the release notes assertions in the test around the
`notes` variable to extract the content of the `### Fixed` section before
checking issue links. Assert all four issue URLs against that extracted section
rather than the full release entry, while preserving the existing heading
assertion.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e07da5f2-656f-429a-af4d-5547964ab065

📥 Commits

Reviewing files that changed from the base of the PR and between dfddd06 and 839ec3b.

📒 Files selected for processing (1)

• tests/release-version.test.ts

[mohanagy]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

The sole actionable finding was fixed in 7b261af and its thread is resolved. Focused tests, lint, typecheck, and fresh current-head CI all pass. The requested current-head CodeRabbit re-review was rate-limited; the prior independent release review approved the patch.