Hi @rfoust — thanks for putting this together! Wanted to flag what's happening with the red ❌ before you spend any time digging.

TL;DR — this isn't your code

The only failed check is Cleanup artifacts, and the failing step is Delete artifacts (job log). That's a teardown step in our agent-review workflow that runs after the actual review work is done. The substantive jobs in that run all passed:

• ✅ Prepare
• ✅ Agent
• ✅ Upload results
• ❌ Cleanup artifacts ← gh api call against the artifacts endpoint flaked out

This is a known intermittent on the GitHub artifacts API (rate limit / 5xx from DELETE /actions/artifacts/{id}), not anything in your diff. No action needed on your end — it'll either self-resolve on the next push or a maintainer will rerun it.

Heads up: the real build is still running

The two checks that matter for merge — build and analyze (cpp) — were still in progress at the time of this comment. Worth keeping an eye on those once they finish. The diff is six small defensive if (m_audio) guards around setTransmitting / setRadeMode / setRadioTransmitting calls in MainWindow.cpp (lines ~1966–2014), all in lambdas connected to RadioModel signals. That's the kind of change that almost never breaks compilation, so I'd expect those checks to come back green.

One small note while you're here: each of the three lambdas only changes if m_audio is non-null, so the wider #if defined(Q_OS_MAC) || defined(HAVE_PIPEWIRE) block below the first guard is unaffected — good. If you wanted to tighten this further (totally optional), the three guarded calls in the moxChanged lambda could share a single early-return at the top, but the current shape is perfectly readable and matches the surrounding style.

Thanks again for taking the time on this — these are exactly the kind of crash-prevention guards that pay off when the audio backend hasn't initialized yet on a slow connect path. 🎯

Claude here — really good crash report, Robbie. Walking through the destruction order to nail the QObject auto-disconnect timing was the key insight. The per-call-site guards (including separating the inner RADE guard from the outer) match the file's existing pattern cleanly. Merged.

73, Jeremy KK7GWY & Claude (AI dev partner)