feat: add Kimi K3 API support - #20
Merged
Merged
Conversation
brainx
marked this pull request as ready for review
July 31, 2026 20:05
brainx
added a commit
that referenced
this pull request
Jul 31, 2026
## Summary - set the package and OpenAPI versions to `0.5.0` - move the current unreleased changes, including Kimi K3 support from #20, into the `0.5.0` changelog section - document the compatibility-preserving internal module decomposition and 1,200-line production-module size ratchet - identify `v0.5.0` as the latest stable release in the roadmap ## Impact Relative to current `main`, this PR changes release metadata and hardens two rate-limit test assertions against threaded access-log ordering. Runtime Kimi K3 support is already present through #20; this PR does not change runtime code, public behavior, API/schema migration, lifecycle ordering, or Hermes compatibility. ## Release safety The release tag must be created only after this PR is squash-merged through GitHub and must target that GitHub-verified commit on `main`. The unsigned topic-branch commits are not valid tag targets. GitHub's immediately preceding squash merge for #20 was independently confirmed as `verified: true` with verification reason `valid`. ## Verification - `.venv/bin/python scripts/check_version_tag.py v0.5.0 --require-changelog` — passed - `make release-check` in the repository development environment — passed - 1,137 tests passed in the normal run with 3 expected skips - 1,137 tests passed under branch coverage with 3 expected skips - 82.44% branch coverage - repository readiness, Ruff formatting and lint, MyPy, Bandit, ShellCheck, dependency validation, package build, installed-wheel smoke, Twine validation, and checksum generation passed - Python 3.14 focused rate-limit audit assertions — 40 repeated executions passed - Ruff format/lint on `tests/test_api.py` — passed - `git diff --check` — passed - Hosted CI run `30662495244` — all Python 3.11, 3.12, 3.13, and 3.14 tests, package, real-Hermes, macOS lifecycle, and subprocess jobs passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
zeus audit initconfiguration using Kimi K3Impact
Zeus users can create Kimi K3-backed Hermes profiles and explicitly initialize repository audits with Kimi K3 while keeping credential values outside the generated configuration. Existing providers and uninitialized audits retain their current behavior.
Verification
make check: 1,137 tests passed with 3 skips in both normal and coverage runs; repository readiness, Ruff, mypy, Bandit, and shellcheck passedManual boundary
No paid live Kimi request was made.