fix: RNode TX flow control, chat unread focus, Reticulum polish

docs/reticulum.md

@@ -194,6 +194,7 @@ Config lives under `userData/reticulum/config/` (rnsd INI). The Connection tab s
 
 - **All:** display name; optional rnsd **mode** (`full`, `gateway`, `access_point`, `roaming`, `boundary`, `point_to_point` — shorthands `gw` / `ap` accepted). Defaults when omitted on add: TCP/UDP/I2P → `boundary`; RNode / RNode Multi → `access_point`; **Auto, BLE Peer, KISS, Pipe** leave mode unset (RNS default `full`). Hubs usually use **Boundary**; RNodes usually use **Access point**. On edit, clearing mode omits it from config (RNS `full`).
 - **IFAC (all types):** optional `network_name` and `passphrase` for private/authenticated network segments ([common interface options](https://reticulum.network/manual/interfaces.html#common-interface-options)). Shown on add and edit; passphrase uses a masked input with show/hide.
+- **Flow control (RF only — RNode / RNode Multi / KISS, covering USB, `ble://`, and `tcp://` RNode ports):** typed `flow_control` checkbox. **Defaults on** for RF interfaces so bursts wait for the device `CMD_READY` ready-gate instead of overflowing the bounded TX queue (drops as `PACKET DROPPED: interface TX channel full`). Not shown for TCP/UDP/I2P/Auto/BLE Peer (key omitted). Existing RF interfaces missing the key are repaired to `Yes` once on sidecar bootstrap; an explicit `No` is preserved. Changing it requires a stack restart. No longer needs the Advanced editor.
 - **Advanced (edit only):** free-form `key = value` lines for other common options (e.g. `forward_interval`, `ifac_size`, I2P SAM host/port below). Keys that duplicate typed form fields are ignored. Unknown INI keys are preserved across enable/edit/repair via sidecar `extra_config` (no longer silently dropped).
 - **TCP client:** host, port (mesh hub — default port **4242**); IPv6 literals use brackets: `[2001:db8::1]:4242`
 - **I2P:** comma-separated peer hostnames (`.b32.i2p` addresses, e.g. `{52-base32-chars}.b32.i2p`); max **512** characters total; validated in UI and sidecar before write. The typed **Host** field is the hub **peers** list, not the SAM bridge. By default the stack talks to a **SAM application bridge** on **`127.0.0.1:7656`** on the machine running mesh-client (not HTTP/HTTPS I2PTunnel proxies on `4444`/`4445`). **Restart I2P after enabling SAM** so the bridge listens, then enable the interface and restart the Reticulum stack if it stays down. RMAP publish on I2P sets `connectable=yes` (inbound); hub `peers` are dialed as clients as well (Python RNS parity).

reticulum-sidecar/src/stack/auto_path_policy.rs

@@ -302,6 +302,7 @@ mod tests {
             reachable_on,
             network_name: None,
             passphrase: None,
+            flow_control: None,
             extra_config: HashMap::default(),
         }
     }