Prepare release 0.4.1

[Mtrya]

Version bump: 0.4.0 → 0.4.1.

Included in this release

• Agent-driven setup guide, compat command, and setup diagnostics #31 — agent-driven setup guide (INSTALL_AI.md, closes Rework installation docs into an agent-native setup tree (INSTALL_AI.md) #29), kimi-bridge compat command + packaged compatibility map, Telegram non-allowlisted sender logging, clean one-line startup failures, doctor unknown-keys warning, README/INSTALL/CONFIGURATION rework.
• chore: support kimi-code 0.29.2 #30 — kimi-code 0.29.2 support (already on main).

Changes here

• pyproject.toml / uv.lock: 0.4.0 → 0.4.1.
• compatibility-map.json: appended the 0.4.1 record (0.28.1, 0.29.0, 0.29.1, 0.29.2 — copied verbatim from the current manifest).
• tests/test_compatibility.py, tests/test_main.py: derive map-dependent expectations dynamically (latest record names the current package version; tested range computed from the map) so future releases do not edit tests.

Validation (UV_CACHE_DIR=/tmp/kimi-bridge-release-0.4.1-cache)

• uv lock --check — pass
• uv run --locked python scripts/check_release.py — release identity valid: kimi-bridge 0.4.1
• uv run --locked pytest -q — 356 passed
• uv run --locked ruff check . — clean
• git diff --check — clean
• uv build --no-sources + twine check dist/* — wheel and sdist PASSED
• uv run --locked python scripts/check_distribution.py --dist-dir dist — passed (metadata, license, bundled assets, isolated installs, --help/--version/doctor, uninstall)

Release plan

Merging this PR precedes publication of GitHub Release v0.4.1 on the merged commit, which triggers artifact publication and the protected PyPI deployment in release.yml.

Summary by Sourcery

Prepare the 0.4.1 release by updating version metadata and aligning compatibility logic with the packaged compatibility map.

Enhancements:

• Update the compatibility map and related logic so the latest entry always matches the current package version and tested Kimi Code range is derived from the map.

Build:

• Bump project version to 0.4.1 in pyproject and refresh the uv lockfile for the new release.

Tests:

• Make compatibility tests derive expected bridge versions and tested Kimi Code ranges dynamically from the compatibility map to avoid per-release test edits.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Prepares the 0.4.1 release by bumping the project version, extending the compatibility map, and making compatibility-related tests derive expectations dynamically from the map to avoid future test churn.

File-Level Changes

Change	Details	Files
Make compatibility tests derive expectations from runtime data instead of hardcoded version lists.	Import version into the compatibility tests to assert that the latest compatibility map entry matches the current package version. Relax the compatibility history assertion to only pin the first bridge version and require that the last entry equals the current package version. In main CLI tests, compute the tested kimi-code version range from COMPATIBILITY_MAP using kimi_code_version_sort_key and format the error message with that dynamic range.	tests/test_compatibility.py tests/test_main.py
Update project metadata and compatibility data for the 0.4.1 release.	Bump project version from 0.4.0 to 0.4.1 in pyproject.toml. Append a 0.4.1 entry to the packaged compatibility-map.json reusing the current supported kimi-code versions from the manifest. Refresh uv.lock to reflect the new release version and lockfile state.	pyproject.toml src/kimi_bridge/compatibility-map.json uv.lock

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#29	Create and ship INSTALL_AI.md as a full agent-facing decision-tree setup guide, along with a slim INSTALL.md happy-path guide for humans, restructuring the installation documentation per the external-first policy and traversal contract described in the issue.	❌	This PR only bumps the package version to 0.4.1, updates the compatibility map record, and makes tests derive expectations dynamically. It does not modify or add INSTALL_AI.md, INSTALL.md, or any installation documentation structure. The PR description notes that #31 contains the agent-driven setup guide and closes the issue, but those changes are not part of this diff.
#29	Integrate any supporting code or configuration changes required by the reworked installation flow (e.g., compatibility tooling, doctor behavior) as part of this issue’s implementation.	❌	The code changes here are limited to version bumping and making tests compute expected ranges from COMPATIBILITY_MAP. Any functional changes related to agent-driven setup, doctor behavior, or compatibility commands were done in a prior PR (#31) and are not present in this diff.

Possibly linked issues

• Rework installation docs into an agent-native setup tree (INSTALL_AI.md) #29: The PR implements the INSTALL_AI.md agent-native setup tree and related features that the issue requests.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 31 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c5471900-98cf-4b05-9cfc-f064c32af6a8

📥 Commits

Reviewing files that changed from the base of the PR and between 4268bb4 and 90f32e3.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• pyproject.toml
• src/kimi_bridge/compatibility-map.json
• tests/test_compatibility.py
• tests/test_main.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/0.4.1

---

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

[sourcery-ai]

Hey - I've left some high level feedback:

• In test_compatibility_map_tracks_release_history_and_current_manifest, you now only assert the first and last entries; consider also asserting that bridges is strictly increasing (or matches a sorted copy) to still catch ordering regressions without requiring per-release updates.
• The tested range in test_compat_rejects_an_untested_version_inside_the_tested_range is recomputed in the test; if the CLI has its own logic for computing this range, consider factoring that into a shared helper so the test verifies the same logic rather than an independently reimplemented version.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In `test_compatibility_map_tracks_release_history_and_current_manifest`, you now only assert the first and last entries; consider also asserting that `bridges` is strictly increasing (or matches a sorted copy) to still catch ordering regressions without requiring per-release updates.
- The tested range in `test_compat_rejects_an_untested_version_inside_the_tested_range` is recomputed in the test; if the CLI has its own logic for computing this range, consider factoring that into a shared helper so the test verifies the same logic rather than an independently reimplemented version.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}