lsm / neokai / 27651591059

82%

push

github

feat(providers): add region support to Kimi provider (China vs Global) (#2116)

* feat(providers): add region support to Kimi provider (China vs Global)

Kimi previously hardcoded api.kimi.com (China). Add region-aware endpoint
resolution so users can pick between the China (api.kimi.com) and Global
(api.moonshot.ai) Anthropic-compatible APIs.

- KimiProvider: export KIMI_REGION_ENDPOINTS + resolveKimiRegion(); pick base
  URL from per-session region, then provider-level default region, then
  'china' fallback. Static BASE_URL/OPENAI_BASE_URL retained for backward
  compatibility. Add setDefaultRegion/getDefaultRegion for provider-sync to
  push the configured region onto the instance.
- provider-sync: read region from ProviderRecord.configJson on every sync and
  apply via KimiProvider.setDefaultRegion so existing sessions route to the
  configured endpoint without per-session changes.
- credential-discovery: persisted Kimi rows seeded with configJson
  {region:'china'} so legacy credentials keep their existing behaviour.
- AddProviderModal: region selector visible only on the Kimi card; choice
  persisted into configJson on create.
- ProvidersSettings: region dropdown + Save button on Kimi provider detail
  panels; updates configJson live.
- Tests: region table, resolveKimiRegion defaults, per-session vs
  provider-default precedence, baseUrl override, invalid region fallback,
  separate bridges per region.

* fix(providers): address review on Kimi region UI + parsing

- ProvidersSettings: convert region heading to a real <label for=...> bound
  to the <select id=...> so screen readers announce the field. Matches the
  pattern already used in AddProviderModal.
- ProvidersSettings: disable the region Save button when the staged value
  equals the persisted region, avoiding a needless providers.update + resync
  on no-op clicks.
- kimi-provider: resolveKimiRegion now lowercases incoming region strings so
  hand-crafted payloads using 'CHINA' / 'Global... (continued)

10525 of 15377 branches covered (68.45%)

Branch coverage included in aggregate %.

51 of 76 new or added lines in 5 files covered. (67.11%)

90513 of 108369 relevant lines covered (83.52%)

291.49 hits per line