fix: stabilize primary ESP-NOW WiFi coexistence

docs/WiFi.md

@@ -256,7 +256,9 @@ distinct from `bridge.channel`, which applies only to the separate ESP-NOW
 bridge feature. WiFi power saving does not let ESP-NOW and infrastructure WiFi
 operate on different channels. On an ESP32 Full build whose primary radio is
 ESP-NOW, `wifi.powersave max` is unavailable because a station using maximum
-modem sleep can miss ESP-NOW broadcasts; use `min` for coexistence.
+modem sleep can miss ESP-NOW broadcasts; use `min` for coexistence. The primary
+mesh transport holds the driver's RF wake reference continuously, so `min`
+does not suspend its ESP-NOW receiver.
 
 ESP-NOW compatibility also depends on the bytes and PHY used above the common
 Espressif transport. The historical `*_repeater_bridge_espnow` firmware wraps

docs/cli_commands.md

@@ -272,7 +272,10 @@ Companion whose primary mesh radio is ESP-NOW, `max` is also unavailable: a
 station using maximum modem sleep can miss ESP-NOW broadcasts, which the access
 point does not buffer for it. A previously saved `max` value is capped to and
 reported as `min`, and a new `max` selection is rejected. These
-WiFi/BLE/primary-ESP-NOW builds therefore use `min`.
+WiFi/BLE/primary-ESP-NOW builds therefore report `min`. The primary mesh radio
+also holds the ESP-IDF WiFi wake reference continuously so unsolicited ESP-NOW
+frames remain receivable; selecting `min` does not put that primary receiver to
+sleep.
 
 #### View or change the primary ESP-NOW/WiFi channel
 
@@ -299,7 +302,8 @@ this node, plus the configured router's 2.4 GHz radio, must use the same fixed
 channel. WiFi power saving does not allow the transports to use different
 channels. On an ESP32 Full build with primary ESP-NOW, `wifi.powersave max` is
 unavailable because maximum modem sleep can miss ESP-NOW broadcasts; use `min`
-for coexistence.
+for coexistence. The firmware keeps the primary ESP-NOW receiver awake while
+still using the `min` WiFi/Bluetooth coexistence policy.
 
 `espnow.channel` is the channel of the primary ESP-NOW mesh transport. It is
 separate from `bridge.channel`, which configures only an ESP-NOW bridge on a

docs/companion_radio_full.md

@@ -70,7 +70,9 @@ backward-compatible default is the distinct wrapped format.
 WiFi power saving cannot put infrastructure WiFi and ESP-NOW on different
 channels. On these two primary-ESP-NOW Full targets, `max` is unavailable
 because maximum modem sleep can make the station miss ESP-NOW broadcasts; use
-`min` for WiFi/BLE/ESP-NOW coexistence.
+`min` for WiFi/BLE/ESP-NOW coexistence. The firmware also holds the ESP-IDF RF
+wake reference for the primary mesh radio, so the ESP-NOW receiver remains
+continuous even though the reported coexistence setting is `min`.
 
 List the available targets: