/* ═══════════════════════════════════════════════════════════════════════════ Sanad UI · the component library — BINDING design/app/README.md § "معايير الواجهة المعتمدة" is the specification; this file is its implementation, and it is the only place these shapes are defined. A new screen is ASSEMBLED from these classes. A new pattern is added here first and then used — never invented inside one screen. With 396 screens the alternative is not untidiness, it is divergence: every developer's own button, and no way to change a rule once. ── Direction ───────────────────────────────────────────────────────────── Every rule uses LOGICAL properties — inline-start/inline-end, margin-inline, border-inline — never left/right. The application runs in Arabic RTL and English LTR from the same stylesheet: setting dir on flips the entire interface, and no rule here has to know which way it is facing. The two exceptions are deliberate and marked: numeric cells force LTR because a negative sign or a currency symbol flips away from its digits in an RTL run, and the Latin-name column does the same for the same reason. ═══════════════════════════════════════════════════════════════════════════ */ /* ───────────────────────────────────────────────────────────────────────── 1 · BUTTONS Every clickable thing is a