chore: prepare the 2.6.0 release

[bagowix]

Summary

Prepare the 2.6.0 minor release.

• Bump the package version from 2.5.0 to 2.6.0.
• Move the current [Unreleased] changelog entries into [2.6.0] - 2026-08-12.
• Update changelog comparison links and the comparison-page release version.
• Regenerate docs/llms-full.txt.

Minor, not patch: the release includes backward-compatible public additions —
CircuitBreaker.call_sync() / call_async(), Registry.names() / items()
and the read-only wrapped property on the httpx2/httpx transports.

Checklist

• Tests added or updated (suite stays at 100% coverage)
• uv run ruff format --check and uv run ruff check pass
• uv run mypy, uv run pyright and uv run pyrefly check pass
• Docs updated (docs/) for user-facing changes
• CHANGELOG.md [Unreleased] updated
• Commits follow Conventional Commits

Additional release checks: the package build passes (interlock_cb-2.6.0).
Griffe reports only the expected public VERSION change (2.5.0 → 2.6.0).

Related issues

Closes #155
Closes #156
Closes #157
Closes #158
Closes #159

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 25973d4c-fa3a-42ce-8f81-e5a029ba5d8a

📥 Commits

Reviewing files that changed from the base of the PR and between 00d8a54 and 92dffc6.

📒 Files selected for processing (4)

• CHANGELOG.md
• docs/comparison.md
• docs/llms-full.txt
• interlock/version.py

---

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

[codspeed-hq]

Merging this PR will not alter performance

✅ 28 untouched benchmarks

---

_{Comparing release/2.6.0 (92dffc6) with main (00d8a54)}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!