…thersdr#3839)

…ethersdr#3839 follow-up)

Follow-up to aethersdr#3839. That change stopped the frequency clipping but drove the
fitted pixel size via QWidget::setFont() — which a QLabel whose stylesheet
names font-family silently discards on every re-polish, so the digits actually
rendered at the ~13px app default ("the frequency is tiny by default"). This
applies the fitted size through the stylesheet as a literal font-size (which
always wins over the cascade), and reorganises the RX Controls panel around it.

- FreqLabelFit.h keeps fitFreqPixelSize(); the size is now applied via the
  label's QSS (literal font-size), with colour/family still resolved from theme
  tokens and the last size cached to avoid a re-polish on every tune step. Each
  freq box is a stable, font-independent width so the fit can't oscillate.
- Hero frequency: its own full-width row at ~34px, with the mode selector and
  the TX/WFM toggles on a compact context strip beneath it. The band and
  filter-bandwidth labels are dropped (the band is obvious from the large
  frequency; bandwidth is already shown by the lit preset button + passband
  graph).
- Volume and AGC are promoted to full-width sliders directly under the mode
  selector; STEP moves into the right control group with balance (pan) and
  squelch. Net top-to-bottom flow: frequency, mode/TX/WFM, volume, AGC, then a
  two-column grid (filter presets + passband | STEP, pan, SQL, RIT, XIT).
- VfoWidget flag: same literal-QSS sizing at the theme nominal.

Proven live on a FLEX-8400M via the agent automation bridge (tune + grab,
before/after, both themes): RX Controls 21.074 MHz shows the full "21.074.000"
at ~34px, 144.2 MHz shows "144.200.000" with no clip, and the VFO flag is
unchanged.

Refs aethersdr#3515, aethersdr#3463 (aethersdr#3839 follow-up).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Reverts #3839.

#3839 landed half-baked. It drove the fitted frequency pixel size via
`QWidget::setFont()`, but a `QLabel` whose stylesheet names
`font-family` makes Qt recompute the font from the QSS on every
re-polish and **discard `setFont()`**, falling back to the ~13px app
default. So the leading digits no longer clip, but the frequency renders
**unreadably small** — the fix is incomplete.

Rather than ship that behavior on `main`, this reverts it. The
**complete** fix is **#3844**:
- the fitted size is applied through the stylesheet as a literal
`font-size` (which always wins over the cascade), so the digits actually
render at the intended size;
- the RX Controls frequency becomes a full-width hero (~34px) with a
reorganized control layout.

Reverts cleanly — no commit since #3839 touched the frequency files.
Build passes.

💻 Generated with Claude Code (Opus 4.8) with architecture by @jensenpat

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

… don't clip

The WFM software-demod toggle lived in RxApplet's `m_freqRow` — the same row as
the large frequency readout — so at narrower applet widths it (with the mode
combo) stole width and clipped the digits. The earlier shrink-to-fit (#3839)
only masked the symptom.

Relocate it to the DAX pan overlay menu, directly below the "IQ Ch" selector —
the natural home, since WFM demodulates that pan's DAX IQ stream on the PC. The
toggle is slice-keyed (acts on the menu's slice) but always reachable (unlike
the FM-mode-gated VFO-flag button), so dropping the always-visible RxApplet
button doesn't cost reachability.

- RxApplet: drop m_wfmButton (creation + member) and the vestigial
  setWfmActive(); keep the mode-combo's wfmActivated(false) teardown so a
  real-mode selection still tears down a running demod.
- SpectrumOverlayMenu: add the WFM toggle below IQ Ch; emit
  wfmToggleRequested(on, sliceId); add a self-gated setWfmActive() reflector.
- MainWindow_Wiring: route the toggle to activateWFM/deactivateWFM with the
  same deactivate guard as the flag button.
- reflectWfmButtons: keep the VFO flag and the DAX-menu toggle in sync.

WFM remains a per-slice singleton; this only changes where the toggle lives.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…gits

The WFM software-demod toggle lived in RxApplet's `m_freqRow` — the same row as
the large frequency readout — so it clipped the digits (#3839's shrink-to-fit
only masked it). A second, FM-mode-gated copy also lived on the VFO flag.

Consolidate to a SINGLE WFM surface in the DAX pan overlay menu, directly below
the "IQ Ch" selector — the natural home, since WFM demodulates that pan's DAX IQ
stream on the PC. WFM runs on raw IQ and is mode-independent, so the menu toggle
is always reachable (the old flag button only appeared in FM modes).

- RxApplet: drop the WFM button + the vestigial setWfmActive(); keep the
  mode-combo wfmActivated(false) teardown.
- VfoWidget: remove the FM-gated WFM button, its setWfmActive() reflector, the
  wfmActivated signal, and the FM-mode gating that showed/tore it down.
- SpectrumOverlayMenu: add the WFM toggle below IQ Ch; emit
  wfmToggleRequested(on, sliceId); add a self-gated setWfmActive() reflector.
- MainWindow_Wiring: route the menu toggle to activateWFM/deactivateWFM.
- reflectWfmButtons: drive the single DAX-menu toggle.

WFM remains a per-slice singleton; this only changes where the toggle lives.
Note: with WFM no longer FM-gated, leaving FM mode on the flag no longer
auto-tears-down the demod (it is raw-IQ, mode-independent); an explicit RxApplet
mode change still tears it down.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>