5 Commits

Include renames

Author	SHA1	Message	Date
Sergey Matyuninandclaude[bot]	3a88f3ad6c	fix: roll back rejected marker writes atomically ... Issue: #442 User-Visible: yes	2026-09-03 21:42:57 +00:00
Matysh	d5268086c2	fix: harden HA area relocation regressions ... Issue: #126 User-Visible: no	2026-08-31 10:16:46 +03:00
Matysh	112c260314	Release v1.61.0-beta.1	2026-08-09 21:51:33 +03:00
Matysh	854a6944a0	test: align smokes with active registry projection	2026-08-08 15:55:33 +03:00
Matysh	69c5a4c41d	Vacuum first-use path: materialize the marker, count rectangle rooms, fix the toasts ... Audit HP-1540-01 (High): an auto-discovered vacuum has no config marker until the device dialog is saved once, yet the live-position section was already interactive. setVac, _vacSaveMatrix and auto-calibration all did cfg.markers.find(...) and silently bailed out — while the auto-calibration toast still claimed success. Every vacuum edit now materializes a minimal marker (same id/binding the dialog Save would produce), _vacSaveMatrix reports whether the write landed, and success toasts are gated on it. HP-1540-04: the auto-calibration room matcher accepted only polygon rooms and told users their room names did not match. It goes through the shared roomPoly() now, so legacy x/y/w/h rectangles count like everywhere else. HP-1540-06: the no-rooms/no-match/rough-fit toasts pointed at the removed point calibration; they now point at the fit panel that shipped instead, and docs/VACUUM.md Setup UX describes the actual UI. Also extracted vacMapIdFromAttrs as the explicit frontend half of the map-id contract (backend half lands with HP-1540-02). Regressions: demo/smoke_vacuum_firstuse.mjs starts from cfg.markers=[] (the fixture gap the audit called out) with rectangle plan rooms and a zero map_index, and fails 11 checks on the v1.54.0 bundle; i18n unit test asserts no point/точк wording in either language.	2026-07-31 13:07:16 +03:00