Take the rest of what reading N1MM turned up

The call frame. Above the callsign box, N1MM writes which spotted station the
radio is sitting on, coloured like the bandmap colours it, or CQ-Frequency when
this is the frequency the last CQ went out on. Space with an empty callsign box
takes the call out of the frame and into the box, but only while searching:
TabPressed does that when the run box is unchecked, because a running station is
answering callers rather than chasing the one under its VFO. How close counts as
sitting on it is N1MM's tuning tolerance, 300 Hz, now a setting.

Sh/dx while unassisted. TelnetClient.Output refuses any command holding SH/DX
when the entry is not assisted, and the telnet window does the same now.
Whether an entry is assisted follows N1MM's own rule: assisted, multi-operator
or checklog may use spots, a single operator who did not say assisted may not.

The node's flavour. Click_LogonButton reads DXSpider, AR-Cluster, CC Cluster or
GoCluster out of the banner; ClusterClient reads the same words and the window
shows what it found. It changes nothing yet — the commands it would change are
ones this does not send — but the node says so and now we know.

CQ WW RTTY's state box. NextTab only stops on SectionText when the station is
US or Canadian, because nobody else sends a state, so a contest can now say a
box is not for this station and the walk steps over it. The box is still there
to type in.

The telnet button editor shows as many buttons as are defined, with an empty row
to write the next one in, rather than N1MM's twelve.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

README.md

@@ -212,6 +212,17 @@ the other, as N1MM has them. A button puts the radio where you left that band
 and mode, or at the start of that part of the band the first time. The button
 for where the radio is now is marked.
 
+### The call frame
+
+Above the callsign box is N1MM's call frame: it says which spotted station the
+radio is sitting on, coloured the way the bandmap colours it, or `CQ-Frequency`
+when this is the frequency you last called CQ on. While searching, space with an
+empty callsign box takes the station out of the frame and into the box, so a
+spotted station is worked without typing its call. While running it does not,
+because a running station is answering callers rather than chasing the one it is
+sitting on. How close the radio has to be to a spot is `TuningToleranceHertz` in
+`settings.json`, 300 Hz out of the box, which is N1MM's default.
+
 ### Where the other station is
 
 Under the entry window is the line N1MM writes there: the beam heading, the
@@ -485,6 +496,14 @@ its tooltip shows the command behind it. What is typed on the command line goes
 out as typed, again as N1MM sends it. The one place this differs from N1MM: the
 commands of one button go out together rather than a quarter of a second apart.
 
+The window says which cluster program the node runs — DXSpider, AR-Cluster, CC
+Cluster or GoCluster — once the node's banner names it, which is where N1MM
+reads it too.
+
+`sh/dx` is refused while the contest entry is single operator and not assisted,
+with the same message N1MM gives. Asking the node for spots is what an
+unassisted entry may not do.
+
 Three of the filters are worth spelling out:
 
 - **Busted spots.** A spotted call the callsign database has never heard, but