Rework the dashboard into two looks over one behaviour

A dashboard is a wall panel somebody hangs in their own hallway, so it
now wears what they choose: a look, and a palette of their own colours.

Two complete component sets live under `Dashboard/ui/` — `glass`
(translucent panes over a slowly moving ground) and `material` (Material
3 tonal cards) — behind one prop contract. Every control's state,
keyboard and `aria-` live in `ui/core` and are shared, so the two sets
are the same dashboard drawn twice rather than two products: a set only
decides what a control looks like while doing it.

Four settings join the channel, each drivable by a flow like any other:
`look`, `palette`, `background` and `touch`. A palette is an ordered list
of hex colours — background, surface, primary, accent, text, then more
chart colours — pasted from a coolors.co link or typed, written onto the
canvas as the token variables everything already reads. Trailing roles
are derived, so three colours are a whole dashboard, and derived text is
held to AA rather than trusted (`theme.check.ts` measures it). A palette
also decides light or dark, since its first colour is the ground.

Widgets are measured against their own tile with container queries rather
than against the viewport, animate through `motion`, and can be drawn
without their title. The three reworks:

- a bar draws a row per reading, up to eight, each in the dashboard's own
  data colours and each able to carry its own scale — replacing readings
  nested in one fill, which could only ever share one colour and stop at
  three. Documents written the old way are read as rows.
- a chart's range picker moved to a column down its right-hand edge, which
  gives the plot back a whole row of a short tile.
- the colour wheel became a disc: hue is the angle and saturation the
  distance from the middle, so a colour is one gesture rather than three,
  with brightness on a slider beside it.

`index.css` and `lib/motion.ts` are untouched — the dashboard overrides
token *values* on its canvas, never the blocks the two repos share.
This commit is contained in:
2026-08-23 21:52:14 +02:00
parent d4c5af4d5a
commit 0b5ce4fcbb
52 changed files with 5517 additions and 1568 deletions
@@ -26,7 +26,6 @@ import assert from "node:assert/strict"
import {
CHART_SLOTS,
NO_PALETTE,
paletteOf,
slotsFor,
} from "@/components/Common/UplotChart"
@@ -63,45 +62,26 @@ for (const lines of [0, -3, 1.5, 9, Number.NaN]) {
// --- inertness: a named palette is drawn as written -----------------------
// A dashboard names colours now (`ui/core/theme.ts`), and a chart draws them
// as they were written: not re-spread, not widened, not reordered.
const NAMED = ["#2a9d8f", "#e9c46a"]
assert.deepEqual(
paletteOf(["3", "1"]),
["3", "1"],
"the order picked is the order kept",
)
assert.deepEqual(
slotsFor(2, ["3", "1"]),
["3", "1"],
slotsFor(2, NAMED),
NAMED,
"a named palette is never re-spread",
)
assert.deepEqual(
slotsFor(5, ["3", "1"]),
["3", "1"],
slotsFor(5, NAMED),
NAMED,
"and it is not widened to fit more lines either — the chart cycles",
)
// Repeats are dropped rather than drawn: two lines on one slot could not be
// told apart, which is the whole reason the picker offers each slot once.
assert.deepEqual(paletteOf(["2", "2", "4"]), ["2", "4"], "a repeat is dropped")
assert.deepEqual(paletteOf([1, 2]), ["1", "2"], "numbers name slots too")
assert.deepEqual(paletteOf([...CHART_SLOTS].reverse()), [
"5",
"4",
"3",
"2",
"1",
])
// Naming none, and every shape a broken one arrives in, all mean the same
// thing: no palette, so the chart spreads itself.
for (const stored of [undefined, null, "", [], ["9", "nonsense"], { 0: "1" }]) {
assert.equal(
paletteOf(stored),
NO_PALETTE,
`${JSON.stringify(stored)} names no palette`,
)
// Naming none means the same thing however it is stored: the chart spreads.
for (const stored of [undefined, NO_PALETTE]) {
for (let lines = 1; lines <= CHART_SLOTS.length; lines++) {
assert.deepEqual(
slotsFor(lines, paletteOf(stored)),
slotsFor(lines, stored),
SPREAD[lines],
`${lines} lines still spread`,
)