docs(wiki): cover the recent work, with worked examples

Asked for the wiki to catch up, and to be explicit — examples rather than
descriptions. New page and six rewritten sections.

Recent QSOs and Filters, the page named in the request: the right-click menu is
now a table of what every entry does, and the filter builder has five worked
multi-criteria filters written out field by field, each ending in what you then
do with the result. Including the distinction that prompted it — "export
selected" takes the highlighted rows, "export filtered view" takes every QSO the
filter matched, and after building a filter it is the second one you want. Plus
the traps: ADIF date format, and "is empty" not being "equals N".

Connections (new): the page for a settings section that had none. What OpsLog
listens to and sends, which outbound row another logger actually wants — a
logger asking for "WSJT-X UDP" discards a bare ADIF record — the custom-message
triggers with their placeholder lists, three worked examples, and the port-clash
warning that produced this week's CAT-drop report.

Amplifiers and Switches: the generic HTTP relay in full — per-relay URLs, the
pattern form, {relay}, {relay-1} and {value} with what each one sends — relay
automatic control with a four-relay antenna-switch example, and the bench power
supply including why OpsLog writes only its output.

Rotators: the two new native types (SPID with the Rot1Prog/Rot2Prog choice,
DCU-1), two-rotor setups, and that Test only reads the heading on the types
where it does.

Awards: the US county database, and the difference between the automatic fill
(blanks only) and the right-click re-derive (replaces) — with the Connecticut
planning regions, which is the case that needs it.

QSL Management: QSL_VIA against QSL_SENT_VIA/QSL_RCVD_VIA, why an import shows E
on every Log4OM record, and that V counts as confirmed.

Troubleshooting: the three field reports of the last few days, by symptom.

Every [[link]] checked to resolve.

wiki/Awards.md

@@ -163,3 +163,40 @@ built-in award without fear of a future release overwriting it.
 
 **Rescan** re-pulls the logbook and recomputes — it picks up fresh LoTW / QRZ /
 eQSL confirmations (see [[QSL Management]]).
+
+---
+
+## US counties (CQ USA-CA)
+
+A county award needs a county on every US QSO, and most logs do not have one:
+neither the callsign nor the prefix carries it, and few operators send it.
+
+**Settings → US counties** downloads the FCC **ULS** database — every US
+amateur licence with its address — and builds a local index of callsign →
+county + grid. It is a few hundred megabytes to fetch and takes a few minutes;
+once built it works offline and needs no key.
+
+With it downloaded:
+
+- A **new US QSO** gets its county (and grid, if you have none) filled in
+  automatically — **only where the field is empty**. A value you or QRZ
+  supplied is never overwritten: the ZIP-derived county is about 98 % right and
+  the one you logged is usually better.
+- **Right-click → Update US county from the ULS database** re-derives the
+  county of the selected contacts and **replaces** what is stored. That is the
+  deliberate opposite of the automatic pass, and it is the way to correct
+  counties already in the log — see the Connecticut note below. Contacts
+  outside the US, and callsigns the database does not hold, are left alone.
+  The entry only appears once the database is downloaded.
+
+### Connecticut
+
+Connecticut **abolished its eight counties** for statistical purposes in 2022;
+the Census Bureau replaced them with nine **planning regions**. CQ USA-CA still
+uses the old county names, so OpsLog maps a Connecticut address back to its
+legal county.
+
+If your database was built by an older OpsLog, the Settings panel says so and
+offers a refresh — a download date alone cannot show it, because a database
+fetched yesterday by an older version still holds the wrong Connecticut
+counties. After refreshing, use the right-click update on your CT contacts.