protocol 2 fix

Source/NEXT_STEPS.md

@@ -3,8 +3,8 @@
 ## Priority
 
 1. Investigate Protocol 2 stop handling.
-2. Complete Protocol 2 Alex support for boards with `Alex1`.
-3. Continue UI cleanup for Protocol 2 specific hardware presentation.
+2. Validate Protocol 2 wideband behavior on real hardware.
+3. Complete Protocol 2 Alex support for boards with `Alex1`.
 
 ## Immediate Issues To Debug
 
@@ -40,6 +40,21 @@
 
 ## Protocol 2 Functional Work
 
+### Protocol 2 wideband runtime verification
+
+- Re-test Protocol 2 wideband on real hardware after the 2026-04-14 integration.
+- Verify that pressing the UI `Wideband` button now really causes the transceiver to:
+  - start sending wideband UDP data,
+  - stop sending wideband UDP data.
+- Verify that this works while the device is already running, without requiring a full stop/start cycle.
+- Verify the incoming packet format and pacing match what the implementation now assumes:
+  - UDP base port `1027`,
+  - sequence number in bytes `0..3`,
+  - 16-bit raw ADC samples starting at byte `4`,
+  - one full spectrum block formed from `Settings::getWidebandBuffers()` packets.
+- Pay special attention to boards that may not follow the default `32 packets per frame` behavior.
+- If a board reports or requires fixed wideband constraints, use the protocol document/device profile to specialize the current defaults.
+
 - Implement proper `Alex1/BPF2/RX2` handling for boards that support a second Alex register:
   - Orion MkII
   - SATURN / ANAN-G2
@@ -50,6 +65,11 @@
 ## UI Work
 
 - Review UI areas that still assume `Metis/Hermes` semantics internally.
+- Confirm the `Wideband` button behavior is now correct from the user point of view:
+  - button state,
+  - dock visibility,
+  - `widebandData` setting,
+  - real hardware stream enable/disable.
 - Make Protocol 2 model/capability presentation more explicit where useful:
   - selected model,
   - protocol version,