feat(providers): refresh NVIDIA hosted models (#12538)

Validado em lote numa worktree combinada com #12524, #12538, #12277 e #12367 sobre o tip de release/v3.8.51: os quatro boardaram sem conflito (áreas disjuntas — zai-web, nvidia, clova, cursor/devin/fable). typecheck:core limpo, check:provider-consistency OK (272 entradas REGISTRY, 355 providers canônicos), check:known-symbols OK, e 305/305 nos testes tocados pelos quatro PRs. Os IDs de modelo adicionados foram conferidos individualmente. Obrigado, @backryun.
This commit is contained in:
backryun
2026-09-03 19:50:02 +09:00
committed by GitHub
parent 032adb0809
commit cdd07df700
21 changed files with 156 additions and 325 deletions

View File

@@ -9,11 +9,12 @@
* probe HANG until the validation timeout, which surfaces as a misleading "Upstream
* Error" on an otherwise-valid key.
*
* `meta/llama-3.1-8b-instruct` is a long-lived, universally-available NIM model (no
* special permission), so it is a far more reliable auth probe. A connection may still
* override it via `providerSpecificData.validationModelId`.
* The default must stay inside the current NVIDIA hosted-model catalog. Nemotron 3.5
* Lightning is the smallest retained general chat model, which keeps the auth probe
* lightweight. A connection may still override it via
* `providerSpecificData.validationModelId`.
*/
export const NVIDIA_DEFAULT_VALIDATION_MODEL = "meta/llama-3.1-8b-instruct";
export const NVIDIA_DEFAULT_VALIDATION_MODEL = "nvidia/nemotron-3.5-lightning-30b-a3b";
export function resolveNvidiaValidationModel(providerSpecificData?: {
validationModelId?: unknown;