lsm / HyperNeo / 30559809612

83%

push

github

fix: relabel GLM provider display to Z.ai (#2273)

* fix: relabel GLM provider display to Z.ai

GLM is the model family (GLM-5, GLM-5.2...), not the provider/company
(Zhipu AI, internationally branded Z.ai). The provider was labelled "GLM"
next to models named "GLM-5" — confusing and redundant. This is a
display-only rename; the internal provider id 'glm', model ids, aliases,
family, registry routing, settings.json keys, env vars (GLM_API_KEY /
ZHIPU_API_KEY), stored credentials, and brand color are all unchanged, so
existing sessions/configs keep working with no migration.

User-facing provider labels updated to "Z.ai":
- GlmProvider.displayName (was 'GLM (智谱AI)')
- credential-probe providerName (surfaces in health-check errors)
- buildSdkConfig missing-key error
- credential-discovery BUILT_IN_PROVIDER_ENV_MAP displayName
- useModelSwitcher PROVIDER_LABELS (picker group header)
- AddProviderModal preset displayName (description stays 'Zhipu AI models',
  matching the Kimi -> 'Moonshot AI models' precedent)
- provider-brand KNOWN_PROVIDER_LABELS (trailing-tag stripper)

Model names (GLM-5, GLM-5.1, GLM-5.2, GLM-5-Turbo, GLM-5V-Turbo, GLM-4.7)
are intentionally unchanged — GLM is the model name.

* fix: relabel GLM provider in query-runner auth error to Z.ai

Review feedback on #2273 (P2): the no-auth-configured error in
query-runner.ts listed "Anthropic or GLM" — GLM as a peer of Anthropic
is the provider/company, which should read Z.ai. Missed in the first
pass because query-runner.ts was outside the task's Key files list.

* fix: backfill persisted GLM display_name to Z.ai for existing installs

Review feedback (owner-approved): ProvidersSettings renders the persisted
ProviderRecord.displayName from providers.list, and migrateProvidersIfNeeded
seeds display_name only on an empty table — so an existing install with a glm
row kept showing 'GLM (智谱AI)' in Settings while the picker showed 'Z.ai'.

Add refreshGlmDisplayName(db): an idempotent, display-n... (continued)

11629 of 16737 branches covered (69.48%)

Branch coverage included in aggregate %.

99103 of 117379 relevant lines covered (84.43%)

303.99 hits per line