Record successful compact STM32 firmware builds

docs/radio_profiles.md

@@ -1216,6 +1216,8 @@ supported feature names and accepted SPI values (`spi=na` without clock
 control). Settings affect the one
 physical radio and both profiles. They are shared by the same CLI roles as
 `radio2`, including Full Companion, and survive reboot and firmware updates.
+Integrated STM32WL builds omit these controls because their radio interface
+does not support the tuning features.
 
 | Control | Values | Effect when enabled |
 | --- | --- | --- |

docs/test-results/stm32_companion_help_2026-10-23.md

@@ -33,3 +33,20 @@ helper frames total 384 bytes; a 512-byte caller/output reserve keeps that
 local estimate at 896 bytes within the existing 1,024-byte minimum stack
 allowance. This is compiler frame accounting, excluding physical interrupt
 high-water. The complete firmware's linked size is a separate build check.
+
+Complete builds at `5b20bf37` passed sequentially with the Cascade profile and
+unchanged flash boundaries. All four USB Companions also passed the canonical
+OTA packaging and runtime RAM checks:
+
+| Target | Linked flash used / limit | Flash remaining |
+| --- | --- | --- |
+| RAK 3x72 USB Companion | 228,920 / 229,376 bytes | 456 bytes |
+| Wio E5 Mini USB Companion | 228,736 / 229,376 bytes | 640 bytes |
+| Wio E5 USB Companion | 228,716 / 229,376 bytes | 660 bytes |
+| Tiny Relay USB Companion | 228,784 / 229,376 bytes | 592 bytes |
+
+The Wio E5 Mini repeater also passed its cable-only build and runtime RAM
+checks at 245,356 / 245,760 flash bytes, leaving 404 bytes. These integrated
+STM32WL targets expose no supported saved radio-switch tuning features; the
+unavailable machinery is omitted without changing their radio commands or
+stored profiles. These are build checks, not physical device qualification.