docs update, be sync

docs/OTA.md

@@ -1,5 +1,24 @@
 # Over-the-air (OTA) updates — deployment schema **v0**
 
+<!-- doc-meta:start -->
+| Field | Value |
+|---|---|
+| Author | Anton Afanasyeu |
+| Revision | R1 |
+| Creation date | 2026-05-20 |
+| Last modification date | 2026-05-20 |
+| Co-authored |  |
+| Severity | medium |
+| State | in progress |
+| Document type | technical |
+<!-- doc-meta:end -->
+
+\newpage
+\newpage
+
+---
+
+
 The app checks a **stable channel URL**, follows it to a per-build manifest, then downloads the update. Version comparison uses **`major.minor.build`** (packed into Android `versionCode` at build time). Deploy never computes `versionCode` by hand.
 
 The client runs checks and downloads in **`OtaUpdateService`** (a standalone `Service`, not embedded in cast/receiver services). Launch checks enqueue work there; download uses a **foreground service** (`dataSync`) with a progress notification.
@@ -14,6 +33,17 @@ MQTT is fully supported for OTA sources using retained topic payloads (`mqtt://.
 
 ---
 
+---
+
+
+---
+
+
+---
+
+---
+
+
 ---
 
 ## Table of contents