Give the telnet window the rest of what N1MM's has

The packet window showed traffic and took a command line, and everything else
about the cluster lived in a dialog under Config. It is now the window N1MM has,
with the same five tabs.

Telnet shows the traffic with spot lines in green, what went out in blue and
lines from a preferred spotter in bold. Double clicking a spot line, or "Jump to
this spot", puts the radio there with the call in the entry window. Scrolling
stops while the pointer is over the traffic. The client keeps the last two
hundred lines, so a window opened mid-contest is not blank.

Clusters keeps the operator's nodes with their ports, passwords and after-login
commands, connects and disconnects, and holds the logon settings. Download
fetches the published list of telnet nodes from NG3K — around fifty, with the
sysop's call and a note about each — and clicking one fills the boxes in. N1MM
downloads its list from its own web service, which asks the operator to opt in
to data collection and is N1MM's to run, so this reads a public page instead.
ClusterList takes any page with telnet:// links in a table; a page it cannot
read leaves the stored list alone.

Filters decide which spots reach the bandmap: bands, modes, beacons, busted
calls, stations outside the call history file, blacklisted spotters and calls,
spots from outside your country, continent or a list of prefixes, and how long a
spot stays on the map. A busted spot is a call the callsign database has never
heard that is one character away from one it knows; a call nothing resembles is
kept, because that is what a new station looks like. Nothing is filtered out of
the traffic itself — the operator sees everything the node sends.

Buttons edits the twelve command buttons. A button takes what N1MM's takes: the
message macros, several commands separated by semicolons, or {CONN} and the name
of a favourite, which connects to that node instead of sending anything. The
label takes the macros too. Right-clicking a button opens the editor.

Config ▸ Cluster now opens this window on the Clusters tab rather than a dialog
of its own, which is where N1MM keeps those settings.

Three things that could take the program down while a cluster was connected:

Settings.Load read a null where the property is not nullable. A file that names
a key with a null value — one written before the property existed and then
edited — put that null straight through, because the property's own default only
runs when the key is missing. Opening the telnet window then threw on the first
list it touched. Every null is now put back to the default the property
declares, walking into the stored records and the lists of them.

Bandmap was written from the cluster's thread and read from the window's, so a
dictionary could be modified while a window enumerated it. Every method locks
now.

ClusterClient disposed its token source while its own loop still used it, and
the retry delay sat outside the catch, so a disconnect faulted the loop task.

Along the way the message macros were checked against N1MM's function-key
documentation, and several were wrong. {LOGGEDCALL} is N1MM's {LASTCALL}, the
serial is #, and there is no {MYZONE}; {NAME} and {GRIDSQUARE} stand for the
other station's name and grid, not ours; {OTHERMHZ} is the radio the operator is
not on. The single-character macros * and ! were missing. Added from the same
table: {LASTCALL}, {PREVNR}, {NAMEANDSPACE}, {CHNAME}, {GRID}, the two grid
bearings and the grid distance, {FREQ}, {FREQROUND}, the other-radio
frequencies, {TIMESTAMP} and {TIME2}. Frequencies are formatted the way N1MM
formats them, with R for the decimal point on CW. The macros that pass a station
to the other band take the second radio as a new argument, and stand for nothing
at a one-radio station.

Left out, and written down: saving spots to a database, which N1MM keeps in its
admin database rather than in the log file the two programs share; the
special-calls list; the two-character busted check, which is a few hundred
thousand lookups per spot against a few hundred for one character; and N1MM's
action macros, which need a different shape than an expander that returns a
string.

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

docs/unfinished.md

@@ -59,6 +59,43 @@ and is listed as a US call now, and China was not split by call area yet. The
 counts a callsign it cannot place — `D1M` — as a multiplier with an empty
 value, and we do not.
 
+**Telnet window: what N1MM has and this does not.** Left out: the special-calls
+list, and saving received spots to a database — N1MM keeps those spots in its
+admin database, which is not the log file the two programs share, so there is
+nothing to be compatible with and nothing asks to read them back. The band plan
+tab is not repeated either, because Config ▸ Sub bands already edits the same
+numbers.
+
+The node list is downloaded from the public NG3K page rather than from N1MM's
+own web service, which asks the operator to opt in to data collection and is
+N1MM's to run. A page that changes shape would stop the download working; the
+reading only needs `telnet://` links in a table, and the old list stays in place
+when a download brings back something unreadable.
+
+**The action macros do nothing.** The text macros are N1MM's, spelled as its
+function-key documentation spells them, and they are listed in the README. What
+is missing is the other half of N1MM's table: the macros that run a program
+command rather than standing for text — `{WIPE}`, `{LOG}`, `{ENTER}`, `{RUN}`,
+`{S&P}`, `{SPOTME}`, `{TOGGLE}`, `{END}`, the `{CAT…}` and `{OTRSP…}` families,
+the audio, rotator and call-stacking macros. They expand to nothing, so a
+message that holds one sends the right characters and takes no action.
+
+They cannot be added to `MessageExpander` as it stands: it turns a template into
+a string, and an action macro has to reach the entry window, the keyer or the
+SO2R box, some of it after the message has been sent (that is what N1MM's
+`{END}` is for). That wants a different shape — a list of steps rather than a
+string.
+
+Two more text macros are out for want of the data behind them: `{LASTEXCH}`,
+which N1MM only fills for ROPOCO and LZ Open, and `{OPERATOR}`, because there is
+no operator separate from the station callsign here. `@`, which voices the
+receive frequency from recorded letter files, waits on voice keying.
+
+**The busted-spot check is one character wide.** N1MM offers two. Every call one
+character away from the spotted one is looked up in the callsign database, which
+is a few hundred lookups per spot; two characters away is a few hundred thousand,
+which is too much work per spot for the little it would add.
+
 **Digital modes.** A contact can be logged as RTTY or another digital mode, and
 the contest rules score it, but there is no digital window: no decoding, no
 transmitting, no interface to fldigi, MMTTY or similar.