v0.2.2

Accuracy + reliability patch from a full library review: five silent false-negative classes closed, two false-positive classes stopped, and the [rag] semantic layer works for the first time.

Fixed

• rag adapter crashed on every call — it read result.is_faithful, a field attune-rag's FaithfulnessResult has never had. faithful is now derived from unsupported_claims; calling the sync judge inside a running event loop raises a clear error.
• Fences with an info string (```python title="ex.py") are now extracted; previously everything inside went unchecked.
• Bare (untagged) code fences are now import-checked via speculative ast.parse — no new false positives.
• One broken command no longer aborts a whole checker — missing/timed-out --help binaries and bad env_python degrade per-flag / per-import.
• Years near a count keyword no longer false-positive (1900–2099 compared only when the keyword directly follows the number); count-source keywords match on a word boundary.
• Link targets can no longer escape project_root; site-absolute targets resolve under the root.

Added

• FindingKind.CHECKER_ERROR for checker infrastructure failures
• Per-call import-resolution cache (one subprocess per distinct module)
• VerifyContext.judge typed Optional[Judge]
• black enforced in CI alongside ruff

Full detail: CHANGELOG.md