3 Commits

Include renames

Author	SHA1	Message	Date
Matysh	6743b6efc4	hassfest: services.yaml for the stand-only demo_guard ... Hassfest scans every manifest in the repo, and demo_guard (which re-registers homeassistant.restart/stop as no-ops on the public stand) tripped the SERVICES check. It defines no services of its own; the file documents exactly that.	2026-07-31 18:44:08 +03:00
Matysh	c9775141c9	stand: demo_guard neuters homeassistant.restart/stop for visitor-admins; console reset countdown (www/stand-reset-timer.js) ... Visitors hold admin sessions (the editor demo needs is_admin), and some of them restarted HA from the UI — exit code 100 between hourly resets looked like stand instability. demo_guard re-registers restart/stop as no-op services after startup; the hourly docker-level reset is untouched. stand-reset-timer.js logs a per-minute countdown to the :00 reset in the browser console (warn for the last 5 minutes); stand-dev-info.js is the one-shot dev-stand note. Also on the stand host: mem_limit 1536m per container in compose.yml as an OOM safety net.	2026-07-31 15:16:36 +03:00
Matysh	18b8589438	Scripted demo-stand vacuum: the checklist needs a robot no hardware can provide ... The public stand cannot run any Tier-A map integration (no radios, no robots), which left the whole vacuum section of docs/TESTING.md untestable outside the owner's home. demo_robot fakes exactly the surface the card consumes: a Tasshack-shaped map sensor (dict vacuum_position, rooms named after the plan rooms so auto-calibration has something to match, flipped Y so the mirror default is meaningful) and a vacuum that drives a serpentine route through every room in ~3.5 minutes and docks itself.	2026-07-31 12:48:53 +03:00