Summary
The OpenAI-Compatible provider setup flow — including all predefined templates
(OpenRouter, Together AI, Groq, Cloudflare AI, NVIDIA NIM) and the custom server
path — contains hardcoded English strings that are not covered by the i18n system.
These need to be extracted into locale resource files so they can be translated.
Scope
OpenAiCompatibleTemplate enum
Each template entry has two string fields that are currently hardcoded English:
tagline — one-sentence value proposition shown in the provider picker detail panelhelpText — multi-line setup instructions shown in the CONFIG step info card
All 5 templates are affected:
CLOUDFLARE_AIGROQNVIDIA_NIMOPENROUTERTOGETHER_AI
UI components using these strings
Any composable that renders template.tagline or template.helpText directly
should switch to stringResource(key) calls.
Summary
The OpenAI-Compatible provider setup flow — including all predefined templates
(OpenRouter, Together AI, Groq, Cloudflare AI, NVIDIA NIM) and the custom server
path — contains hardcoded English strings that are not covered by the i18n system.
These need to be extracted into locale resource files so they can be translated.
Scope
OpenAiCompatibleTemplateenumEach template entry has two string fields that are currently hardcoded English:
tagline— one-sentence value proposition shown in the provider picker detail panelhelpText— multi-line setup instructions shown in the CONFIG step info cardAll 5 templates are affected:
CLOUDFLARE_AIGROQNVIDIA_NIMOPENROUTERTOGETHER_AIUI components using these strings
Any composable that renders
template.taglineortemplate.helpTextdirectlyshould switch to
stringResource(key)calls.