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

docs/architecture/FABRIC_FIRST_TRANSPORT_AND_STRESS_PLAN.md

@@ -258,7 +258,7 @@ Production fabric-core migration boundary:
   QUIC endpoint candidates for the next hop, sends the envelope over the chosen
   QUIC route, and reroutes to warm standby/fallback QUIC candidates on connect
   failure or response timeout.
-- The legacy HTTP production forward carrier has been removed from the mesh
+- The compat HTTP production forward carrier has been removed from the mesh
   runtime API. Production forwarding now exposes a single QUIC transport
   implementation; HTTP handlers remain only as node-local API surfaces and test
   harness entry points.
@@ -287,7 +287,7 @@ Production fabric-core migration boundary:
 - Node-agent discovery now advertises multiple QUIC candidates in one heartbeat
   instead of collapsing to one address: operator/public QUIC, listener QUIC,
   LAN/interface QUIC, STUN reflexive `ice_quic`, reverse/outbound-only, and
-  `relay_quic` fallback. Candidate metadata carries `local_segment_id`,
+  `relay_quic` fallback. Candidate metadata carries `locality_group_id`,
   `nat_group_id`, `stun_server`, `ice_foundation`, `relay_node_id`, and
   `relay_endpoint` when configured. When a relay endpoint is the first physical
   QUIC hop, its advertised certificate fingerprint must survive route planning
@@ -296,23 +296,23 @@ Production fabric-core migration boundary:
 - Endpoint candidate scoring is QUIC-mode only. It ranks `direct_quic`,
   `lan_quic`, `ice_quic`, `reverse_quic`, and `relay_quic` using freshness,
   health observations, latency, reliability, region, policy tags, and live
-  capacity pressure; HTTP/WebSocket labels are treated as rejected legacy
+  capacity pressure; HTTP/WebSocket labels are treated as rejected compat
   candidates rather than alternate transports.
 - `FabricTransportForTarget` no longer accepts a WebSocket carrier. Transport
   selection can return only `QUICFabricTransport`; unsupported labels fail with
   a QUIC-required error.
-- Explicit transport labels are authoritative. A legacy label such as `relay`
+- Explicit transport labels are authoritative. A compat label such as `relay`
   or `outbound_reverse` is rejected even when the endpoint string uses a
   `quic://` scheme; configs must use `relay_quic` and `reverse_quic`.
-- Node-agent config loading rejects legacy advertised transport labels and
+- Node-agent config loading rejects compat advertised transport labels and
   HTTP/WebSocket advertised endpoint schemes for mesh, STUN-reflexive, and relay
   fabric endpoints. Bad endpoint posture fails before heartbeat publication.
-- Host-agent install/runtime validation rejects legacy mesh advertise transport
+- Host-agent install/runtime validation rejects compat mesh advertise transport
   labels and HTTP/WebSocket advertise endpoints before they can be passed into a
   node-agent Docker runtime.
 - JSON-advertised endpoint candidates and scoped synthetic config route
   recovery surfaces are hard-fail QUIC-only: endpoint candidates, recovery
-  seeds, and rendezvous leases reject legacy transport labels and
+  seeds, and rendezvous leases reject compat transport labels and
   HTTP/WebSocket endpoint schemes instead of silently downgrading or dropping
   entries.
 - Rendezvous relay leases and peer-connection intents now use `relay_quic` as
@@ -325,24 +325,24 @@ Production fabric-core migration boundary:
 - Node-agent synthetic runtime no longer installs an HTTP peer transport as an
   inter-node carrier, and the shared mesh runtime package no longer exports an
   HTTP peer transport implementation. Any HTTP synthetic motion is confined to
-  explicit legacy smoke harness code while fabric acceptance uses QUIC loadtest
+  explicit compat smoke harness code while fabric acceptance uses QUIC loadtest
   gates.
 - Control-plane and debug JSON mesh config loading is validated after
   conversion into runtime structures. Peer endpoint candidates, recovery seeds,
   rendezvous leases, and selected relay endpoints in route decisions must use
   QUIC labels/endpoints before they can update node runtime state.
-- Scoped synthetic mesh configs also reject legacy `peer_endpoints` directly,
+- Scoped synthetic mesh configs also reject compat `peer_endpoints` directly,
   in addition to QUIC-only checks for endpoint candidates, recovery seeds, and
   rendezvous leases.
 - The old fabric-session WebSocket endpoint is no longer exposed by
-  `FabricSessionEnabled` alone. It requires an explicit legacy test harness flag
+  `FabricSessionEnabled` alone. It requires an explicit compat test harness flag
   and is not part of the node-agent fabric transport surface.
 - Same local segment or same NAT group is treated as a LAN route by the planner,
   so a whole cluster piece behind one NAT can prefer private addresses between
   its own nodes while still maintaining outbound/relay visibility to the rest
   of the fabric.
 - Heartbeat telemetry includes `fabric_runtime_report` with QUIC-only status,
-  route-set counts, QUIC candidate totals, rejected legacy/non-QUIC candidate
+  route-set counts, QUIC candidate totals, rejected compat/non-QUIC candidate
   totals by transport label, route pressure, QUIC listener state, goroutines,
   heap usage, and the next recommended soak gate.
 - `FabricOverlayTransport` is the generic service-neutral send facade over
@@ -375,7 +375,7 @@ Production fabric-core migration boundary:
   healthy targets are present. A `mixed-public-nat-lan-relay` or
   `nat-lan-relay` run fails if it does not exercise `lan_quic`, `ice_quic`,
   `reverse_quic`, and `relay_quic`.
-- Loadtest verdicts also fail on legacy route-mode labels. Seeing `relay`,
+- Loadtest verdicts also fail on compat route-mode labels. Seeing `relay`,
   `outbound_reverse`, `direct_http`, `direct_https`, `direct_tcp_tls`, `ws`,
   `wss`, or `websocket` in route-mode telemetry is treated as a transport-layer
   violation even if payload delivery succeeds.
@@ -686,7 +686,7 @@ Production fabric-core migration boundary:
   `control_ack_p95_ms=2`, `ack_p95_ms=7`, `channel_leaks=0`,
   `route_pressure.active_total=0`, and matching acquire/release counts.
 - Verified strict QUIC route-mode gate:
-  `fabric-loadtest-20260516-182550` rebuilt the loadtest image with legacy
+  `fabric-loadtest-20260516-182550` rebuilt the loadtest image with compat
   route-mode verdicts and ran the 4-node mixed topology profile. It produced
   400/400 successful logical channels, observed only `lan_quic`, `ice_quic`,
   `reverse_quic`, and `relay_quic`, kept `ack_mismatched_streams=0`,
@@ -816,7 +816,7 @@ Production fabric-core migration boundary:
 - Published and registered node-agent release `0.2.280-fabricsession` with
   linux binary/native and Docker image artifacts. The release is intentionally
   not assigned to live node update policies yet because current live node
-  workload/env posture still advertises legacy `direct_http` and HTTP/HTTPS
+  workload/env posture still advertises compat `direct_http` and HTTP/HTTPS
   mesh endpoints. Before rollout, node configs must be migrated to
   `quic://...` endpoints, QUIC advertise labels, and enabled QUIC listener env
   such as `RAP_MESH_QUIC_FABRIC_ENABLED=true` plus