release: prepare v0.5.1

[mohanagy]

Summary

Refs #297. This is the release-artifact PR only; it does not publish, tag, or promote to main.

• Bumps @lubab/miftah and lockfile metadata from 0.5.0 to 0.5.1.
• Moves the reviewed first-use README, owner guide, setup-wizard front door, and aggregate test-isolation notes into dated v0.5.1 release notes.
• Updates the README, owner guide, and preset/client compatibility document to install/declare 0.5.1.
• Tightens the release contract around the patch contents and the still-open external evaluator boundary.

Release rationale

npm latest is 0.5.0. The exact v0.5.0..development delta is a compatible corrective set: documentation/onboarding fixes, numbered/back/cancel wizard usability, and test-isolation maintenance. It contains no intentional public API incompatibility or new broad capability family, so 0.5.1 is the correct patch release.

This release does not claim that external validation under #25, #88, #202, #204, or #290 is complete.

TDD evidence

The updated release contract first failed because package/lock metadata still reported 0.5.0 and no dated 0.5.1 changelog section existed. After the release alignment, focused release/README/preset/feature-guide contracts pass 31/31.

Local validation

Passed on Node 22.22.3:

• npm audit --omit=optional --audit-level=high: 0 vulnerabilities.
• npm run test:core: 425 passed, 26 expected skips.
• npm run test:coverage: 1,783 passed, 33 expected skips; 95.65% statements, 91.89% branches, 98.66% functions.
• 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/docs contracts: 31 passed.

Two ordinary aggregate npm test runs each completed 1,782 tests before unrelated unchanged process-heavy contracts observed different aggregate-only outcomes. The exact doctor test/file then passed (1/1 and 28/28); the exact upstream recovery file passed 10/10; the full coverage aggregate passed all 1,783 tests. Both observations are recorded under #297. No timeout, skip, worker, coverage, production, runtime, or containment change was made. Fresh current-head CI is the mandatory aggregate release gate.

Next release steps

1. Require every current-head CI and review gate, including Linux quality coverage and Linux/macOS/Windows Node 20/22/24.
2. Merge into development only when green.
3. Open a separate development → main promotion PR with no release drift.
4. After promotion and post-merge main CI are green, create GitHub Release v0.5.1 at the exact current main commit. The protected trusted-publishing workflow performs npm publish --provenance; no workstation publish or registry token is used.
5. Verify npm registry version/provenance, workflow result, tag/commit alignment, and fresh installed-package behavior before closing [Release] Publish v0.5.1 first-use onboarding fixes #297.

Summary by CodeRabbit

• Release

  • Updated the package version to 0.5.1.
  • Added a dated v0.5.1 changelog entry.

• Documentation

  • Updated installation instructions and setup guidance to use @lubab/miftah@0.5.1.
  • Clarified the release’s experimental, pre-1.0 status.

• Tests

  • Updated release checks and documentation validation for v0.5.1.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 62ddb1a1-6e67-4bfd-8082-fd2bc2ed199a

📥 Commits

Reviewing files that changed from the base of the PR and between 7a2cc73 and ec7ee2c.

⛔ 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

---

📝 Walkthrough

Walkthrough

The package version is bumped to 0.5.1, installation references and catalog documentation are aligned, a dated changelog entry is added, and release-version tests are updated for the new artifacts and first-use correction wording.

Changes

v0.5.1 release preparation

Layer / File(s)	Summary
Release metadata and documentation package.json, CHANGELOG.md, README.md, docs/*.md	Sets the package version and documented installation references to 0.5.1, and adds the dated corrective release entry.
Release validation expectations tests/release-version.test.ts	Updates release artifact assertions and validates the revised changelog wording while retaining the experimental pre-1.0 status check.

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

Possibly related issues

• mohanagy/miftah issue 297 — Covers the v0.5.1 release preparation reflected by the version, documentation, changelog, and test updates.

Possibly related PRs

• mohanagy/miftah#291 — Updates the same release-version and documentation contract surface.
• mohanagy/miftah#162 — Adjusts release-version tests and experimental package-status expectations.
• mohanagy/miftah#100 — Bumps package and release artifact version expectations.

Poem

A rabbit hops through versions bright,
From zero-five-oh to zero-five-one tonight.
The changelog blooms, the tests agree,
Docs point where the package should be.
Experimental whiskers still sway—
“Pre-one-point-oh!” they proudly say.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately describes the release-prep change to v0.5.1.
Description check	✅ Passed	The description is detailed and covers summary, rationale, and validation, though it does not use the exact template headings or an explicit Security impact section.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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

📝 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.1-prep

---

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