v0.16.4

docs/FLOW.md

@@ -22,6 +22,12 @@ Flow is an authoring/orchestration layer. It does not replace the thermostat, sc
 - Thermostat hysteresis, compressor protection, schedule hand-back, manual/local ownership and Temporary Quick Thermostat keep their existing priority.
 - GREE fan/quiet/sleep and dry/fan HVAC modes are suppressed on thermostat-assigned devices when they would fight the regulator. Device-only features such as light/turbo/louver/air/xfan/health remain available through the normal command path.
 
+## Wyłączanie Flow / Disabling Flow (0.16.4)
+
+`Flow.enabled=false` and `draft=true` are authoritative: generated automations and schedules do not execute, create deadlines or contribute to the control plan even if a legacy/imported child record still says `enabled=true`. Runtime-only Flow checkpoints cannot overwrite `enabled`, resurrect deleted rules or persist across a Flow recompile. Actions recheck both their own enabled state and the parent Flow under the automation execution lock.
+
+Disabling, deleting or replacing a thermostat Flow releases zone-level thermostat intent attributed to that Flow (including stale manual setpoints and pending compressor actions) immediately during the Flow edit, with a regulator-cycle fallback for old/imported data. Manual/local takeover is never cleared. Single-shot device/group/HA commands that have already reached an external device/service are not retroactively undone; disable blocks **future executions**. Stateful timing counters, change-event latches, rolling samples and cooldowns start fresh when the Flow is enabled again; disabled time is not counted.
+
 ## Concurrency invariants
 
 Structural Flow writes use the global order: