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

docs/architecture/DISTRIBUTED_FABRIC_NODE_PROTOCOL_PLAN.md

@@ -24,7 +24,7 @@ policy allows, host limited control/storage roles when approved, and report
 mobile-specific capacity signals such as battery, network type, NAT behavior,
 foreground/background state, and metered network policy.
 
-Node survival and recovery across endpoint moves, NAT-only reachability, legacy
+Node survival and recovery across endpoint moves, NAT-only reachability, compat
 contract overlap, and unavailable manual host access are governed by
 `docs/architecture/FABRIC_NODE_SURVIVAL_AND_RECOVERY_POLICY.md`. In
 particular, nodes like `ifcm-rufms-s-mo1cr` must remain recoverable through the
@@ -179,8 +179,8 @@ Endpoint state is also distributed:
 
 Moving a service must not break the farm.
 
-`RAP_BACKEND_URL` or any fixed HTTP/API address is only a migration fallback for
-old nodes. It is not cluster truth. After bootstrap, a node finds services by
+`RAP_FABRIC_REGISTRY_RECORDS_JSON` and signed registry gossip, not any fixed
+HTTP/API address, define cluster truth. After bootstrap, a node finds services by
 logical role through signed fabric registry records that can be carried by any
 reachable peer.
 
@@ -258,7 +258,7 @@ Service classes that must use this registry before production hardening:
 - `vpn-egress-pool`: user-visible exit pools; users see pools, not backing
   nodes.
 
-Legacy endpoint compatibility is allowed only for rolling migration:
+Compat endpoint compatibility is allowed only for rolling migration:
 
 - Old nodes may use their baked HTTP/control URL only to fetch a new version or
   a signed registry bootstrap record.
@@ -504,7 +504,7 @@ Deliverables:
 
 ### Stage FNP-3: WebSocket/TCP Compatibility Transport
 
-Status: retired as a migration-only stage.
+Status: removed as a migration-only stage.
 
 This stage existed to bootstrap binary frame semantics before QUIC routing and
 carrier reuse were ready. It introduced the transport-neutral frame loop,