# Phase 14: Translation Polish & Testing - Context

**Gathered:** 2026-01-29
**Status:** Ready for planning

<domain>
## Phase Boundary

Complete Polish translations for all new strings added during Vue i18n migration and verify the entire bilingual experience works correctly. This phase ensures 100% translation coverage and validates Polish pluralization, layout integrity, and full user flows.

</domain>

<decisions>
## Implementation Decisions

### Translation review workflow
- Use both automated scan AND runtime logging to identify missing translations
  - Script compares en.json keys against pl.json, outputs diff
  - Run app in Polish, log any fallback-to-English events
- You will review all Polish translations for accuracy
- Present translations in side-by-side markdown file (EN | PL columns)
- Include context hints for ambiguous strings (e.g., "button on quest form")
- Show pluralization with expanded forms: one | few | many | other separately
- Generate all missing translations in one batch (not split by domain)
- You provide corrections inline in the review file, Claude applies to pl.json
- Commit review file to .planning/ as documentation of translation decisions

### Testing approach
- Manual walkthrough testing (no automated E2E)
- Full coverage: every page and modal, including edge cases and error states
- Include visual checks for text overflow/truncation (Polish strings can be longer)
- Track issues in simple markdown list, fix inline during phase

### Pluralization validation
- Unit tests to verify plural rules return correct forms
- Test ALL plural keys (not just a sample)
- Comprehensive test values: 0, 1, 2, 3, 4, 5, 11, 12, 21, 22, 100, 101, 102, 105
- Tests live in vue-queststream-app/tests/ with other Vue tests

### String coverage criteria
- Definition of complete: 100% coverage — every key in en.json must have Polish translation
- Generate coverage report: script outputs X/Y strings translated, lists missing keys
- Zero i18n warnings in console when running in Polish
- Translate everything: placeholders, aria-labels, titles — full accessibility in Polish

### Claude's Discretion
- Coverage report script implementation details
- Test file organization and naming
- Order of testing flows during manual walkthrough
- How to structure the side-by-side review file

</decisions>

<specifics>
## Specific Ideas

- Review file should be easy to edit inline — markdown table format
- Pluralization unit tests should be comprehensive enough to catch edge cases in Polish's 4-form system
- Visual checks important because Polish tends to have longer strings than English

</specifics>

<deferred>
## Deferred Ideas

None — discussion stayed within phase scope

</deferred>

---

*Phase: 14-translation-polish-testing*
*Context gathered: 2026-01-29*