Make documentation standalone and generalize examples

frontend/src/components/Dashboard/ui/core/motion.ts

@@ -1,10 +1,8 @@
 /**
  * How each look moves.
  *
- * `lib/motion.ts` is the app's own set and is duplicated verbatim in the
- * website repo (`make design-check` holds the two byte-identical), so a
- * dashboard that moves differently needs its own table rather than an entry
- * there. The two looks are meant to *feel* different: material settles quickly
+ * Dashboard motion has its own presets, separate from the app shell's
+ * `lib/motion.ts`. The two looks are meant to *feel* different: material settles quickly
  * and squarely, glass carries a little overshoot.
  *
  * Physics only. What animates is each set's business; this is how it moves

frontend/src/components/Dashboard/ui/core/theme.ts

@@ -10,9 +10,8 @@
  *
  * The result is written onto the canvas as the plain token variables the app
  * already themes with (`--background`, `--card`, `--primary`, …), which is the
- * same mechanism `.theme-light` and `.theme-dark` use on a subtree. Nothing here touches
- * `index.css`: that file's token blocks are byte-identical with the website's
- * and `make design-check` holds them there.
+ * same mechanism `.theme-light` and `.theme-dark` use on a subtree. Palette
+ * overrides leave the app's base tokens in `index.css` unchanged.
  *
  * Every value written out is a literal hex. uPlot draws on a canvas, and a
  * canvas takes neither `color-mix()` nor an unresolved custom property, so a