v1.1.3

Runtime monitor guard + GPS baud hardening + GPS_BAUD config

Runtime WiFi adapter safety guard
wifi_feeder now checks before entering monitor mode that the target interface is not your active management interface (same ip route get 1.1.1.1 logic already used by the installer). If it is, the feeder exits with a clear error instead of silently killing SSH.

Additionally, if the adapter is NM-managed but not the backhaul (e.g. after swapping adapters), the feeder now auto-releases it from NetworkManager and persists its MAC to /opt/droneaware/monitor_macs. The NM unmanaged config is updated to include all known monitor adapter MACs — swapping to a previously-used adapter no longer requires a fresh install.

GPS baud rate hardening
detect_baud_rate() now requires 2 consecutive NMEA sentences with valid checksums before accepting a baud rate. Previously a single $GP-prefixed line was enough, which could produce a false positive at 4800 baud on a 9600-baud module (u-blox M9N, etc.).

GPS_BAUD config option
Advanced users can now pin a specific GPS baud rate by setting GPS_BAUD=9600 (or any rate) in /opt/droneaware/config.env. When set, auto-detection is skipped entirely. Leave blank to keep auto-detection.

Run sudo droneaware update to get the fix.