(CODUX-226) Translate integrations and MCP Settings

[numnx]

🧩 Task: Translate integrations and MCP Settings

Automated task PR opened by Code UX for T08.

📋 Summary

Sprint: Sprint 226 · Dashboard internationalization foundation · Task: T08

Establish a dashboard-only English/German internationalization system with persisted locale selection, complete German coverage across every dashboard route and overlay except English documentation bodies, locale-aware formatting, and automated coverage checks while preserving backend contracts and runtime/API-authored messages verbatim.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-14 05:14:42 UTC
Finished	2026-07-14 05:33:45 UTC
Duration	19m 3s

📊 Token Usage

Metric	Value
Input tokens	1,529,517
Cached input tokens	55,133,952
Output tokens	188,947
Total tokens	56,852,416
Invocations	6
Tool calls	439
Active time	1h 44m 36s

Included usage estimate (subscription/local login): $40.88

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

📝 Full Task Prompt

## Objective
Translate the Integrations and MCP Settings surfaces while preserving credentials, capability checks, terminal output, tool contracts, and security boundaries.

## Scope
- Create `dashboard/src/v2/i18n/messages/settings-integrations.ts`
- Edit `SettingsIntegrationsPanel.tsx` and `SettingsMcpPanel.tsx`
- Edit `dashboard/src/v2/components/settings/ProviderInstanceCard.tsx`, `TerminalLoginModal.tsx`, and `AutomationCredentialManager.tsx`
- Edit presentation helpers in `dashboard/src/v2/lib/chat-provider-view-models.ts`, `provider-lifecycle.ts`, `provider-runtime-preview.ts`, and `dashboard/src/v2/lib/settings/provider-instances.ts`
- Verify but do not translate raw failures from `chat-provider-api.ts`, `local-mcp-api.ts`, `automation-credential-api.ts`, or other client API modules
- Update integration, provider, MCP, terminal-login, automation-credential, and accessibility tests

## Implementation Requirements
1. Translate provider setup descriptions, authentication-mode labels, chat bridge fields, importer controls, connection states, terminal chrome, MCP categories, install/regenerate/copy controls, validation fallbacks, and all accessible feedback.
2. Keep provider/product names, credential field values, secret placeholders, detected paths, endpoints, repository identifiers, tool names, server names, scopes, transport values, terminal streams, and server-returned diagnostics verbatim.
3. Preserve redaction, secure-storage capability checks, two-step removal, focus restoration, pending suppression, local file selection, terminal keyboard handling, clipboard status, MCP installation, and token regeneration behavior.
4. Test German success and validation states plus unavailable secure storage, provider/network failure, terminal failure, clipboard denial, duplicate server names, invalid URLs/transports, and retry/recovery paths.

## Constraints
- Never place credentials, tokens, terminal output, API errors, or secret-derived values into translation interpolation or logs.
- Do not change provider/API/MCP contracts, authentication modes, capability enforcement, or backend routes.
- Do not edit shared Settings shell files or model-routing panels.

## Verification
- Run focused tests for Integrations, provider cards, terminal login, MCP, automation credentials, and chat-provider presentation.
- Run `pnpm run lint`.
- Run `pnpm run test:dashboard`.
- Run `pnpm run build`.
- Success means all dashboard-owned integration chrome is German while secrets, terminal streams, tool identities, and server diagnostics are unchanged.

🌿 Branch Info

Base: feature/CODUX-226-dashboard-internationalization-foundation
Head: task/feature-codux-22-t08-codex-ec76475a-mrjwh9jh

---

🤖 Generated by Code UX