NOTEPAD: clear what wave 3 closed, record what it left

NOTEPAD.md

@@ -12,6 +12,17 @@ Deferring because out of scope is fine, but don't mention deferring than.
 
 ### To be sorted
 
+- CHORE/DEMO: the demo panel now fills all 17 rows its 2560×1600 canvas holds, every row
+  across all 16 columns. Another tile needs a rearrangement first — worth doing together
+  with re-authoring `PAGES` as a single section.
+- CHORE/TEST: no Playwright coverage for the colour tile — `tests/widgets.spec.ts` covers the
+  other controls. Wants a spec that drags the hue ring and asserts one publish on release.
+- CHORE/UI: the colour wheel's arrow keys move a fixed 5°, with no PageUp/PageDown or
+  Home/End. Fine for picking by eye; a panel that wants an exact hue has no coarse/fine step.
+- CHORE/UI: the colour wheel reads the pointer's angle only, never its distance from the
+  centre (marked `ponytail:` in `ColorWidget.tsx`), so a colour takes two gestures — the ring,
+  then saturation. A saturation-by-radius disc would need a second axis on a control that can
+  announce one value.
 - CHORE/DEMO: `seed_demo.py` still writes the Home dashboard as three titled sections
   ("Right now", "Energy and comfort", "Yield model"). The editor and the panel now read a
   page's sections as one grid, so those headings are no longer drawn and the first editor
@@ -55,8 +66,9 @@ Deferring because out of scope is fine, but don't mention deferring than.
   `# ponytail:` in `api/deps.py`; cache behind the dashboard store's version if it shows
   up in a profile.
 - CHORE/TEST: the frontend has no unit-test runner (Playwright only), so pure helpers like
-  the slider's `tickIntervals` have nowhere to be checked cheaply.
-- FEAT/UX add a color-wheel widget to the dashboard to control the color of e.g. RGB leds; The color picker should be a custom component that integrates smoothly with the existing UI and follow a functional and clean design usable for touch wall panels
+  the slider's `tickIntervals` have nowhere to be checked cheaply. `color.check.ts` is a
+  worked pattern — `bun run` over plain `node:assert`, no framework, imported by nothing so
+  it never bundles. What is left is a make target that runs every `*.check.ts`.
 - FEAT/UI when an installation is added to the hub, the dialog which shows the access code should disappear automatically
 - BUG/UI the "Connect" button in "Remote Access" when adding an installtion to the hub is invisible and only shows upon hovering (could also be a local browser issue)
 - CHORE/PKG the SPA is not in the wheel: `fluksio serve` serves no UI, on the