Fill in the rest of N1MM's network status window

Seven tabs now, in N1MM's order, and the messages behind them.

**Options** holds what there is something behind: Log QSOs at all Stations,
which decides whether the contacts the others log are kept here; the
message trace, moved off the Messages tab where N1MM does not keep it; and
Run1/Run2, which used to be guessed from the radio number and is now the
operator's choice, sent in every `STATUS` and every `XMIT`. The transmit
interlocks stay out: this program does not block a transmitter, and a
station that claimed it did would be waited on for nothing.

**Call Stack Targets.** A callsign heard at one station and handed to the
position that will work it — `STACKANOTHERCALL` with the call alone,
`STACKCALL` with the contact behind it. The target is picked from the tab
or from the station list, and what arrives goes on the call stack of the
radio the operator is on, sorted by whether it is a multiplier here.

**The master** is the station the entry follows for cluster spots and the
time. `MASTER` names it to everybody, so the column agrees everywhere.

**The clock.** `TIME` carries a station's clock and Force Time Sync sends
it. N1MM sets the clock from it when it is running as an administrator and
says how far out it is when it is not; this program always does the second,
because setting the clock needs root and a contest logger has no business
asking for it. Anything over two seconds is called out.

**Serial numbers.** Reset Serial Numbers at all Stations sends
`RESETQSONRS` and every station starts again at one. The contacts already
logged keep the numbers they were sent with.

**What the entry agrees on** is now checked rather than assumed:

| What | How |
|---|---|
| the contest | `CONTESTNAME` as soon as a connection opens, and again in every `CHECKSUM` |
| the country file | its issue date — the publisher's `=VER20260826` — rides in `STATUS` |
| the computer name | longer than N1MM's fifteen characters is named at startup; a second computer answering to this one's name is named when its beacon arrives |
| the station number | two stations on the same number are named when the second says so |

`CountryFile` reads its issue date, which nothing had asked it for before.

Left for later: the master relaying its cluster spots, and the shared
serial-number pool where stations claim numbers in advance.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PdAYHcdRktqKry7nk414TU

docs/unfinished.md

@@ -396,16 +396,57 @@ burst of three does not read as thousands an hour. The five transmit-interlock
 flags in the message are sent as false: this program does not block a
 transmitter.
 
-**The network status window** has N1MM's Stations, Actions, Resynchronize,
-Rescore and Messages tabs and
+**The network status window** has all seven of N1MM's tabs — Stations,
+Resynchronize, Rescore, Options, Call Stack Targets, Actions and Messages — and
 its columns — Computer, IP Address, Pass, Run, 10, 100, Freq, Op, Msg, Send,
 Receive, Band, R/M, Mode. Right-click a row to pass the contact being worked to
 that station, to talk, or to close and open its connection; a connection closed
 by hand stays closed until it is opened again, because the next beacon would
 otherwise open it within ten seconds. The Resynchronize and Rescore tabs work
-on a period — the contest, since a time, or the last few hours. Left out: the
-transmit interlocks of N1MM's Options tab, the Master column and the
-call-stacking target tab. There is nothing behind any of them here.
+on a period — the contest, since a time, or the last few hours. Options holds
+what there is something behind: Log QSOs at all Stations, the message trace, and
+Run1/Run2. Left out are the transmit interlocks — this program does not block a
+transmitter, and a station that claimed it did would be waited on for nothing —
+and the two telnet options, which wait on the master relaying cluster spots.
+
+**What the entry agrees on.** Four things have to match across the stations of
+an entry, and each is now checked rather than assumed:
+
+| What | How it is checked |
+|---|---|
+| the program version | the beacon, which N1MM refuses to talk past |
+| the contest | `CONTESTNAME` as soon as a connection opens, and again in every `CHECKSUM` |
+| the callsign | `CHECKSUM` |
+| the country file | its issue date rides in `STATUS`; two issues score the same contact differently |
+
+A computer name longer than the fifteen characters N1MM allows is named at
+startup, a second computer answering to this one's name is named when its
+beacon arrives, and two stations that have taken the same station number are
+named when the second one says so.
+
+**The clock.** `TIME` carries a station's clock and Force Time Sync sends it.
+N1MM sets the clock from it when it is running as an administrator and says how
+far out it is when it is not; this program always does the second, because
+setting the clock needs root and a contest logger has no business asking for it.
+Anything over two seconds is called out.
+
+**The master** is the station the entry follows for cluster spots and the time,
+set from the station list and told to everybody, so the `Master` column agrees
+everywhere. What it does not do yet is relay: N1MM's master passes its cluster
+spots to the others over the link, and `ADDSPOT` and `PACKET` are not written.
+
+**Call stacking.** A callsign heard at one station and handed to the position
+that will work it: `STACKANOTHERCALL` with the call alone, `STACKCALL` with the
+contact behind it. The target is picked from the Call Stack Targets tab or from
+the station list, and what arrives goes on the call stack of the radio the
+operator is on, sorted by whether it is a multiplier here.
+
+**Serial numbers.** Reset Serial Numbers at all Stations sends `RESETQSONRS`
+and every station starts again at one. The contacts already logged keep the
+numbers they were sent with; the reset lasts as long as the program is open,
+the way N1MM's does. The shared number pool — `RESERVENR`, `QSONRS`, `REJECTNR`,
+where stations claim numbers in advance so two positions cannot send the same
+one — is not written.
 
 **The ten-minute rule.** `BandChangeRules` counts band changes and the stay on a
 band, and the entry window shows the countdown. What was missing was the rule