v0.16.0

docs/API.md

@@ -1,6 +1,6 @@
 # GREE Controller API reference
 
-HTTP and WebSocket API for GREE Controller **0.15.20**.
+HTTP and WebSocket API for GREE Controller **0.16.0**.
 
 [← Main documentation](../README.md)
 
@@ -243,7 +243,7 @@ Response:
 {
   "status": "ok",
   "name": "gree-controller",
-  "version": "0.15.20",
+  "version": "0.16.0",
   "uptime_seconds": 1234,
   "control_ready": true,
   "time": "2026-08-30T06:54:00Z"
@@ -306,7 +306,7 @@ Returns the initial Web UI snapshot:
   "control_plan": {"generated_at": "2026-09-04T08:00:00Z", "zones": [], "rules": []},
   "control_plan_revision": 42,
   "system": {
-    "version": "0.15.20",
+    "version": "0.16.0",
     "uptime_seconds": 1234,
     "auth_required": false,
     "control_ready": true,

docs/FLOW.md

@@ -14,7 +14,7 @@ Flow is an authoring/orchestration layer. It does not replace the thermostat, sc
 
 ## Existing control domains remain authoritative
 
-- `zone_thermostat` writes the existing persistent Zone intent and wakes the normal thermostat cycle. `power=false` sends an explicit physical OFF to the assigned unit but does **not** change the persistent Zone `enabled` flag; Zone enable/disable remains an administrative control gate. It can also issue one-shot granular vertical/horizontal louver commands to the assigned unit; these auxiliary fields do not take over thermostat ownership.
+- `zone_thermostat` writes the existing persistent Zone intent and wakes the normal thermostat cycle. `power=false` sends an explicit physical OFF to the assigned unit but does **not** change the persistent Zone `enabled` flag; Zone enable/disable remains an administrative control gate. A concrete Flow mode (`heat`/`cool`) is also written with the OFF frame so a stale device `dry`/`fan` mode is not retained; Flow `auto` remains an ownership policy and is never mapped to physical GREE Auto on OFF. While a zone is owned by `automation.flow`, the global outdoor-assist bias is suppressed so the Flow's own room-temperature thresholds remain authoritative. It can also issue one-shot granular vertical/horizontal louver commands to the assigned unit; these auxiliary fields do not take over thermostat ownership.
 - `group_action` calls the existing `control_group` path, including custom group targets.
 - `device_action` uses the existing `DeviceCommand` / automatic-device path.
 - `device_feature_action` uses the same path but compiles exactly one selected `DeviceCommand` field, leaving all other unit settings untouched.

docs/openapi.json

@@ -2,7 +2,7 @@
   "openapi": "3.1.0",
   "info": {
     "title": "GREE Controller API",
-    "version": "0.15.20",
+    "version": "0.16.0",
     "summary": "Local HTTP/WebSocket API for GREE Controller",
     "description": "Local API used by the GREE Controller Web UI and Home Assistant integration.",
     "license": {
@@ -6079,7 +6079,7 @@
           },
           "version": {
             "type": "string",
-            "example": "0.15.20"
+            "example": "0.16.0"
           },
           "uptime_seconds": {
             "type": "integer",