/* ============================================================
   Semantic tokens — motion (systems/blog)
   ============================================================

   Intent-named values referencing primitives. THIS is what components code
   against: a token says what a duration is FOR, not how long it is.

   AUTHORED IN #120. The tier did not exist, so `pill` (#116) could not ease
   its hover and shipped without a transition -- recorded in `pill.spec.md`
   rather than hardcoded, because a raw `200ms` is the literal
   `checks/literals.py` rejects.

   ONE ROLE, NOT THREE. `--transition-control` is the only semantic name here
   because it is the only occupant: every animated thing in this system is a
   control changing colour on hover or focus. `base` needs more because it has
   a spinner, a drawer and a modal; this system has none of them.

   That is deliberate, and it is the rule `systems/blog/README.md` states --
   a role exists when a component needs it. Three roles for one occupant would
   be two names nothing reads, which is the shape of token this repository has
   removed before rather than added.

   NAMED `--transition-*` LIKE `base`, not `--duration-*`. `base`'s
   `semantic/theme.css` records why: Tailwind claims the `--duration-*`
   namespace for its own utility lookup, so a `--duration-base` declaration is
   a name Tailwind never reads. This system ships no Tailwind today, and the
   name is kept anyway -- two systems disagreeing about what a duration token
   is called is a cost paid by every person who moves between them.
   ============================================================ */

:root {
  --transition-control: var(--sc-motion-base) var(--sc-motion-ease);
}