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.

app.go

@@ -19947,6 +19947,12 @@ func (a *App) SaveChaseSettings(cs ChaseSettings) error {
 	a.clusterStatusMu.Lock()
 	a.clusterStatusIdx = nil
 	a.clusterStatusMu.Unlock()
+	// The frontend caches resolved verdicts and only asks about unknown keys —
+	// without this it kept judging half the screen under the OLD rules until a
+	// restart, which read as the new mode simply not working.
+	if a.ctx != nil {
+		wruntime.EventsEmit(a.ctx, "spotstatus:invalidate")
+	}
 	return nil
 }