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

docs/architecture/MESH_ROUTING_RUNTIME_IMPLEMENTATION_PLAN.md

@@ -604,14 +604,14 @@ experiment while preserving the production forwarding kill-switch. This result
 is retained only as test-history context; it is not the active transport
 direction for the fabric runtime:
 
-- `HTTPPeerTransport` maps explicit peer node IDs to synthetic HTTP endpoint
+- `QUICPeerTransport` maps explicit peer node IDs to synthetic QUIC endpoint
   URLs.
-- `rap-node-agent` can start a synthetic `/mesh/v1/*` endpoint only when
-  `RAP_MESH_SYNTHETIC_RUNTIME_ENABLED=true` and `RAP_MESH_LISTEN_ADDR` is set.
+- `rap-node-agent` can start the synthetic fabric runtime only when
+  `RAP_FABRIC_RUNTIME_ENABLED=true` and `RAP_FABRIC_LISTEN_ADDR` is set.
 - peer endpoints and synthetic routes can be injected as JSON for smoke/debug
   only.
 - `mesh-live-smoke` proves direct and single-relay synthetic traffic over real
-  local HTTP endpoints.
+  local QUIC endpoints.
 - bounded `synthetic.echo` remains the only test-service payload.
 - `/mesh/v1/forward` remains disabled.
 - no production service traffic is authorized.