chore(main): release 0.22.0

[mlorentedev]

🤖 I have created a release beep boop

0.22.0 (2026-06-26)

Features

• harness: agnostic agent-skill presence by uniform injection (#607) (3d61c2c), closes #559
• secrets: add the Bitwarden backend resolver to dotf secrets (#606) (736273b)
• secrets: strip backend unlock credentials from the run child env (#610) (8b56f1f)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Warning

Review limit reached

@mlorentedev, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 10 minutes and 56 seconds. Learn how PR review limits work.

To continue reviewing without waiting, enable usage-based billing in the billing tab.

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e02f222c-841e-483a-8693-965a0399dfcc

📥 Commits

Reviewing files that changed from the base of the PR and between 0686581 and 663bd7b.

📒 Files selected for processing (3)

• .release-please-manifest.json
• CHANGELOG.md
• versions.conf

📝 Walkthrough

Walkthrough

Bumped the project to version 0.22.0 in the release manifest and pinned version config, and added the v0.22.0 changelog entry dated 2026-06-26.

Changes

Release metadata update

Layer / File(s)	Summary
Version bump and release notes .release-please-manifest.json, versions.conf, CHANGELOG.md	Updates the tracked release version to 0.22.0 and adds the corresponding changelog entry for v0.22.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• mlorentedev/dotfiles#449: Updates the same release-version files for another automated version bump.
• mlorentedev/dotfiles#455: Also updates .release-please-manifest.json, versions.conf, and CHANGELOG.md as part of a release bump.
• mlorentedev/dotfiles#602: Touches the same versioning files while moving the project to 0.22.0 from an earlier release line.

Suggested labels

autorelease: tagged

Poem

🐰 I hopped through the release trail bright,
From 0.21.1 to 0.22.0 tonight.
A changelog nibble, a version sprout,
All neat and tidy, no rabbit doubt.
Thump thump — the new tag shines just right.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR only performs a release/version bump and changelog update; it does not implement the curator harness work required by #559.	Add the #559 engine and harness changes: curator AGENT.md, minimal agents manifest and agent-md support, forced-skill hook emission, and compile-harness.bats coverage.
Description check	⚠️ Warning	The PR description is a release note, but it does not include the required Summary, SDD checklist, or Test plan sections from the repository template.	Rewrite the description using the template and fill in the Summary, SDD checklist, and Test plan sections, or add a specific skip-sdd rationale if applicable.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately describes the release version bump in the changeset.
Out of Scope Changes check	✅ Passed	The changes are limited to release artifacts and version bumps, which are in scope for an automated release PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main

---

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

[mlorentedev]

🤖 Created releases:

• v0.22.0

🌻