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/QSL-Management.md

@@ -34,6 +34,38 @@ auto-refreshes the **award** stats.
 - **LoTW upload** goes through **TQSL** (ARRL's signer) — set the TQSL path and
   station location in Settings.
 
+## Paper QSL: sent, received, and how
+
+The QSL Manager's paper form sets four things on a batch at once — the sent
+status and date, the received status and date — plus **how the card travelled**,
+in each direction.
+
+Two ADIF fields are involved and they are **not** the same thing:
+
+| Field | Holds | Example |
+|---|---|---|
+| `QSL_VIA` | the **manager's callsign** | `M0OXO` |
+| `QSL_SENT_VIA` / `QSL_RCVD_VIA` | **how the card travelled** — an enumeration | `B` bureau · `D` direct · `E` electronic |
+
+Some loggers write the routing into the manager field, and OpsLog's own older
+versions wrote the words "Bureau" / "Direct" / "Electronic" there too. If your
+log has a mixture, OpsLog offers a **repair** — it tells you how many QSOs are
+affected **before** it changes anything, and it only moves values that are
+unmistakably a routing method (a manager is a callsign, never one of those six
+words).
+
+On **import**, the two fields are kept apart and nothing is invented: a file
+without a routing gives an empty routing. If you see `E` on every imported QSO
+it came from the file — Log4OM writes `QSL_SENT_VIA:E` on every record whether
+a card was ever sent. To clear them, filter the imported QSOs and use
+**Bulk edit field** with an empty value ([[Recent QSOs and Filters]]).
+
+## Confirmed means Y or V
+
+A LoTW confirmation can come back as **V** (verified) rather than **Y**. Both
+count as confirmed — in the awards, the band/mode matrix, the slot statistics,
+the row colours and the QSL Info tab alike.
+
 ## E-mail eQSL
 
 Right-click a QSO → **Send eQSL by e-mail** via the configured SMTP account. The