harden

<!-- 🔒 LOCKED — managed by clade · auto-generated by sync-to-codex; edit source in .claude/ then re-run sync --> Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs. ## Assess Hardening Needs Identify weaknesses and edge cases: 1. **Test with extreme inputs**: - Very long text (names, descriptions, titles) - Very short text (empty, single character) - Special characters (emoji, RTL text, accents) - Large numbers (millions, billions) - Many items (1000+ list items, 50+ options) - No data (empty states) 2. **Test error scenarios**: - Network failures (offline, slow, timeout) - API errors (400, 401, 403, 404, 500) - Validation errors - Permission errors - Rate limiting - Concurrent operations 3. **Test internationalization**: - Long translations (German is often 30% longer than English) - RTL languages (Arabic, Hebrew) - Character sets (Chinese, Japanese, Korean, emoji) - Date/time formats - Number formats (1,000 vs 1.000) - Currency symbols **CRITICAL**: Designs that only work with perfect data aren't production-ready. Harden against reality. ## Hardening Dimensions Systematically improve resilience: ### Text Overflow & Wrapping **Long text handling**: ```css /* Single line with ellipsis */ .truncate { overflow: hidden; text-overflow: ellipsis; white-space: nowrap; } /* Multi-line with clamp */ .line-clamp { display: ...