Take WAE QTC traffic down

Ctrl+Z opens the QTC window for the station being worked, which is the key N1MM
puts it on, and the window is laid out the way N1MM lays it out: the header,
ten lines of time, callsign and serial number, an Agn and a Cfm button beside
each, Clear, Close and Cancel underneath, and the same colours — green for a
line that will be saved, red for one still empty, yellow for one that cannot be
read. Enter and Tab move forward and space moves within a line, so a line can be
walked while listening to it.

Sending, the lines are filled from the log and cannot be edited: the contacts
not reported to anybody yet, oldest first, never the station being worked, and
never past the ten any station may have. The rule for what has been reported is
N1MM's — a contact counts as reported when a QTC row carries its call and the
serial we sent it — so the pair is kept in the row the way N1MM keeps it.

Which way traffic goes is not the operator's choice on CW and SSB: Europe
receives and the rest of the world sends. On RTTY it goes both ways, and there
the window carries a switch. That is the one piece of the workflow that is ours
rather than N1MM's, which toggles a QTC mode outside the window instead.

Nothing here transmits. N1MM sends the lines on CW and RTTY and plays recorded
voice messages on SSB; we have no QTC message templates, no voice keyer and no
digital window, so Agn, Cfm and RX Ready move the cursor and the operator sends
by hand.

Running it caught what the tests could not: focus set in the constructor does
not stick, so the first thing typed into a freshly opened window was dropped and
every field after it took the value of the one before.

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

docs/unfinished.md

@@ -39,10 +39,15 @@ 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.
 
-**Entering WAE QTC traffic.** The contest, the QTC rows, the scoring and the
-Cabrillo `QTC:` records are in, and a log written by N1MM reads back with its
-QTCs. What is missing is the window an operator takes traffic in: today a QTC
-can only reach the log by being read from a file N1MM wrote.
+**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.
+
+**N1MM's QTC setup tab is not there.** Field spacing, the CW messages for Agn
+and TU, and the settings that skip the Cfm and QRV steps are all N1MM options
+this window does not have.
 
 **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