chore: prepare v0.3.0 release

[mohanagy]

Summary

• Prepare the next pre-1.0 minor release, 0.3.0, from development.
• Move the merged [Security] Prevent same-agent self-approval in fallback confirmation flows #96, [Security] Harden generated multi-profile configs against silent profile switching #97, and [Clients] Classify privileged management tools and generate permission guidance #98 release notes into a dated changelog section.
• Synchronize package metadata, lockfile, preset compatibility documentation, and the versioned release contract.

Release rationale

#96 intentionally changes the public fallback-confirmation behavior to fail closed and introduces the explicit security.approvalMode: "delegated-agent" opt-in. Under the pre-1.0 release policy, this user-visible compatibility change requires a minor release rather than a patch.

Security impact

This PR adds no runtime behavior. It releases the already-reviewed approval, multi-profile, and management-tool hardening from #96, #97, and #98 under accurate versioned contracts.

Test-first and validation

• Advanced the release contract to 0.3.0; it first failed because package metadata and a dated changelog entry were still 0.2.1, then passed after the minimal updates.
• Full local validation passed: npm test (1,023 passed, 22 expected skips), npm run test:core (392 passed, 22 expected skips), npm run test:coverage (95.47% statements, 92.00% branches), npm run lint, npm run typecheck, npm run build, npm run smoke:cli, npm run check:pack, and npm run test:package.

Summary by CodeRabbit

• Release

  • Updated the package version to 0.3.0.
  • Added the dated 0.3.0 release entry to the changelog.

• Documentation

  • Updated the documented catalog version to 0.3.0.

• Tests

  • Updated release validation and generated release note expectations for version 0.3.0.

[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: bfdd8a2e-f3b1-453d-9e5e-e5e425daea7b

📥 Commits

Reviewing files that changed from the base of the PR and between 910762b and daaad6a.

⛔ 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 package version is bumped to 0.3.0, the changelog and catalog documentation are updated, and release-version tests now validate the 2026-07-18 release metadata and revised release notes.

Changes

Release 0.3.0

Layer / File(s)	Summary
Release metadata and documentation package.json, CHANGELOG.md, docs/presets-and-clients.md	Package metadata, changelog entries, and the documented catalog version now reference 0.3.0.
Release artifact test contract tests/release-version.test.ts	Tests now validate the 0.3.0 version, dated release headings, error messages, changed-section content, issue references, and highlight patterns.

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

Possibly related PRs

• mohanagy/miftah#45: Updates the shared release-artifact test contract for a package version change.
• mohanagy/miftah#76: Updates changelog headings, package version metadata, and release-version expectations.
• mohanagy/miftah#92: Updates changelog and release-note contract expectations for a version bump.

Poem

A rabbit hops past version two,
To three-point-zero, fresh and new.
The changelog blooms, the tests agree,
Release notes bound with certainty.
“A tidy launch!” cheers Bunny glee.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: preparing the v0.3.0 release.
Description check	✅ Passed	The description matches the template's main sections and includes rationale, security impact, and validation results.
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/v0.3.0-prep

---

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