Mark

Composes with the classes `Box` computes instead of replacing them.

Which scale the highlight is drawn from — the 200 step fills the background and the 900 step writes the text, which is what keeps the pair readable in any of them. Name the scale only (`"success"`), never a step: `"success.500"` pins BOTH ends to that one step and the text disappears into its own background.

The element it paints. A real `mark` is what tells assistive tech this run is called out, so changing it turns the highlight into decoration the reader never hears about.

Animates the element in when it first scrolls into view. `true` takes the catalogue entrance; an object tunes it — `preset`, `distance`, `spring`, `duration`, `once`, `amount`, `rootMargin` and `index` for a stagger. It lives here rather than on each surface so that `Card`, `Paper`, `GradientBorder`, `Section` and anything else built on `Box` inherit one implementation. Without it `Box` stays a server component; with it the root swaps for a client shell and the children keep rendering on the server. The entrance is a CSS transition, not a JavaScript animation: it is the only motion in the catalogue that fires WHILE the user scrolls, and the compositor should own it.