2 Commits

Include renames

Author	SHA1	Message	Date
stroblmeandClaude Opus 5	518231aa39	Touch is a panel setting, and the rail grows with it ... It described the wrong object. A dashboard is a document that may hang on a hallway tablet and in a desk browser at the same time, and only one of those has fingers on it — so the flag moves off `DashboardDef.settings` and onto `PanelDef` as a plain bool, ticked in the Panels dialog. `useCanvasRoot` takes it as an argument rather than reading the document, and `/panel/{id}` is the only surface with a panel to ask. Dropping the message binding with it is deliberate: nothing drove it, and a flow deciding whether a screen has fingers on it was never the point. A stored `settings.touch` is inert rather than migrated, which `_check_settings` skipping unknown names already guaranteed. The rail was the other half. It had no touch behaviour at all and its 40px buttons met neither branch of the 44/32 rule. `[data-touch] .dui-rail{-item}` in `ui/core/core.css` spends the padding and the gap on the buttons instead, so they reach the 44px target and the rail comes out taller at exactly the same width — `RAIL_INSET` never moves, and the arrangement under it does not either. Also closes the panels-dialog icon gap: `DashboardSummary` carries the `icon` now, so the dialog draws each assigned dashboard's rail glyph beside its checkbox. `initials()` went from three identical copies in the looks to one in `Dashboard/icons.ts`, so the dialog and the rail fall back the same way. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Va7ExQDtuwKN7kNpHhWWNQ	2026-08-31 19:04:20 +02:00
stroblmeandClaude Opus 5	7600aaf7ea	Guard what a dashboard save does not change ... `PUT /dashboards/{name}` had no backend test: three cover what it promises — a first draft for a name nobody has used (200, not the 404 that came off in 4a2337f), an update that keeps everything the edit did not name, and a save based on a version someone moved past. The Playwright half is the same property through the editor. Pages and sections are gone since 7ff29ca, so what the editor never draws — a widget's md/sm placements and the dashboard-wide settings — is what a save has to carry, and dragging one widget is what the spec makes it carry it through. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K1moruzue2kTJd3uVisgNk	2026-08-28 12:59:08 +02:00