Two related fixes to TitleBar's new PanLock accessors so all four platforms
compile again:

1. signals: vs. public: — MOC parses anything inside a `signals:` block as
   a signal declaration, so the inline `bool isPanFollowChecked() const`
   and `void setPanFollowChecked(bool)` were rejected at moc time with
   "Not a signal declaration" (TitleBar.h:56). Both methods are accessors,
   not signals — they belong in `public:`.

2. Out-of-line over inline. Even after the section move, the inline
   bodies referenced `m_panFollowBtn->isChecked()` and `QSignalBlocker`,
   which need the full QPushButton type. The header only forward-declares
   QPushButton, so inline bodies couldn't compile in callers either
   (the moc error masked this until now). Moving the definitions to
   TitleBar.cpp keeps the header light and matches the style of
   neighbours like `isSystemMoveAreaAt`.

Build verified locally on Arch Linux x86 — 632/632 clean (only the
pre-existing unrelated macDaxDriverInstalled warning). Same maintainer
fix-up pattern as aethersdr#3279/aethersdr#3286/aethersdr#3289/aethersdr#3381/aethersdr#3398/aethersdr#3417/aethersdr#3439/aethersdr#3441.

Principle XI.

Two related fixes to TitleBar's new PanLock accessors so all four platforms
compile again:

1. signals: vs. public: — MOC parses anything inside a `signals:` block as
   a signal declaration, so the inline `bool isPanFollowChecked() const`
   and `void setPanFollowChecked(bool)` were rejected at moc time with
   "Not a signal declaration" (TitleBar.h:56). Both methods are accessors,
   not signals — they belong in `public:`.

2. Out-of-line over inline. Even after the section move, the inline
   bodies referenced `m_panFollowBtn->isChecked()` and `QSignalBlocker`,
   which need the full QPushButton type. The header only forward-declares
   QPushButton, so inline bodies couldn't compile in callers either
   (the moc error masked this until now). Moving the definitions to
   TitleBar.cpp keeps the header light and matches the style of
   neighbours like `isSystemMoveAreaAt`.

Build verified locally on Arch Linux x86 — 632/632 clean (only the
pre-existing unrelated macDaxDriverInstalled warning). Same maintainer
fix-up pattern as aethersdr#3279/aethersdr#3286/aethersdr#3289/aethersdr#3381/aethersdr#3398/aethersdr#3417/aethersdr#3439/aethersdr#3441.

Principle XI.

## Summary

Three leaks found and fixed during an ASAN session on Linux/RPi5. Total
reduction: 137,879 bytes → 0 bytes leaked on exit. The leaks were not
causing a crash, but were detected while investigating a use-after-free
in `CatPort::stop()` (see PR aethersdr#3414).

- **`SpectrumWidget`**: `prepareForShutdown()` was guarded by `#ifndef
Q_OS_LINUX`, preventing `releaseResources()` from running on Linux
shutdown. Removing the guard eliminates 137 KB of GPU pipeline objects
reported as leaked on exit.

- **`MainWindow` (two fixes in one commit)**: A `pcMicLevelChanged`
signal lambda captured two heap-allocated `float` values via raw pointer
— replaced with `std::make_shared<float>` so they are freed when the
connection is destroyed. Also removed an orphaned `m_radioInfoLabel =
new QLabel("")` allocation that was immediately overwritten four lines
later.

- **`MainWindow`**: `m_connStatusLabel` was created with no parent and
never added to a layout, so Qt never took ownership. Parenting to `this`
also cleans up the `QAccessibleCache` entry created by the first
`setText()` call.

> **Note:** the branch also contains a cherry-pick of the `CatPort` fix
from PR aethersdr#3414, included here only to keep ASAN output clean during
testing. That fix is already tracked in its own PR.

## Test plan

- [ ] Debug/ASAN build on Linux (RPi5 aarch64): `LEAK_SANITIZER:
detected memory leaks` absent on clean exit
- [ ] ASAN baseline before fixes: 137,879 bytes in 245 allocations
- [ ] ASAN after all fixes: 0 bytes leaked from application code

🤖 Generated with [Claude Code](https://claude.ai/claude-code)

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>