website: added qrg stuff to the features list and linked it to other articles

website/src/features/band-recognition.md

@@ -14,6 +14,7 @@ tagsList:
   - ON4KST
   - contest workflow
 related:
+  - qrg-detection
   - station-map
   - directional-opportunities
   - priority-score

website/src/features/dx-cluster.md

@@ -15,6 +15,7 @@ tagsList:
   - Minos
   - contest logger
 related:
+  - qrg-detection
   - station-map
   - directional-opportunities
   - log-sync

website/src/features/priority-score.md

@@ -15,6 +15,7 @@ tagsList:
   - SHF
   - contest workflow
 related:
+  - qrg-detection
   - band-recognition
   - timeline
   - airscout

website/src/features/qrg-detection.md

@@ -0,0 +1,102 @@
+---
+title: Automatic QRG Detection
+icon: 📻
+category: ON4KST Chat
+since: "1.1"
+summary: Recognise complete and relative QRG information in chat messages and retain the sender's recent band context before using a global fallback.
+description: KST4Contest extracts usable frequencies from public and directed ON4KST messages and makes the result available to band, priority, sked, path and logger workflows.
+tagsList:
+  - QRG detection
+  - frequency
+  - relative QRG
+  - band context
+  - ON4KST
+  - contest workflow
+related:
+  - band-recognition
+  - station-map
+  - priority-score
+  - sked-reminder
+  - dx-cluster
+---
+
+## Why detect a frequency from chat text?
+
+Frequencies in the ON4KST chat are rarely written in one consistent form. One station may send `432.088`, then shorten the next message to `.100`. Another may write `qrg 210` while a bare `210` in a different message means something else entirely.
+
+KST4Contest evaluates both public and directed chat messages so that useful QRG information does not have to be copied manually into every later operating step.
+
+Automatic QRG Detection has existed since version 1.1. The more precise sender-specific context evaluation described below is included from version 1.42 onwards.
+
+## Which forms are recognised?
+
+Complete frequencies provide their band directly. Examples include:
+
+```text
+144.210
+432,088
+10368.100
+```
+
+Relative forms omit the band and need additional context:
+
+```text
+.210
+,088
+qrg 210
+freq is 210
+on 210
+210 MHz
+```
+
+A dot or comma marks a relative frequency explicitly. A three-digit value is accepted only when nearby text identifies it as a frequency.
+
+## Which band is used for a relative QRG?
+
+KST4Contest resolves the missing band in this order:
+
+1. It first looks for a suitable band context detected for the same sender during the previous 30 minutes.
+2. If several current bands are known, it uses the most recently updated plausible context.
+3. Only when no suitable station context exists does it use the configured **Fallback band for relative QRG detection**.
+
+For example, assume that the global fallback is 144 MHz. A station first sends `432.088` and then `.100` a few minutes later. The recent context belongs to the same sender, so the result is `432.100 MHz`, not `144.100 MHz`.
+
+Another station without suitable recent context would use the global fallback for the same `.100` message.
+
+## Why are bare three-digit numbers ignored?
+
+Values such as:
+
+```text
+210
+599
+144
+```
+
+are deliberately not treated as QRGs without recognisable frequency context. Otherwise, a signal report of `599`, a band name or a QSO count could become a formally valid but operationally useless frequency.
+
+Rejecting an ambiguous number is less convenient than guessing correctly. It is considerably more convenient than tuning to a frequency which existed only in the parser's imagination.
+
+## Where is the detected QRG used?
+
+The most recently detected frequency appears in the **QRG** column. The same information can also contribute to:
+
+- [Band Recognition](/features/band-recognition/) and open band opportunities;
+- the [Priority Score](/features/priority-score/);
+- frequency selection for [skeds](/features/sked-reminder/);
+- the selected frequency for [path analysis](/features/station-map/); and
+- automatic or manually triggered [DX Cluster spots](/features/dx-cluster/).
+
+If a QRG appears in the same message which creates a directional opportunity, it is processed before the optional spot check. The new frequency can therefore already be used for that spot.
+
+## Text evidence is not current operating proof
+
+The result is derived from message text. KST4Contest cannot prove that the sender is still operating on the detected frequency, that the value was not superseded outside the chat or that an apparently clear statement belongs to the intended operating context.
+
+A detected QRG is useful working information. It is not a live measurement and not a guarantee that calling on that frequency will reach the station.
+
+In practical terms: the function preserves frequency context which would otherwise be easy to lose. The operator still checks whether that context remains plausible before using it.
+
+[Read the complete QRG Detection description in the manual.](/manual/en/features/#qrg-detection)
+
+[Open the fallback-band configuration.](/manual/en/configuration/#fallback-band-for-relative-qrg-detection)

website/src/features/sked-reminder.md

@@ -11,6 +11,7 @@ tagsList:
   - contest reminder
   - Win-Test
 related:
+  - qrg-detection
   - priority-score
   - airscout
   - timeline

website/src/features/station-map.md

@@ -15,6 +15,7 @@ tagsList:
   - Copernicus GLO-90
   - contest workflow
 related:
+  - qrg-detection
   - band-recognition
   - directional-opportunities
   - dx-cluster