Keep classic ESP32 release profiles within their measured RAM budgets

docs/companion_offline_queue.md

@@ -15,13 +15,13 @@ A reboot clears it.
 | RP2040 | 256 |
 | STM32 | 16 |
 | Known constrained classic ESP32 target override | 128 |
-| Meshadventurer Full Companion | 64 |
+| Meshadventurer Full Companion | 16 |
 | Constrained Full ESP32 fallback | 16 |
 
 An explicit target `OFFLINE_QUEUE_SIZE` overrides the platform default. The
 Heltec V2 and TLora V2 Full Companion profiles, for example, use 16 frames so
 their combined WiFi, BLE, and LoRa mOTA image retains enough internal DRAM.
-Meshadventurer SX1262 and SX1268 Full Companion use 64 frames together with 160
+Meshadventurer SX1262 and SX1268 Full Companion use 16 frames together with 100
 contacts and 30 group channels; their ordinary transport-specific images keep
 128 frames and 40 channels.
 

docs/companion_radio_full.md

@@ -314,9 +314,9 @@ partition layout. Other boards with 8 MB or more retain dual application
 partitions.
 Heltec V2 and TLora V2 use 100 contacts, 8 group channels, and a 16-frame offline
 queue in this combined profile because of internal DRAM limits. Meshadventurer
-SX1262 and SX1268 retain 160 contacts, use 30 group channels, and use a
-64-frame queue. That is the smallest measured reduction which cleared their
-classic ESP32 internal-DRAM link limit; their ordinary transport-specific
+SX1262 and SX1268 use 100 contacts, 30 group channels, and a 16-frame queue.
+These capacities preserve the required 8 KiB static internal-DRAM reserve
+alongside MOTA and all Full transports; their ordinary transport-specific
 images retain 160 contacts, 40 channels, and 128 queued frames.
 
 Full Companions normally retain 256 pending Companion message frames. ESP32

docs/full_companion_features.md

@@ -161,3 +161,8 @@ and the board's matching BLE-DFU-capable bootloader/SoftDevice. USB remains
 the fallback when the installed bootloader does not support that procedure.
 Bluetooth DFU updates the Companion; the separate Bluetooth MOTA source
 service feeds packages to other mesh nodes.
+
+For OTAFIX installations, use the exact board/storage profile from
+[OTAFIX 2.4.5](https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.5).
+Its release notes cover the Bluetooth reconnect fix and upgrades from older
+bootloaders, including the special UF2-drive precautions for version 2.4.3.

docs/releases/1.17.1.5.md

@@ -31,6 +31,15 @@ application slots and OTA metadata; nRF52 Bluetooth qualification checks the
 linked DFU service and its application ZIP. LoRa installation on nRF52 still
 requires the exact matching OTAFIX bootloader and storage arrangement.
 
+Classic ESP32 capacity limits are recorded in each artifact's capability
+manifest. Generic E22, Heltec V2, Meshadventurer, and T-Beam OTA repeaters,
+plus the TLora MQTT repeater, use 50 neighbors where needed to preserve the
+required internal RAM reserve.
+T-Beam MQTT repeater profiles retain the full rule engine with 31 flood rules;
+constrained classic ESP32 ESP-NOW bridges with logging use 47.
+Meshadventurer Full uses 100 contacts, 30 group channels, and a 16-frame
+offline queue while retaining its MOTA and transport features.
+
 Since 1.17.1.4, this branch also includes USB session and contact-persistence
 fixes, automatic nRF52 ExtraFS recovery, improved Indicator setup/display
 handling, compressed MOTA transport, and measured ESP32 memory limits.
@@ -62,3 +71,5 @@ the matrix unsuccessful and must be resolved before publication.
 `--allow-no-ota` is an explicit development override for cable-only
 infrastructure. Those outputs do not belong in this OTA-required release.
 Use a separate output directory when changing the radio or settings profile.
+Use a fresh release output directory after changing the source revision or
+firmware version so packaging cannot mix old and new binaries.