(CODUX-226) Translate the Scheduler

[numnx]

🧩 Task: Translate the Scheduler

Automated task PR opened by Code UX for T18.

📋 Summary

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

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 00:52:04 UTC
Finished	2026-07-14 01:05:59 UTC
Duration	13m 55s

📊 Token Usage

Metric	Value
Input tokens	299,756
Cached input tokens	19,842,560
Output tokens	45,044
Total tokens	20,187,360
Invocations	2
Tool calls	129
Active time	35m 6s

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

✅ 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 every Scheduler route workflow and make schedule presentation locale-aware without changing persisted timestamps, recurrence rules, or targets.

## Scope
- Create `dashboard/src/v2/i18n/messages/scheduler.ts`
- Edit `dashboard/src/v2/SchedulerPage.tsx`
- Edit presentation functions in `dashboard/src/v2/lib/scheduler-api.ts` while preserving request/response behavior
- Update `tests/dashboard/v2/scheduler-page.test.tsx` and add focused recurrence, locale-formatting, validation, and accessibility coverage

## Implementation Requirements
1. Translate page headers, calendar/list modes, target choices, recurrence editors, status filters, remediation recommendations, form validation, confirmations, empty/loading/error states, and live announcements.
2. Replace implicit or English date/time formatting with active-locale formatters while preserving selected timezone, ISO persistence, recurrence boundaries, sorting, and daylight-saving behavior.
3. Keep sprint/template/node/thread names, cron/recurrence values, timezone IDs, target payloads, execution messages, and server errors verbatim.
4. Test German one-time and recurring schedules, invalid dates/windows, timezone display, due-run actions, disable/delete, remediation configuration, network failure/retry, realtime refresh, keyboard operation, and mobile layout.

## Constraints
- Do not translate or mutate scheduled chat messages, sprint prompts, template content, node inputs, timezone IDs, or API payload values.
- Do not change scheduler endpoints, recurrence expansion, due-run processing, realtime subscriptions, or idempotency.
- Preserve duplicate-submit suppression and stale-response handling.

## Verification
- Run `pnpm exec vitest run tests/dashboard/v2/scheduler-page.test.tsx` plus new focused Scheduler tests.
- Run `pnpm run lint`.
- Run `pnpm run test:dashboard`.
- Run `pnpm run build`.
- Success means Scheduler copy and formatting follow German locale while persisted schedule semantics remain unchanged.

🌿 Branch Info

Base: feature/CODUX-226-dashboard-internationalization-foundation
Head: task/feature-codux-22-t18-codex-9f8ce8b0-mrjwhx22

---

🤖 Generated by Code UX