home-assistant

# Build an automation people can use The deliverable is standard `automations.yaml`, a testable brief and fixture inventory in `project.json`, and a portable installation kit—not a diagram or a preview-only dashboard. Habitat's `index.html` is served by `tools/serve.mjs`; opening it as a static file is insufficient. Start with the desired outcome and constraints. If the user has no devices, use explicitly labeled example entities. If they provide existing YAML, keep a copy and preserve unrelated entries; do not replace their installation configuration. Clarify consequential choices such as manual overrides, thresholds and timeout behavior when needed, but do not require hardware for a device-free project. Read [references/scenarios.md](references/scenarios.md) when creating or changing the test model. Use actual Core triggers, conditions, templates and actions; do not translate them into a homegrown interpreter. Support a new user request with its own entity inventory and meaningful cases. The hallway starter is an editable starting point, not the definition of this harness. Design assertions from the brief before adjusting the implementation. Cover normal operation and important non-firing cases where guards matter; include interruption, bounce, missing sensor or manual takeover when relevant. Assert exact call sequence, target, timing and important final states. A complete suite requires each automation to finish with a service call in at least one case; this is minimum...