/* ──────────────────────────────────────────────────────────────
   Fix: @planetdds/ui ships Tailwind v3 compiled CSS (dist/styles.css,
   imported globally in src/index.css) whose `.translate-x-*` /
   `.translate-y-*` utilities write `transform: translate(...)`.
   Tailwind v4 defines the same class names but writes the discrete
   `translate` CSS property instead. Both rules match any element
   using one of these classes (library or first-party — the v3 sheet
   is imported app-wide), so the element gets translated twice.

   This file must NOT go through the Tailwind v4 build pipeline: when
   this same override lives in a Tailwind-processed file, the build
   silently drops any rule whose selector matches a class Tailwind
   itself generates (verified — `outline`, `translate: none`, doesn't
   matter what the declaration is, the whole rule disappears from the
   compiled output). Loading this as a separate, untouched stylesheet
   is what makes the fix actually survive the build.

   Loaded via a plain <link> in index.html. Rotate/scale don't have
   this name-collision problem in a Tailwind-processed file, so their
   overrides stay in src/index.css.

   TODO: Remove this file (and its <link> in index.html) once
   @planetdds/ui updates to Tailwind v4 and recompiles its CSS.
   ────────────────────────────────────────────────────────────── */
[class*="translate-x-"],
[class*="translate-y-"] {
  translate: none;
}