Score the last three cases the way N1MM scores them

The three differences left after replaying the log were ours on purpose. A log
has to score the same in both programs, so they now follow N1MM:

- ARRL DX and CQ WW RTTY count the 14 Canadian areas N1MM lists as `48SDC14P`,
  which keeps Newfoundland apart from Labrador. A station sending the postal
  code is counted as the area the contest names.
- A maritime mobile is scored from the call it signs. CQ WW says it counts for
  the zone alone; N1MM gives it the country, and so do we.
- A callsign the country file cannot place counts as a multiplier with an empty
  value, so every unplaceable call worked on a band shares one multiplier.

29 of the 37 contest instances in the log now agree with N1MM on every contact
and on the totals. What is left is the country file of the day and rows whose
cached points N1MM never worked out again after a call was corrected.

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

docs/unfinished.md

@@ -55,9 +55,7 @@ any other message.
 disagreements are the country file of the day, not the rules: 4U1A counted as
 `4U1V` then and as `OE` in today's `wl_cty.dat`, `KP2BH` counted as `KP2` then
 and is listed as a US call now, and China was not split by call area yet. The
-2022 to 2025 logs agree to the contact. One difference is ours on purpose: N1MM
-counts a callsign it cannot place — `D1M` — as a multiplier with an empty
-value, and we do not.
+2022 to 2025 logs agree to the contact.
 
 **Telnet window: what N1MM has and this does not.** Left out: the special-calls
 list, and saving received spots to a database — N1MM keeps those spots in its