chore: prepare v0.3.2 release

[mohanagy]

Fixes #127

Release contents

• Bumps @lubab/miftah to 0.3.2 and synchronizes the lockfile plus generated compatibility documentation.
• Records the completed PostHog command-wrapper routing fix (fix: classify PostHog exec reads and align route preview with enforcement #106), downstream-close containment fix (test: diagnose clustered identity-manager timeouts in full coverage runs #112), and esbuild 0.28.1 security remediation (security: triage npm audit low-severity dependency advisory #120).
• Updates the release artifact contract for the exact version and release notes.

Local validation

• npm audit --json — clean
• focused release and preset-doc contracts — passed
• npm run lint — passed
• npm run typecheck — passed
• npm run build — passed
• npm run smoke:cli — passed
• npm run check:pack — passed
• npm run test:package — 17 passed
• npm run test:core — 393 passed, 23 platform skips

The first local npm test run encountered startup/discovery-sensitive failures now recorded in #130, #131, and #132. Focused #130 and #132 files subsequently pass unchanged; #131 has reproduced one intermittent startup timeout. No timing, coverage, or containment behavior was changed. This release must not be promoted unless the current-head CI matrix is entirely green.

Summary by CodeRabbit

• Bug Fixes

  • Improved shutdown containment behavior.
  • Resolved an advisory related to the development server.
  • Addressed PostHog command-wrapper grammar and upstream process containment issues.

• Chores

  • Released version 0.3.2 with updated changelog and documentation.
  • Updated release validation for the new version.

[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: 5eb80e3b-77ff-43d2-b411-cdb1615e9a3d

📥 Commits

Reviewing files that changed from the base of the PR and between 83d9719 and 92cec92.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• CHANGELOG.md
• docs/presets-and-clients.md
• package.json
• tests/release-version.test.ts

---

📝 Walkthrough

Walkthrough

The release is prepared for version 0.3.2 by updating package and documentation versions, adding changelog entries, and revising release-version tests for the new heading, date, error text, and fixed-item content.

Changes

v0.3.2 release preparation

Layer / File(s)	Summary
Update v0.3.2 release metadata CHANGELOG.md, package.json, docs/presets-and-clients.md	Package metadata and documentation now use 0.3.2, while the changelog adds the dated release section and fixed entries.
Align release-note tests tests/release-version.test.ts	Release artifact tests validate the v0.3.2 changelog heading and error text, and release-note tests assert the updated fixed entries.

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

Possibly related PRs

• mohanagy/miftah#100: Updates the same release-version metadata and releaseNotes() test expectations.
• mohanagy/miftah#76: Updates versioned changelog sections and release-version tests.
• mohanagy/miftah#92: Updates changelog release sections and version-specific release-note validation.

Poem

A rabbit checks the version line,
“0.3.2” now looks divine.
The changelog blooms, the tests agree,
Fixed notes hop in merrily.
Release carrots, neatly packed! 🐇

---

Important

Pre-merge checks failed

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

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	It includes a summary and validation notes, but the required Security impact section is missing.	Add the missing Security impact section and explicitly address dependency, subprocess, and failure-behavior changes.
Linked Issues check	❓ Inconclusive	The version, changelog, docs, and release-note updates fit #127, but the lockfile change is in excluded package-lock.json and can't be verified.	Provide the package-lock.json diff or remove the path filter so the lockfile update can be verified.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	It clearly states the v0.3.2 release prep and matches the change set.
Out of Scope Changes check	✅ Passed	The changes are limited to release versioning, changelog/docs updates, and release-note test adjustments.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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/v0.3.2-prep

---

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