chore(release): prepare v0.5.8

[mohanagy]

Refs #350.

Prepares the compatible v0.5.8 patch release after the actionable upstream-startup diagnostics in #348, safe dependency refresh in #349, and Windows ACL integration-test stabilization in #353.

Changes

• bump package and lockfile versions to 0.5.8
• add the dated v0.5.8 changelog entry with experimental and external-validation boundaries
• update first-use install/version references
• update the release artifact contract, including every concrete dependency claim

Security impact

• startup diagnostics remain bounded and secret-redacted
• dependency updates are compatible versions already validated across supported Node and operating-system combinations
• production ACL behavior, security rules, fail-closed boundaries, and timeouts are unchanged by test(windows): stabilize ACL probe budget #353
• Vitest 4 and TypeScript 7 remain explicitly excluded because their current upgrades do not pass release gates

Validation

• schema and release contract validation
• package.json and package-lock.json both report 0.5.8
• package contents: 48 files verified
• documentation install/version references updated
• dependency scope and deferred-major claims asserted
• npm test: 1,828 passed, 33 skipped
• npm run test:core: 426 passed, 26 skipped
• npm run test:coverage: 1,828 passed, 33 skipped; thresholds passed
• npm run test:oauth-console: 491 passed, 4 skipped
• 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
• npm audit reviewed: 5 existing advisories (1 moderate, 4 high); no broad audit-fix mutation applied

One initial local coverage run hit an unchanged 5-second filesystem timing timeout; the immediately preceding full run passed the same test in 139 ms, and the isolated coverage rerun passed it in 128 ms without changing thresholds or timeouts. The separate Windows ACL hosted-runner failure is fixed and validated by #353.

Summary by CodeRabbit

• New Features

  • Added clearer, actionable diagnostics when upstream services fail to start, with sensitive information redacted.
  • Improved recognition of pinned uvx configurations.

• Bug Fixes

  • Updated compatible dependencies to improve reliability and maintenance.

• Documentation

  • Updated installation instructions, package references, examples, and guidance for version 0.5.8.
  • Added release documentation covering startup diagnostics, uvx recognition, dependency updates, and known validation limitations.

[coderabbitai]

📝 Walkthrough

Walkthrough

The release preparation updates Miftah to version 0.5.8, refreshes installation documentation and changelog content, and aligns release artifact tests with the new version and release notes.

Changes

Release preparation

Layer / File(s)	Summary
Version and release artifact updates package.json, README.md, docs/presets-and-clients.md, docs/whats-new-in-0.5.md, CHANGELOG.md	The package version and documented installation commands now use 0.5.8. The changelog records startup diagnostics, dependency refreshes, and release status.
Release contract validation tests/release-version.test.ts	Release tests now expect version 0.5.8 and validate the updated changelog sections, references, diagnostics, maintenance commands, uvx, and dependency changes.

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

Possibly related PRs

• mohanagy/miftah#298: Both PRs prepare patch releases across package metadata, documentation, changelog, and release tests.
• mohanagy/miftah#306: Both PRs update patch-release artifacts and release-version assertions.
• mohanagy/miftah#328: Both PRs update package metadata, release documentation, changelog entries, and release assertions.

Poem

A rabbit checked the version line,
“0.5.8” now reads just fine.
The changelog speaks, the tests agree,
Docs guide installs reliably.
Hop, hop—release notes shine!

---

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
Linked Issues check	✅ Passed	The changes satisfy the coding-related requirements in [#350] for versioning, changelog, documentation, dependency scope, and release-contract updates.
Out of Scope Changes check	✅ Passed	The changes are limited to v0.5.8 release preparation, documentation, version metadata, changelog content, and related release tests.
Title check	✅ Passed	The title clearly identifies the release preparation and the target version, which matches the main changes.
Description check	✅ Passed	The description covers the release summary, security impact, validation results, known limitations, and referenced issues.

✨ 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/issue-350-v0.5.8

---

_{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`:
- Line 89: Update the release-notes assertions in the release version test to
verify each concrete dependency claim from the PR objectives, including dotenv,
TypeScript ESLint, Vitest 4, and TypeScript 7, rather than relying only on the
generic dependency match. Preserve the existing notes validation while adding
specific case-insensitive assertions for all named dependencies.

🪄 Autofix

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: 3a52b033-64f6-4ef2-a686-ed1a5269e006

📥 Commits

Reviewing files that changed from the base of the PR and between 6255210 and d8730be.

⛔ 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