release: 8.2.1

[CryptoJones]

Patch release rolling up #229.

Fixed

• Hooks pinned to a canonical omind. Hook commands baked shutil.which("omind") into settings.json as an absolute path frozen at setup time, so whichever install sat first on PATH captured the wiring permanently. On a dev box that was an editable checkout's venv: self-update upgraded ~/.local/bin while all five hooks kept running a months-old build — silently, because the wiring still looked correct. Now resolves ~/.local/bin/omind, the uv-retargeted symlink, giving a pin that is absolute and stable. Every harness, not just Claude Code; doctor fails on a non-canonical pin.
• recall-note accepts titles containing /. The guard names notes by title in block messages, but those titles are sanitized when written, so the guard could block an action, demand a recall, and then refuse it — an impossible remediation loop across 73 of 831 notes on the vault that surfaced it.
• self-update re-provisions and warms the index. Not a rebuild: opening the index runs the existing SCHEMA_VERSION check, paying a migration during the update rather than ambushing the next search.
• guard pause capped at 4h + a PAUSED banner in session priming. One machine was found paused for 185h with enforcement silently off.

Changed

• doctor reports the deny rate, warning above 25%. The install that motivated this sat at 51% — one action in two — which raw counts hid.

Added

• docs/install-verification.md — an agent-executable acceptance matrix for new installs (~70 rows). Behavioral rather than by inspection; the deny set is exercised through guard explain so nothing destructive ever runs.

Version

Bumped in lockstep: pyproject.toml, src/omind/__init__.py, uv.lock. 928 tests pass, ruff clean.

Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

[coderabbitai]

Warning

Review limit reached

@CryptoJones, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

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

How do review 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 refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 6bf5d66d-1341-4f0a-b97d-750d82f9af95

📥 Commits

Reviewing files that changed from the base of the PR and between 8f21e44 and 6f3d3ad.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• CHANGELOG.md
• pyproject.toml
• src/omind/__init__.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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