adevwithpurpose ff6d465140 fix(dashboard): remap Kimi Code API-key save to admitted managed id (#10096) ...

The unified Kimi Code card's API-key branch posted provider: "kimi-coding"
to POST /api/providers. "kimi-coding" is an OAuth-primary managed id, not
an admitted API-key/dual-auth connection id, so the backend correctly
rejected it with 400 "Invalid provider" even though key validation passed.

Add resolveApiKeySaveProviderId() in useApiKeySave.ts to remap the posted
provider id to the dedicated, admitted managed API-key id
"kimi-coding-apikey" for the API-key save flow only. The OAuth flow
(handleOAuthSuccess in ProviderDetailPageClient.tsx) never calls this hook
and keeps posting "kimi-coding" unchanged.

Regression test: tests/unit/bug-10096-kimi-coding-apikey-save.test.ts

2026-08-14 18:38:39 -03:00

..

_helpers

…

_setup

…

benchmarks

…

boundary

…

e2e

feat(providers): integrate audited free-tier gateways (#9210)

2026-08-12 16:19:25 -03:00

fixtures

fix(radar): refresh entitlement-sensitive state (#9776)

2026-08-10 20:10:12 -03:00

golden-set

…

helpers

refactor(db): add combo repository boundary (#8757)

2026-08-06 19:11:57 -03:00

homolog

…

integration

feat(codex): add OAuth fingerprint convergence modes (#10243)

2026-08-14 00:57:23 -03:00

live

…

llm-security

…

load

…

manual

…

security

…

snapshots

refactor(providers): remove the Puter provider at its owner's request (#10210)

2026-08-12 16:54:50 -03:00

translator

…

unit

fix(dashboard): remap Kimi Code API-key save to admitted managed id (#10096)

2026-08-14 18:38:39 -03:00

_cp_mock_hook.mts

…

_cp_mock_module.mts

…

_run_dns_guard_test.sh

…

e2e-tool-calls.sh

…

theoldllm-stress.test.ts

…