fix(chase): switching the rules invalidates every resolved verdict

The frontend caches statuses and only asks about unknown keys, so flipping
the chase mode left half the screen judged under the old rules until a
restart — which read as the mode not working. The backend now broadcasts an
invalidation and the panels re-ask as rows repaint. The entity badges also
say their name with a question mark, dashed, when the need is only a missing
QSL — the 50% opacity was invisible on a filled chip.

frontend/src/App.tsx

@@ -3862,6 +3862,12 @@ export default function App() {
     // The DX Call was cleared in WSJT-X / JTDX / MSHV → clear our entry to match.
     // Only when something is actually in the entry, so an idle digital app doesn't
     // wipe a call being typed by hand.
+    const unsubStatusInval = EventsOn('spotstatus:invalidate', () => {
+      // The chase rules changed: every resolved verdict is stale. Cleared, and
+      // the flushes re-ask as rows repaint.
+      setSpotStatus({});
+      spotStatusRef.current = {};
+    });
     const unsubClear = EventsOn('udp:clear_call', () => {
       // The decoder cleared its DX Call: the next call it announces — even the
       // same one re-selected — is a fresh edge.
@@ -3925,7 +3931,7 @@ export default function App() {
       const file = String(p?.file ?? '').replace(/^.*[\\/]/, '');
       showToast(file ? t('adifmon.toastFrom', { n, file }) : t('adifmon.toast', { n }));
     });
-    return () => { unsubDX?.(); unsubRC?.(); unsubClear?.(); unsubFlexSpot?.(); unsubTciSpot?.(); unsubProg?.(); unsubBulk?.(); unsubLog?.(); unsubAdifMon?.(); };
+    return () => { unsubDX?.(); unsubRC?.(); unsubClear?.(); unsubStatusInval?.(); unsubFlexSpot?.(); unsubTciSpot?.(); unsubProg?.(); unsubBulk?.(); unsubLog?.(); unsubAdifMon?.(); };
     // eslint-disable-next-line react-hooks/exhaustive-deps
   }, []);