Send WAE QTC traffic on CW

The QTC window took traffic down and read it out of the log, but nothing left
the window: on CW the operator had to send the lines by hand. It now puts them
on the air through the entry window's keyer, the way N1MM's QTC window sends
through its own entry window, so the same macros are expanded and the same
transmitter is pointed at first.

Sending a series: Send Hdr keys the header, Send1 to Send10 key one line each —
the time, the callsign and the serial number — and Close keys the TU message
when one is set. Taking one down: Hdr Agn asks for the header again, and shift
with Enter in a box asks for that one field again and clears it.

The messages and their defaults are N1MM's: AGN TIME, AGN CALL, AGN SERIAL, the
hard-coded HDR AGN with its two spaces, and a TU that sends nothing until the
operator writes one. So is the field spacing, written N1MM's way with S for a
space. All five are in Setup, where the note about the missing settings used to
be.

Nothing is sent on SSB or RTTY. N1MM plays four recordings on SSB and sends
RTTY from its digital window, and there is neither here, so on those modes the
buttons move the cursor as before. RX Ready sends nothing on any mode, because
a recording is all N1MM ever sends from it. Serial numbers go out as digits:
N1MM can send cut numbers and nothing here does, in any message.

Driven under Xvfb against a fake cwdaemon, in a WAE CW contest with four
contacts logged. Sending, it keyed QTC 1/2, 2257 DL1AAA 01, 2257 DL2BBB 01,
then QTC 2/2 with its two lines and TU DE W1ABC on close. Receiving, HDR  AGN,
AGN TIME, AGN CALL and AGN SERIAL.

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

docs/unfinished.md

@@ -39,17 +39,16 @@ and passed over. Acting on them means holding N1MM's section lists and its
 rules about which sections are retired, and getting that wrong throws away good
 data. The file is read without them.
 
-**The QTC window does not transmit.** Ctrl+Z opens it and traffic goes into the
-log, but N1MM sends the QTC text itself: the lines on CW and RTTY, and recorded
-voice messages for QRV, Agn, Cfm and TU on SSB. Here the Agn, Cfm and RX Ready
-buttons only move the cursor. What is missing under it is the message templates
-for QTC traffic, a voice keyer, and the digital window.
+**The QTC window transmits on CW only.** The header, the lines, the TU and the
+four again messages go out through the keyer, with N1MM's messages and N1MM's
+defaults. Nothing goes out on SSB or RTTY: N1MM plays four recordings on SSB —
+QRV, Agn, Cfm and TU — and sends RTTY from its digital window, and this program
+has neither a voice keyer nor a digital window. RX Ready therefore sends nothing
+on any mode here, because N1MM only ever sends a recording from it.
 
-**The QTC setup covers the window, not the sending.** Right-click ▸ Setup has
-the four settings that change how the window behaves, with N1MM's defaults.
-What is not there is everything about putting QTCs on the air: N1MM's CW
-messages for Agn and TU, its SQTC field spacing, its four SSB recordings, and
-its RTTY message templates. Those wait on a transmit path.
+**Cut numbers are not sent.** N1MM can key a serial number as letters — `N` for
+9, `T` for 0 — and offers several styles. Nothing here does, in a QTC line or in
+any other message.
 
 **Two WAE numbers do not agree with N1MM, both from 2020 and 2021 logs.** The
 disagreements are the country file of the day, not the rules: 4U1A counted as