kerfmaster pin list · UI / workflow decisions
recordStates what the code does today. Auditable against the code — this is the only type that can go stale.
Content last changed 2026-09-04 — computed from the item itself, not typed.
Built 2026-09-04. ONE palette by construction: every signal colour was already a CSS variable that both the stylesheet (status dots, finding rows) and the canvas (cssVar) read -- the editor writes overrides as inline style on <body>, so one change recolours dots, findings and canvas alike, on either theme. Overrides are per-STATION presentation state (localStorage km_colors, exactly like theme/units -- per-operator colours arrive with operator accounts, stated on the modal). Per-row reset + reset-all; colour never stands alone (the dot glyphs ✓ ! ✕ stay, taught in the modal and the tour). Three-lens clean: native colour input + CSS variables + localStorage, no platform-divergent API. Fixed on the way: the drag-handle 'clear' green read an undefined --ok variable and always fell to a JS literal -- now reads the palette's --good.
Proven: 9 live Playwright checks over the public URL (menu entry, 9 rows, glyphs, live override -> CSS var flips, survives reload, reset-all restores, storage clean). Web-only change -- served from disk, no restart needed.