v0.13.1

docs/API.md

@@ -1,6 +1,6 @@
 # GREE Controller API reference
 
-HTTP and WebSocket API for GREE Controller **0.13.0**.
+HTTP and WebSocket API for GREE Controller **0.13.1**.
 
 [← Main documentation](../README.md)
 
@@ -231,7 +231,7 @@ Response:
 {
   "status": "ok",
   "name": "gree-controller",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "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.0",
+    "version": "0.13.1",
     "uptime_seconds": 1234,
     "auth_required": false,
     "control_ready": true,
@@ -1450,6 +1450,8 @@ log.created
 
 `control_plan.updated` uses `data.revision` plus `data.plan`. Revisions increase only when the materialized plan changes semantically; `generated_at` alone does not create a new revision.
 
+`zone.updated` keeps the existing full-zone payload. Regulator passes that only advance the internal `updated_at` heartbeat are deduplicated and do not emit a frame; any actual zone state/sensor/control change still emits the full snapshot. Device polling keeps `device.updated` heartbeats for live `last_seen` UI, but heartbeat-only fields do not invalidate `control-plan`.
+
 Additional engine/integration events may be introduced without changing the envelope.
 
 `api.request` data: