# Complete i18n Coverage

## Problem Statement

Several frontend components contain hardcoded English strings that are not internationalized. This breaks the multi-language support for users who prefer Chinese (Traditional) or other locales.

## Affected Components

1. **WeeklyReportPreview.tsx** (~20 hardcoded strings)
   - Report labels, status names, error messages
   - Date formatting uses hardcoded locale

2. **ReportHistory.tsx** (~10 hardcoded strings)
   - History labels, loading states, empty states

3. **AuditPage.tsx** (~30 hardcoded strings in modal)
   - Detail modal labels, verification modal text
   - Field names, status messages

4. **WorkloadPage.tsx** (1 hardcoded error message)

## Proposed Solution

1. Add all missing translation keys to locale files
2. Replace hardcoded strings with `t()` function calls
3. Use dynamic locale for date formatting based on `i18n.language`

## Success Criteria

- All user-visible strings use i18n translation keys
- Both `en/common.json` and `zh-TW/common.json` contain all keys
- Date/time formatting respects user's language preference
- Frontend builds and functions correctly