chore: prepare the 2.7.0 release

[bagowix]

Summary

Prepare the 2.7.0 minor release.

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

Minor, not patch: the release adds public API. #177 gives every HTTP client integration a rejection type that lives in the host library's own hierarchy — CircuitOpenTransportError (httpx, httpx2), CircuitOpenClientError (aiohttp), CircuitOpenRequestError (requests), plus CallTimeoutTransportError and BulkheadFullTransportError on the two httpx transports.

Nothing an existing caller does stops working: a rejection is still a CircuitOpenError carrying breaker_name, retry_after and last_failure; it now also carries the host base type. The one behavioural difference is the point of the change — except httpx.TransportError, except aiohttp.ClientError and except requests.exceptions.RequestException now catch a rejection where it previously escaped to an outer except Exception. The bases are the broadest "the request never completed" types, never a leaf, so no typical retry predicate starts firing on a rejection; the changelog entry records that choice.

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.7.0), twine check PASSED on both artefacts, and griffe reports the VERSION attribute (2.6.1 → 2.7.0) as the only public difference — the new exception types are additions, so nothing is flagged as a breakage.

Related issues

#177

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 7 minutes

Limit details: You’ve used all 3 included reviews currently available.

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 934477d1-9987-4019-b106-a6e7916b95c9

📥 Commits

Reviewing files that changed from the base of the PR and between bb8605f and baaf947.

📒 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.}

[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!

[codspeed-hq]

Merging this PR will not alter performance

✅ 28 untouched benchmarks

---

_{Comparing release/2.7.0 (baaf947) with main (bb8605f)}