рабочий вариант, но скороть 10 МБит

docs/architecture/DATA_PLANE_V1.md

@@ -262,7 +262,7 @@ Rules:
 - latest frame wins
 - render must not block input/control
 - binary payloads should be used on direct data plane
-- backend fallback may continue existing JSON/base64 behavior during migration
+- compat fallback may continue existing JSON/base64 behavior during migration
 
 ### `clipboard`
 
@@ -347,7 +347,7 @@ The DP-2 JSON header contains:
 - `session_id`
 - `channel`, currently `render`
 - `message_type`, currently `render.frame.full` or `render.frame.region` on
-  direct worker WSS; `session.frame` remains accepted as the legacy DP-2
+  direct worker WSS; `session.frame` remains accepted as the compat DP-2
   binary message type for compatibility.
 - `sequence`
 - `timestamp`
@@ -950,7 +950,7 @@ explicit direct render message types:
 
 Compatibility:
 
-- Windows client direct transport still accepts legacy binary `message_type=session.frame`.
+- Windows client direct transport still accepts compat binary `message_type=session.frame`.
 - Inside the Windows application pipeline, direct binary frames are normalized
   back into the existing `session.frame` envelope so UI, lifecycle, input,
   clipboard, and file transfer behavior remain unchanged.