rtl-ui-auditlisted

# RTL UI Audit Verify the real localized interface, not a blanket `direction: rtl` approximation. Direction, reading order, interaction, mixed content, and visual hierarchy must all remain correct. ## Safety - Read the repository's localization, design-system, and browser-testing instructions before editing. - Preserve language meaning. Do not rewrite copy you cannot confidently review; flag linguistic uncertainty separately from layout defects. - Do not mirror brand marks, media controls, clocks, checkmarks, phone numbers, or other semantically fixed assets without evidence. - Avoid global transforms and broad physical-property rewrites that can regress left-to-right locales. Fix the owning component or token. ## Workflow 1. Launch the real page in the RTL locale and its corresponding LTR locale. Record route, locale mechanism, viewport set, and build identity. 2. Inspect document `lang` and `dir`, framework locale state, DOM order, accessibility tree, focus order, and computed styles. 3. Audit layout with logical properties: inline/block margins, padding, inset, border radii, text alignment, flex/grid order, scroll origin, sticky edges, overlays, and safe areas. 4. Audit content: headings, paragraphs, lists, tables, forms, placeholders, validation, dates, currency, phone numbers, email, URLs, code, filenames, and user-generated mixed-direction strings. Apply bidi isolation such as `bdi`, `dir="auto"`, or Unicode isolation only where semantics require it. 5. Classify ic