feat: panadapter spots that read, a CI-V link that survives, no auto-call

Panadapter spots are now worth reading. The comment carries the spotter, the
entity and the status in DXHunter's own shape — "CQ up 2 [F4BPO] [Franz Josef
Land] [New Slot]" — which needed two things nothing documents: SmartSDR splits
its command line on SPACES, so the words ran together until every space became
non-breaking; and it truncates past ~60 characters, so the cluster's own words
are trimmed first and the three brackets always survive. RBN column padding is
collapsed on the way in, or a preserved run of spaces opened a gap wide enough
to push the rest off screen.

"Already worked" means the CALLSIGN is in the log, not the entity: saying it of
a station never contacted was simply wrong. Each status can also be kept off the
panadapter entirely, and the WSJT-X decode spots obey the same switches — the
palette governs the panadapter, not one of the two things that feed it.

And the radio is no longer hammered: a spot whose frequency, colour and comment
are unchanged is not removed and redrawn. A busy skimmer feed re-spots the same
station every few seconds; one two-minute session sent 2128 adds, 88 of them for
a single callsign, and the display did not move a pixel for any of them.

CI-V, from an IC-7850 that kept killing JTDX: a reply the rig sent to another
controller on the same bus is no longer taken for ours, and a set_ptt, set_freq
or set_mode whose acknowledgement goes missing is verified by reading the rig
back instead of being reported as a failure. WSJT-X and JTDX answer a failed
command with a Rig Control Error and drop the link mid-over — 98 keyings, 6 lost
acknowledgements, 2 dropped connections in one session. The check waits 700 ms,
not the poll's 150: the rig has just failed to answer twice because it was
retuning, and a short probe would fail for the same reason.

Auto-call is withdrawn — it duplicated DXHunter, which already answers decodes,
and two programs deciding that from one shack key over each other. The library
is kept whole and dormant; a guard in App.tsx makes sure a stored preference
cannot key a transmitter whose switch no longer exists.

Also:
  - the log rotates while running, not only at startup: the CI-V trace left on
    wrote 416 MB and nothing would have stopped it before the disk did. Closing
    it now releases the crash file too — the runtime keeps its own duplicate.
  - the interface zoom announces itself, with a badge, a click back to 100% and
    a View menu; Ctrl+wheel and Ctrl+0 always worked and nothing said so.
  - no more elastic bounce, and no swipe-to-navigate out of the app.
  - Edit QSO: your own TX power and the contacted station's extended locator
    were saved and written back with no box to set them.
  - FT decodes: continents are a multiple choice; a compound MSHV message that
    answers two stations in one line is recognised as addressed to you.

frontend/src/lib/autocall.ts

@@ -1,5 +1,18 @@
 // Auto-call: let OpsLog answer a decode without the operator clicking it.
 //
+// WITHDRAWN FROM THE INTERFACE, because DXHunter already does it.
+//
+// Two programs from the same shack deciding on their own to answer the same
+// decode is worse than either doing it alone: they cannot see each other, so
+// they key over one another, and afterwards there is no telling which of them
+// called. The duplicate is the one to remove, and DXHunter is where this lives.
+//
+// There is no switch in Preferences and no button on the decodes toolbar, and
+// App.tsx returns before the loop can run. The file is kept whole: the rules
+// below are the delicate part, argued over and tested, and rewriting them from
+// memory later would be worse than leaving them here. Reinstating the feature
+// means restoring all three — the settings page, the button, and the guard.
+//
 // This KEYS THE TRANSMITTER on its own, which is why the rules here are written
 // as a series of refusals rather than a search for a reason to call. Everything
 // below has to be true; anything unknown means no.
@@ -154,9 +167,20 @@ export function shouldAutoCall(
   if (!call) return no('no callsign');
   // Never answer ourselves, however the decode reached us.
   if (opts.myCall && call === opts.myCall.trim().toUpperCase()) return no('own callsign');
-  // Only a CQ. Answering a station mid-QSO is both rude and futile — WSJT-X
-  // actions a Reply only for CQ and QRZ anyway.
-  if (!d.cq) return no('not a CQ');
+  // NOT limited to a CQ, deliberately.
+  //
+  // It used to be, on the reasoning that answering a station mid-QSO is calling
+  // over somebody. That reasoning ignored the case the feature exists for: a
+  // DXpedition running a pileup never sends CQ at all — it works caller after
+  // caller — so the rule sat out the one contact auto-call was turned on for. A
+  // new entity on 15 m FT8, decode after decode, and not a single transmission.
+  //
+  // WHEN to transmit is not ours to decide either: the Reply goes to the
+  // decoder, and MSHV starts at once while JTDX waits for a CQ. Two correct
+  // behaviours, both belonging to the program that owns the timing. Here the
+  // question is only whether the station is one the operator wants — the
+  // criteria below answer that, and the cooldown and the busy check keep it from
+  // calling twice.
   // Not while ANY receiver is mid-QSO — transmitting, or holding a DX call it
   // has not finished with. Starting a second exchange before the first is done
   // is what turned this into a machine that called without stopping.