Retain USB packet logging in canonical nRF sensor OTA pairs

docs/cli_commands.md

@@ -1249,7 +1249,15 @@ expected by ordinary USB-to-MQTT parsers.
 
 Ordinary non-OTA artifacts compile packet logging into the canonical image and
 control its live USB output at runtime; no separate `-logging-` artifact is
-emitted. Use the separately named `-ota-` artifact when LoRa OTA is required. A
+emitted. Canonical RAK3401/RAK4631 repeater, room and sensor OTA pairs, plus
+Tower SD repeater and Tower room pairs, also retain packet logging in both
+Full-sensor and Reduced-sensor artifacts. Verbose debug stays off by default;
+`get/set usb.logging` controls packet output. Their capability manifests must
+verify both `logging.usb.packets` and `logging.usb.control` in the packaged
+application. Specialized storage/transport aliases and other space-constrained
+OTA-only targets retain their target-specific logging policy.
+
+For other roles, use the separately named `-ota-` artifact when required. A
 `-full-usb-wifi-ota-` artifact combines USB packet logging, direct WiFi MQTT,
 LoRa OTA, and the expanded FULL feature set. A `-full-logging-ota-` artifact is
 emitted only when that hardware/role has no matching WiFi MQTT environment.

docs/ota_protocol.md

@@ -189,7 +189,13 @@ FULL-capable non-companion hardware/role that has a matching MQTT environment.
 It compiles USB packet logging and direct WiFi MQTT together. A
 `*-full-logging-ota-*` fallback is emitted only when there is no MQTT sibling;
 ordinary non-OTA roles compile runtime USB logging into their canonical image,
-so separate standard-logging artifacts are not emitted. Non-MQTT FULL twins
+so separate standard-logging artifacts are not emitted. Canonical RAK3401/RAK4631
+repeater, room and sensor OTA pairs, and Tower SD repeater/room pairs, retain
+runtime USB packet logging in both sensor variants too. Verbose debug is off
+by default; packaged `logging.usb.packets` and `logging.usb.control` capability
+checks prevent a stale no-logger image from satisfying a resumed build.
+Specialized storage/transport aliases and other constrained OTA targets keep
+their existing logging policy. Non-MQTT FULL twins
 are also skipped for covered ESP32 roles. MQTT observers and ESP-NOW bridges are emitted only with
 expanded FULL partitions. Menu option 8, or `build-full-esp32-firmwares`,
 builds the unified profiles plus necessary fallbacks. Menu option 9, or