Score Worked All Europe, QTC traffic and all

WAE is two contests in one. The QSOs are scored like any other, except that a
multiplier is worth four on 80 metres, three on 40 and two on the high bands, so
Multiplier grew a weight and ScoreTally sums weights rather than counting.
Europe works the rest of the world and the rest of the world works Europe; on
RTTY that rule is dropped and everybody works everybody.

The other half is QTC traffic: one station reads back contacts it has already
made, ten to a series, and every line is a point for both stations. Those lines
live in the log as rows of their own, exactly where N1MM puts them — Exchange1
says SQTC or RQTC, the reported contact's time, call and number go in the sent
report, received report and sent number columns, and the series in misc text.
So a log written by either program opens in the other with its traffic intact.
A QTC row is not a worked station: Contest.IsContact says so, and ContestLog
keeps such rows out of the dupe index and the multiplier index while still
counting their points. Cabrillo writes them as QTC: records.

Checked against eight real WAE logs rather than against my own reading of the
rules. Points agree with N1MM on all eight, to the contact. Weighted
multipliers agree on the six logs from 2022 on; the two older ones differ only
where the country file has since changed its mind, and in one place on purpose:
N1MM counts a callsign it cannot place as a multiplier with an empty value.

That comparison turned up two bugs of ours. A KG4 call is Guantanamo Bay only
when it is three or five characters long — KG4NE is, KG4IGC is an ordinary US
call — and the country file cannot say so, so every program that reads it
carries the rule. And Callsign is a record holding a list of modifiers, so the
generated equality compared that list by reference and two parses of one call
came out different.

Entering QTCs while operating is not there yet; the window is next.

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

README.md

@@ -41,7 +41,7 @@ scorer: red for a dupe, green for a new multiplier, blue for points.
 
 | | |
 |---|---|
-| Contests | CQ WW (CW, SSB, RTTY), CQ WPX (CW, SSB, RTTY), ARRL DX, IARU HF, Sweepstakes, RTTY Roundup, NAQP, general logging, and user-defined `.udc` contests |
+| Contests | CQ WW (CW, SSB, RTTY), CQ WPX (CW, SSB, RTTY), WAE (CW, SSB, RTTY), ARRL DX, IARU HF, Sweepstakes, RTTY Roundup, NAQP, general logging, and user-defined `.udc` contests |
 | Log | N1MM `.s3db`, Cabrillo 3.0 out, ADIF in and out |
 | While typing | dupe check, multiplier check, points, country and zone from the country file, exchange filled from a call history file |
 | Windows | entry, log, check, bandmap, available mults and Qs, score summary, packet |
@@ -265,6 +265,26 @@ are a drawing aid: a contact logs either side of a boundary just the same.
 Bands where N1MM's own numbers contradict themselves — 60M, and everything
 above 2M — get no shading rather than a guess.
 
+### Worked All Europe
+
+WAE is scored differently from everything else here. A multiplier counts four
+times on 80 metres, three times on 40 and twice on 20, 15 and 10, and half the
+score is QTC traffic: one station reports contacts it has already made to the
+station it is working, and every line reported is a point for both of them.
+
+The QTC lines live in the log as rows of their own, which is where N1MM keeps
+them — `Exchange1` says `SQTC` or `RQTC`, the time, callsign and serial number
+of the contact being reported go in the sent report, received report and sent
+number columns, and the series such as `9/10` goes in the misc text column. A
+log written by either program therefore opens in the other with its QTCs
+intact, and a QTC row is written to the Cabrillo file as a `QTC:` record.
+
+**Entering QTCs while operating is not there yet.** The rules, the scoring and
+the file formats are; the window for taking traffic down is next.
+
+The scoring was checked against six real WAE logs, and agrees with N1MM on
+points and on weighted multipliers to the contact.
+
 ### Band edges
 
 A contact just outside a band edge keeps its band. `Bands.ForFrequency` first