Add the `BITS` parameter (from `ActivityDetail::bits`) to the
`RX.ACTIVITY` network message, alongside the existing FREQ, DIAL,
OFFSET, SNR, SPEED, TDRIFT, and UTC parameters.
This allows TCP clients to detect frame boundaries — specifically
`JS8CallFirst` (bit 0) and `JS8CallLast` (bit 1) — enabling instant
message finalization without waiting for a timeout-based deadline.
Currently, `RX.DIRECTED` messages already benefit from the `isLast`
check (in `processCommandActivity.cpp`) which appends the EOT character
before sending the network message. However, `RX.ACTIVITY` sends the
network message *before* the `isLast` check, so TCP clients have no way
to know when a message is complete. Adding BITS solves this asymmetry.
Use case: headless JS8Call stations (e.g., Raspberry Pi) using the TCP
API for RX can now display decoded messages with 0s delay instead of
waiting TRPeriod + margin.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
rename remaining files that didn't match their class definitions
relocate the explicit UI_Constructor member function to JS8_MainWindow
relocate the processBufferedActivity member function to JS8_MainWindow
format affected files with LLVM clang-format
Set default APRS inbound relay to off
Fix layout of General->Networking & Autoreply tab in Settings
