simllms 0.1.0__tar.gz

simllms-0.1.0/CHANGELOG.md

@@ -0,0 +1,155 @@
+# Changelog
+
+All notable changes to simllms are documented here. The docs site's
+changelog page is a generated copy of this file — edit this one only.
+
+The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## [Unreleased]
+
+### Added
+
+- **Both packages now describe themselves truthfully on their registry.**
+  `crates/simllms/Cargo.toml` and `crates/simllms-python/pyproject.toml` each
+  declare an explicit `include` whitelist, so a packed artifact holds what it
+  should and nothing else: for the crate, the source tree plus the English
+  README, both license files, the third-party attribution and this changelog;
+  for the Python distribution, those five beside the module the build backend
+  packs by itself.
+- `cargo xtask sync-package` writes the per-package copies of those five files
+  (cargo and maturin both refuse to reference anything above the package
+  directory), and `cargo xtask check-package` proves they match the root
+  originals, that the manifests carry the SPDX license expression, the
+  provider keywords and a provider-agnostic one-sentence description, and —
+  given `cargo package --list` on stdin — that the packed crate holds exactly
+  the whitelist.
+- `crates/simllms-python/tests/test_package_inventory.py` opens the built
+  `.crate`, wheel and sdist and asserts the same inventory from the artifact
+  side: the license files land in the wheel's `*.dist-info/licenses/`, the
+  sdist carries what PEP 639 demands, and no `__pycache__` leaks in. CI packs
+  all three artifacts and names them to those checks, so a run that skipped
+  them cannot report green.
+- Links inside the English README now point at the repository rather than at
+  repository paths. A registry page renders the copy that sits inside the
+  package, where `docs/getting-started.md` and `crates/…/examples/…` are not
+  there to be found — and `cargo xtask check-package` now refuses any carried
+  file that links to something which does not travel with it.
+- **The whole release line runs without publishing anything.**
+  `.github/workflows/release.yml` starts on a version tag or on a hand dispatch
+  whose `dry_run` input defaults to the rehearsal. The pull-request gate's family
+  runs again there; five wheels build from one abi3 extension each (manylinux
+  x86_64 and aarch64 from pinned `manylinux_2_28` images, the latter
+  cross-compiled rather than emulated, macOS x86_64 and arm64 as two separate
+  wheels, Windows amd64); the crate and the sdist come from their own packagers;
+  and only the `publish` job — behind the shared approval environment and an
+  explicit `dry_run` test — reaches a registry. A rehearsal skips it visibly
+  rather than leaving it out of the run.
+- **Publication is one sequential act behind one approval.** The `publish` job
+  exchanges the runner's OpenID Connect identity for a one-shot Cargo token
+  (`rust-lang/crates-io-auth-action`), publishes the crate first, then the
+  wheels and the sdist through the registry's official action, then opens the
+  GitHub Release page. No long-lived registry credential is stored anywhere, no
+  reusable workflow stands in for the publication steps (a reusable workflow
+  cannot be a Trusted Publishing publisher — ADR-0006), and the crate step asks
+  `index.crates.io` whether the number is already there and skips loudly when it
+  is, because the first Release publishes the crate by hand before crates.io's
+  publisher binding can exist.
+- `cargo xtask release-notes <tag>` composes the GitHub Release body from the
+  changelog's dated section and the vendored Catalog Snapshot's own metadata —
+  its date and upstream commit — plus the platform list the matrix owes a wheel
+  to, so the page is read from the repository instead of typed on release day.
+- **The first Release is executed from a runbook, not from memory.**
+  `docs/releasing.md` walks the one-time setup in the order the registries force
+  it (verify the account email, create the approval environment, bind the
+  pending Python publisher, publish the crate once with a short-lived token,
+  revoke it, bind the crate's trusted publisher), then the tag procedure, the
+  Forward Fix policy, yank as human steps only, and the post-release restoration
+  of `[Unreleased]`. `cargo xtask check-workflow` holds the runbook to the
+  workflow: the approval environment is named in both, and the sections are
+  checked to exist in that order. The decisions behind publication are recorded
+  in ADR-0006 (trusted publishing) and ADR-0007 (the Authoritative Version).
+- `cargo xtask check-release <tag>` refuses a tag with a pre-release or build
+  suffix, a tag whose number differs from the Authoritative Version, a tag on a
+  commit that has not landed on `main`, and a version the changelog holds no
+  dated section for — naming the rule that fired each time. `cargo xtask
+  release-tag` answers what tag this commit would become, which is the only
+  question a rehearsal can ask.
+- `cargo xtask check-workflow` reads the release file and holds it to itself: the
+  triggers, the pinned base images, the absence of an emulator, one abi3 wheel
+  per platform, build and publish as separate jobs joined by artifacts, and every
+  gate the pull-request path runs. It also requires the release file to *run* the
+  verdicts that decide a release — `check-release` and `check-artifacts` — and to
+  hand the seam its tag, the wheel it installs, and the name of the environment it
+  installs into, because a deleted step leaves a file that is still well-formed and
+  a rule nobody invokes stops nothing.
+  `cargo xtask check-artifacts <dir> --tag <tag>` compares a built artifact set
+  against the intended platforms, so a missing platform and an unexpected extra
+  both go red.
+- `crates/simllms-python/tests/test_release_artifacts.py` runs against an
+  installed wheel in a venv that never saw the checkout: the reported version is
+  the tag's, the version comes out of the compiled extension, the licenses and
+  the attribution sit where an installer looks, a Gate refusal raises the typed
+  capability error without a network call, and the request debugger renders an
+  outbound body with no credential in it. The release path fails the run if any
+  of those checks skipped.
+
+### Changed
+
+- The crate's whitelist names `src/*.rs` and `examples/*.rs` rather than the two
+  directories. `cargo package` reaches into a listed directory without asking
+  version control, so a bare `src` would publish an ignored neighbour of the
+  sources — a stray `src/__pycache__/` or an editor's backup. `check-package`
+  refuses a directory entry, and the release job plants a marker inside every
+  ignored directory before packing, so the artifact checks prove it stayed out.
+- The Python distribution declares `license = "MIT OR Apache-2.0"` as an SPDX
+  expression with `license-files` (PEP 639, `Metadata-Version: 2.4`) instead
+  of a `License ::` classifier, which PyPI deprecated. The wheels are built
+  with `maturin>=1.9.3`.
+- crates.io accepts five keywords, so the crate carries `llm`,
+  `openai-compatible` and three provider names; PyPI has no such cap and
+  carries all twelve. `check-package` requires the crate's set to be a subset
+  of the Python one.
+
+## [0.1.0] - 2026-10-16
+
+First working release: one request shape, one response shape, and a
+per-model statement of what each model can actually do — checked locally,
+before any network call.
+
+### Added
+
+- **Unified chat client** for DeepSeek, Moonshot (Kimi), Qwen/DashScope,
+  Zhipu (GLM), Xiaomi MiMo, OpenRouter, and any OpenAI-compatible gateway
+  (`Provider::Custom`), as both a Rust crate and a Python package.
+- **Capability Gate**: impossible requests are refused locally with the
+  missing capability named (and, when the catalog knows any, capable models
+  suggested). Unknown model ids warn and pass (ADR-0005).
+- **Capability catalog** vendored from a filtered models.dev snapshot
+  (515 entries), regenerated by `cargo xtask refresh-catalog`; hand-
+  maintained image-generation overrides where providers publish nothing.
+- **`refresh_models()`** (Rust only in this release) consults the provider's own model listing
+  (DeepSeek, Moonshot, DashScope, OpenRouter) and merges it under the
+  precedence user > provider > catalog.
+- **Streaming** (`chat_stream`) normalized into text/reasoning deltas plus
+  a final chunk with finish reason and usage; first-token and idle
+  timeouts; drop cancels the request.
+- **Structured output**, native-only (ADR-0004): the schema reaches the
+  provider as a constrained `response_format`, never as prompt text;
+  refusals surface locally with alternatives.
+- **Image generation** across three provider wire shapes (Zhipu sync URL,
+  OpenRouter sync b64, DashScope submit-then-poll), normalized to a
+  bytes-or-URL result; unsupported parameters are refused with the
+  parameter and model named.
+- **Retries** with exponential backoff and Retry-After support (429/5xx
+  and transport errors only), disabled per client when wanted.
+- **Error layers** (`Capability` / `Config` / `Api` / `Transport`) with the
+  provider's `raw_body` preserved verbatim as evidence.
+- **Python bindings** (pyo3, abi3-py310): `Client` with the same gating and
+  error mapping, `AsyncClient` as an executor-bound thread bridge, sync and
+  async streaming, `generate_image`, `debug_request`, and standard logging
+  under the fixed `"simllms"` logger.
+- **CI**: hermetic PR gate (Rust + Python) with an offline generated-catalog
+  check, and a weekly workflow that opens a reviewable catalog-bump PR —
+  never auto-merged (ADR-0002).
+
+[0.1.0]: https://github.com/SidneyLYZhang/simllms/releases/tag/v0.1.0

simllms-0.1.0/LICENSE-APACHE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

simllms-0.1.0/LICENSE-MIT

@@ -0,0 +1,25 @@
+Copyright (c) 2026 Sidney Zhang
+
+Permission is hereby granted, free of charge, to any
+person obtaining a copy of this software and associated
+documentation files (the "Software"), to deal in the
+Software without restriction, including without
+limitation the rights to use, copy, modify, merge,
+publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software
+is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice
+shall be included in all copies or substantial portions
+of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF
+ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
+TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
+PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
+SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
+IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.

simllms-0.1.0/PKG-INFO

@@ -0,0 +1,95 @@
+Metadata-Version: 2.4
+Name: simllms
+Version: 0.1.0
+Classifier: Programming Language :: Rust
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+License-File: LICENSE-APACHE
+License-File: LICENSE-MIT
+License-File: THIRD-PARTY-NOTICES.md
+Summary: Unified client for multiple LLM providers
+Keywords: llm,openai-compatible,deepseek,moonshot,kimi,qwen,dashscope,zhipu,glm,xiaomi,mimo,openrouter
+License-Expression: MIT OR Apache-2.0
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
+
+# SimLLMs
+
+**One client shape for every major LLM provider — impossible requests are
+refused locally, before you pay for them.**
+
+simllms unifies DeepSeek, Moonshot (Kimi), Qwen/DashScope, Zhipu (GLM),
+Xiaomi MiMo, OpenRouter, and any OpenAI-compatible gateway behind one
+client: one `chat`, one `generate_image`, one streaming shape, and a
+per-model statement of what that model can actually do. The capability
+Gate refuses impossible requests before any network call and tells you
+what is missing — and which models on the same provider can do it.
+
+- 中文文档 / Chinese: [README.md](https://github.com/SidneyLYZhang/simllms/blob/main/README.md)。
+- Full docs: [docs/getting-started.md](https://github.com/SidneyLYZhang/simllms/blob/main/docs/getting-started.md)
+  (also on GitHub Pages once published).
+
+```rust
+let client = Client::new(Provider::DeepSeek, "deepseek-v4-pro", api_key);
+let reply = client.chat(vec![Message::text("你好")]).await?;
+```
+
+```python
+from simllms import Client
+
+client = Client("deepseek", "deepseek-v4-pro", api_key)
+reply = client.chat(["你好"])
+```
+
+## Runnable examples
+
+Every example talks to a local mock service when no credentials are
+present, and to the real provider when the matching API key is set.
+
+| Topic | Rust (`crates/simllms/examples/`) | Python (`crates/simllms-python/examples/`) |
+| --- | --- | --- |
+| Chat | [`deepseek_chat.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/deepseek_chat.rs) | [`chat.py`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms-python/examples/chat.py) |
+| Streaming | [`chat_stream.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/chat_stream.rs) | [`chat_stream.py`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms-python/examples/chat_stream.py) |
+| Structured output | [`structured_output.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/structured_output.rs) | [`structured_output.py`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms-python/examples/structured_output.py) |
+| Image generation | [`generate_image.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/generate_image.rs) | [`generate_image.py`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms-python/examples/generate_image.py) |
+| Custom gateway | [`custom_gateway.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/custom_gateway.rs) | — |
+
+Rust: `cargo run --example deepseek_chat` (same pattern for the rest).
+Python: from `crates/simllms-python/`, run `uv run examples/chat.py`
+(same pattern for the rest).
+
+The examples cover DeepSeek, Moonshot, OpenRouter, and Zhipu; each
+provider's API key is read from its environment variable
+(`DEEPSEEK_API_KEY` etc.), falling back to the local mock when unset.
+
+## Install
+
+```bash
+# Rust
+cargo add simllms
+```
+
+```bash
+# Python
+pip install simllms   # or: uv add simllms
+```
+
+This release does not bind every client entry point on the Python side; the
+list is in the "Rust-only for now" section of
+[docs/getting-started.md](https://github.com/SidneyLYZhang/simllms/blob/main/docs/getting-started.md),
+and Python coverage lands in a later minor release.
+
+Docs: [docs/getting-started.md](https://github.com/SidneyLYZhang/simllms/blob/main/docs/getting-started.md) ·
+topic guides live under `docs/` (chat / streaming / structured-output /
+image-generation / capabilities / custom-gateway).
+
+## License
+
+MIT OR Apache-2.0. The model capability snapshot comes from
+[models.dev](https://models.dev) (MIT), see
+[THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).
+

simllms-0.1.0/README.en.md

@@ -0,0 +1,75 @@
+# SimLLMs
+
+**One client shape for every major LLM provider — impossible requests are
+refused locally, before you pay for them.**
+
+simllms unifies DeepSeek, Moonshot (Kimi), Qwen/DashScope, Zhipu (GLM),
+Xiaomi MiMo, OpenRouter, and any OpenAI-compatible gateway behind one
+client: one `chat`, one `generate_image`, one streaming shape, and a
+per-model statement of what that model can actually do. The capability
+Gate refuses impossible requests before any network call and tells you
+what is missing — and which models on the same provider can do it.
+
+- 中文文档 / Chinese: [README.md](https://github.com/SidneyLYZhang/simllms/blob/main/README.md)。
+- Full docs: [docs/getting-started.md](https://github.com/SidneyLYZhang/simllms/blob/main/docs/getting-started.md)
+  (also on GitHub Pages once published).
+
+```rust
+let client = Client::new(Provider::DeepSeek, "deepseek-v4-pro", api_key);
+let reply = client.chat(vec![Message::text("你好")]).await?;
+```
+
+```python
+from simllms import Client
+
+client = Client("deepseek", "deepseek-v4-pro", api_key)
+reply = client.chat(["你好"])
+```
+
+## Runnable examples
+
+Every example talks to a local mock service when no credentials are
+present, and to the real provider when the matching API key is set.
+
+| Topic | Rust (`crates/simllms/examples/`) | Python (`crates/simllms-python/examples/`) |
+| --- | --- | --- |
+| Chat | [`deepseek_chat.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/deepseek_chat.rs) | [`chat.py`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms-python/examples/chat.py) |
+| Streaming | [`chat_stream.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/chat_stream.rs) | [`chat_stream.py`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms-python/examples/chat_stream.py) |
+| Structured output | [`structured_output.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/structured_output.rs) | [`structured_output.py`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms-python/examples/structured_output.py) |
+| Image generation | [`generate_image.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/generate_image.rs) | [`generate_image.py`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms-python/examples/generate_image.py) |
+| Custom gateway | [`custom_gateway.rs`](https://github.com/SidneyLYZhang/simllms/blob/main/crates/simllms/examples/custom_gateway.rs) | — |
+
+Rust: `cargo run --example deepseek_chat` (same pattern for the rest).
+Python: from `crates/simllms-python/`, run `uv run examples/chat.py`
+(same pattern for the rest).
+
+The examples cover DeepSeek, Moonshot, OpenRouter, and Zhipu; each
+provider's API key is read from its environment variable
+(`DEEPSEEK_API_KEY` etc.), falling back to the local mock when unset.
+
+## Install
+
+```bash
+# Rust
+cargo add simllms
+```
+
+```bash
+# Python
+pip install simllms   # or: uv add simllms
+```
+
+This release does not bind every client entry point on the Python side; the
+list is in the "Rust-only for now" section of
+[docs/getting-started.md](https://github.com/SidneyLYZhang/simllms/blob/main/docs/getting-started.md),
+and Python coverage lands in a later minor release.
+
+Docs: [docs/getting-started.md](https://github.com/SidneyLYZhang/simllms/blob/main/docs/getting-started.md) ·
+topic guides live under `docs/` (chat / streaming / structured-output /
+image-generation / capabilities / custom-gateway).
+
+## License
+
+MIT OR Apache-2.0. The model capability snapshot comes from
+[models.dev](https://models.dev) (MIT), see
+[THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md).

simllms-0.1.0/THIRD-PARTY-NOTICES.md

@@ -0,0 +1,19 @@
+# Third-party notices
+
+## models.dev snapshot
+
+The capability data in `catalog/modelsdev-snapshot.json` and the generated
+file `crates/simllms/src/catalog_data.rs` is derived from
+[models.dev](https://models.dev) ([anomalyco/models.dev](https://github.com/anomalyco/models.dev)),
+copyright the models.dev contributors, licensed under the MIT License.
+The snapshot records its exact upstream commit and date in `meta`.
+Image-generation capability entries are **not** from models.dev; they are
+hand-maintained in this repository.
+
+### MIT License (models.dev)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

simllms-0.1.0/pyproject.toml

@@ -0,0 +1,65 @@
+[build-system]
+# 1.9.3 is the first release that carries PEP 639 license files into a source
+# distribution, which is what the two settings below ask for.
+requires = ["maturin>=1.9.3,<2"]
+build-backend = "maturin"
+
+[project]
+name = "simllms"
+# The Authoritative Version is the root workspace manifest; this copy derives
+# through the binding crate's Cargo.toml, which the build backend reads.
+dynamic = ["version"]
+description = "Unified client for multiple LLM providers"
+requires-python = ">=3.10"
+# PEP 639: an SPDX expression for the license, and the files themselves listed
+# so they reach an installed distribution under `*.dist-info/licenses/`. The
+# deprecated `license = { text = … }` table carried the words and nothing else.
+license = "MIT OR Apache-2.0"
+license-files = ["LICENSE-APACHE", "LICENSE-MIT", "THIRD-PARTY-NOTICES.md"]
+# Registry pages render this file; the repository's default README is Chinese.
+readme = "README.en.md"
+# PyPI has no keyword ceiling, so this side names every provider; the crate is
+# capped at five and picks the ones people search for.
+keywords = [
+    "llm",
+    "openai-compatible",
+    "deepseek",
+    "moonshot",
+    "kimi",
+    "qwen",
+    "dashscope",
+    "zhipu",
+    "glm",
+    "xiaomi",
+    "mimo",
+    "openrouter",
+]
+classifiers = [
+    "Programming Language :: Rust",
+    "Programming Language :: Python :: Implementation :: CPython",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+]
+
+[tool.maturin]
+module-name = "simllms._core"
+bindings = "pyo3"
+# The wheel is told about the licenses through `license-files` and about the
+# README through `readme`, so only the source distribution needs them listed as
+# files. Each path is a copy that `cargo xtask sync-package` writes: PEP 639
+# forbids `..` here, so a root-level file cannot travel by reference.
+include = [
+    { path = "CHANGELOG.md", format = "sdist" },
+    { path = "LICENSE-APACHE", format = "sdist" },
+    { path = "LICENSE-MIT", format = "sdist" },
+    { path = "README.en.md", format = "sdist" },
+    { path = "THIRD-PARTY-NOTICES.md", format = "sdist" },
+]
+# Byte-compiled files from whoever built the wheel have no business travelling
+# inside it; the wheel is the installed package, not a working directory.
+exclude = ["**/__pycache__/**", "**/*.pyc"]
+manifest-path = "simllms-python/Cargo.toml"
+python-source = "python"