Give the network status window N1MM's tabs and columns

The window was one flat table of columns this program made up. N1MM's has
tabs and a fixed set of columns, and an operator who knows one has to be
able to read the other.

**The window** now has Stations, Actions and Messages. Stations is a grid
with N1MM's headers in N1MM's order — Computer, IP Address, Pass, Run,
10, 100, Freq, Op, Msg, Send, Receive, Band, R/M, Mode — and a row per
station, this computer included. Right-click a row to pass the contact
being worked to that station, to talk, to show the connection log, or to
close and open its connection. Actions holds the talk line, the pass
frequency, the echo and the networking switch; Messages holds the chat,
the connection failures, the echo round trips and a trace of every
message that arrives.

**`STATUS`** is what fills those columns. N1MM sends it every few seconds
whether anything has changed or not — the pass frequency, the frequency,
run or search and pounce, the operator, the rates over the last ten and
the last hundred contacts, the mode, the categories and the version — so
a station sitting on one frequency for an hour still has a current row.
`BANDMAP` only says a station moved. The five transmit-interlock flags
are sent as false: this program does not block a transmitter.

**`Rates.PerHour`** reads the two rate columns out of the log. Count back
over the last N contacts, stop at a gap longer than the contest's minimum
off time, and treat a span under a minute as a minute, so three contacts
in five seconds read as 180 an hour rather than 2160.

A connection closed by hand stays closed. Without that flag the next
beacon opens it again within ten seconds, which makes the menu item look
broken.

Left out, because there is nothing behind them: N1MM's Resynchronize and
Rescore tabs, the transmit interlocks of its Options tab, the Master
column and the call-stacking target tab.

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

docs/unfinished.md

@@ -382,6 +382,26 @@ Where a station is goes out once a second when it has changed, rather than from
 each of the dozen places it can change from. In a multi-single entry that is
 what the other operators watch.
 
+**The status message.** `STATUS` goes out every five seconds whether anything
+has changed or not, and it is what fills the other operators' windows: the pass
+frequency, the frequency, run or search and pounce, the operator, the rates over
+the last ten and the last hundred contacts, the mode, the categories and the
+version. `Rates.PerHour` reads the two rates out of the log the way N1MM does —
+counting back over the last N contacts, stopping at a gap longer than the
+contest's minimum off time, and treating a span under a minute as a minute so a
+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 and Messages tabs 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. Left out: N1MM's Resynchronize and Rescore
+tabs, the transmit interlocks of its Options tab, the Master column and the
+call-stacking target tab. There is nothing behind any of them here.
+
 **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
 itself: only a user-defined contest carried one, so every built-in contest