Translation workflow documented

Severity: Recommended

Without a documented workflow, translations become a bottleneck. Developers don't know how to add strings, translators don't know when new strings appear.

Check automatically:

# Look for translation/i18n docs
find . -maxdepth 4 -type f -name "*.md" | xargs grep -l -iE "translation|i18n|localization" 2>/dev/null | head -5

# Check for translation service integration
grep -riE "crowdin|lokalise|phrase|transifex|weblate|poeditor" . --include="*.json" --include="*.yaml" --include="*.yml" --include="*.md" 2>/dev/null | grep -v node_modules | head -5

# Look for CONTRIBUTING or README mentions
grep -iE "translation|translat|i18n|locale" README.md CONTRIBUTING.md docs/*.md 2>/dev/null

Ask user:

• "How do translations get from developers to translators and back?"
• "Is there a translation management system?" (Crowdin, Lokalise, Phrase, etc.)
• "Who can add/modify translations?"

Pass criteria:

• Workflow documented (even lightweight: "add to en.json, PM notifies translators")
• Clear ownership (who coordinates translations)
• Translation service integrated OR manual process documented

Fail criteria:

• No documentation ("ask Sarah, she handles translations")
• Workflow exists in someone's head only
• Developers blocked waiting for unclear process

Evidence to capture:

• Documentation location
• Translation management system (if any)
• Workflow owner

---