v0.13.5

docs/API.md

@@ -1,6 +1,6 @@
 # GREE Controller API reference
 
-HTTP and WebSocket API for GREE Controller **0.13.4**.
+HTTP and WebSocket API for GREE Controller **0.13.5**.
 
 [← Main documentation](../README.md)
 
@@ -231,7 +231,7 @@ Response:
 {
   "status": "ok",
   "name": "gree-controller",
-  "version": "0.13.4",
+  "version": "0.13.5",
   "uptime_seconds": 1234,
   "control_ready": true,
   "time": "2026-08-30T06:54:00Z"
@@ -257,7 +257,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.13.4",
+    "version": "0.13.5",
     "uptime_seconds": 1234,
     "auth_required": false,
     "control_ready": true,
@@ -1465,6 +1465,8 @@ In `0.13.3`, logical thermostat targets use `0.1 °C` precision consistently. Te
 
 In `0.13.4`, disabled-zone thermostat controls remain visually active because explicit temporary/manual thermostat actions are still allowed while zone automation is disabled. The UI shows this distinction directly on the thermostat card; HTTP and WebSocket contracts are unchanged.
 
+In `0.13.5`, the same disabled-zone behavior is explained directly beside the zone enabled/disabled setting, so users see before changing it that disabling a zone stops automation but does not block manual thermostat, temporary thermostat or direct manual control. HTTP and WebSocket contracts remain unchanged.
+
 Additional engine/integration events may be introduced without changing the envelope.
 
 `api.request` data: