feat: kimi (Moonshot AI) built-in provider (ADR-0026)
Add a first-class `kimi` provider and `kimi://` DSN scheme for Moonshot AI's OpenAI-compatible Chat Completions API. Both reuse provider/openai (no new client, mirroring llama-swap's chat path). Default endpoint is the international host; the China endpoint is reachable via a kimi:// LLM_* DSN. - Credential is KIMI_API_KEY, read through the registry's injected envLookup so it stays hermetically testable. WithAPIKey is passed unconditionally so an unset KIMI_API_KEY can never fall through to the openai client's OPENAI_API_KEY default. - New openai.WithAPIKeyName option customizes the missing-key error hint (default OPENAI_API_KEY); kimi names KIMI_API_KEY. - Hermetic tests: built-in base URL + bearer, missing-key hint names KIMI_API_KEY with no OPENAI fallthrough and no network hit, kimi:// scheme round-trips against the China host. - Docs in sync: README built-in table + DSN scheme list + support matrix, .env.example, env.go DSN doc, ADR-0026 (+ index, backfilling 0024/0025), progress.md. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
This commit is contained in:
+21
@@ -264,3 +264,24 @@ tests flush out.
|
||||
cheap `Health(ctx)` probe (GET /health) for often-offline hosts.
|
||||
- Hermetic httptest coverage for every new wire shape + validation errors.
|
||||
- Consumer: mort's llamaswap media tool cluster (status/image/TTS/STT tools).
|
||||
|
||||
## 2026-07-18 — Kimi (Moonshot AI) built-in provider (ADR-0026)
|
||||
|
||||
- New built-in `kimi` provider + `kimi://` DSN scheme: Moonshot's
|
||||
OpenAI-compatible Chat Completions endpoint, so both reuse `provider/openai`
|
||||
(no new client, mirrors llama-swap's chat path). Default base URL
|
||||
`https://api.moonshot.ai/v1`; China endpoint via
|
||||
`LLM_KCN=kimi://[email protected]/v1`.
|
||||
- Credential is `KIMI_API_KEY` (read through the registry's injected envLookup,
|
||||
so it's hermetically testable). `WithAPIKey` is passed unconditionally so an
|
||||
unset `KIMI_API_KEY` can never fall through to the openai client's
|
||||
`OPENAI_API_KEY` default.
|
||||
- New `openai.WithAPIKeyName` option customizes the missing-key error hint
|
||||
(default `OPENAI_API_KEY`); the kimi built-in/scheme name `KIMI_API_KEY`.
|
||||
- Hermetic tests (capturing RoundTripper): built-in base URL + bearer, missing
|
||||
key names KIMI_API_KEY with no OPENAI fallthrough and no network hit, and the
|
||||
kimi:// scheme round-trips against the China host.
|
||||
- Docs kept in sync: README built-in table + DSN scheme list + support matrix
|
||||
(footnote ³), `.env.example`, ADR-0026 (+ index; also backfilled the missing
|
||||
0024/0025 index rows).
|
||||
- Consumer: mort names Kimi as a failover tier.
|
||||
|
||||
Reference in New Issue
Block a user