Release 1.0.5

Author: AI3I

.gitignore

@@ -7,3 +7,6 @@ logs/
 dist/
 build/
 *.egg-info/
+config/pycluster.local.toml
+.codex
+.deploy-files.txt

CHANGELOG.md

@@ -2,6 +2,35 @@
 
 All notable changes to pyCluster should be recorded here.
 
+## 1.0.5 - 2026-04-04
+
+### Changed
+
+- cleaned up the telnet command surface so operator responses are more readable and more consistent across `show/*`, `set/*`, `unset/*`, mail, route, protocol, and sysop command families
+- moved a large share of operator-facing telnet text and selected operational log strings into `config/strings.toml` so wording tweaks no longer require code edits or restarts
+- public web 24-hour spot stats, history, and leaderboard views now use real time-window queries instead of capped recent-spot snapshots
+- the System Operator web console now shows country-data status more clearly, including left-nav pills for loaded `CTY.DAT` and `wpxloc.raw` version/date metadata
+- deploy tooling now treats country-data refresh as `CTY.DAT` plus `wpxloc.raw`, and `deploy/doctor.sh` checks the public stats endpoint on the correct listener
+- upgrades and deploys are now documented around `config/pycluster.local.toml` so host-local settings stay out of the tracked base config
+
+### Added
+
+- `wpxloc.raw` parsing and fallback lookup support for heading, web spot enrichment, and suspicious-prefix review cues
+- email OTP MFA recovery paths in both the System Console and telnet via `sysop/clearmfa <call>`
+- stale-user cleanup controls in the System Operator web console
+- richer cluster-mail observability in telnet and the System Operator web console
+
+### Fixed
+
+- `set/name`, `set/qth`, `set/qra`, `set/location`, `set/home`, and related `show/*` commands now persist and read back consistently
+- `set/location` now takes precedence over `set/qra`, while `set/qra` backfills location only when location is unset
+- `show/heading`, `who`, `show/links`, `show/route`, and related peer/operator views now report more accurate live state
+- telnet login handling no longer misbehaves when negotiation bytes are present before the callsign
+- public web frequency formatting and 24-hour summary counts now match real backend data better
+- live spot ingest now uses permissive plausibility checks instead of an over-strict homemade world callsign validator, while suspicious cases are flagged for review instead of being dropped
+- cluster mail routing handles offline peers and undeliverable paths more cleanly, with clearer operator readback
+- `show/wm7d` CQ-zone handling for calls like `N9JR` now prefers better lookup data instead of stale prefix-only assumptions
+
 ## 1.0.4 - 2026-03-30
 
 - fixed the cumulative upgrade path so older `1.0.0` databases with the real `user_prefs(pref_key, pref_value)` schema now upgrade cleanly through `deploy/upgrade.sh`

README.md

@@ -16,7 +16,7 @@ It keeps the familiar telnet-style operator experience, adds a public web UI and
 
 - Telnet-first DX cluster workflow with modernized operator output
 - Public web UI for users and a dedicated web console for system operators
-- SQLite persistence, CTY refresh tooling, and fail2ban integration
+- SQLite persistence, CTY and wpxloc refresh tooling, and fail2ban integration
 - Validated deploy path across modern Debian, Ubuntu, Fedora, and Red Hat-family Linux
 
 ## 🧭 What pyCluster Does
@@ -29,7 +29,7 @@ It keeps the familiar telnet-style operator experience, adds a public web UI and
 - ships with deployment tooling for systemd-based Linux hosts
 - integrates with fail2ban for login-abuse protection
 - supports age-based cleanup for spots, messages, and bulletins
-- maintains local CTY data with optional automatic refresh from Country Files
+- maintains local `CTY.DAT` and `wpxloc.raw` data with optional automatic refresh from Country Files
 
 ## Where pyCluster Improves on Legacy Cluster Software
 
@@ -67,6 +67,15 @@ In practice that means:
 
 pyCluster is usable today as a single-node cluster with web and telnet access, persistent storage, peer linking, and operator controls. The codebase is still evolving, but it is no longer just a prototype.
 
+Current release: `1.0.5`
+
+Recent highlights in `1.0.5`:
+
+- cleaner and more human-readable telnet/operator command replies
+- `CTY.DAT` and `wpxloc.raw` visibility plus refresh support
+- public web 24-hour spot stats that reflect real time windows
+- more complete MFA recovery, cluster-mail observability, and config-override documentation
+
 ## 🖥️ Interfaces
 
 ### Telnet
@@ -131,6 +140,8 @@ pip install -e .
 pycluster --config ./config/pycluster.toml serve
 ```
 
+Operator-local overrides can live in `./config/pycluster.local.toml`. When present, pyCluster loads `pycluster.toml` first and then layers `pycluster.local.toml` on top. Keep the tracked base file close to upstream and put host-specific changes in the local override file.
+
 Deploy on a supported Linux host:
 
 ```bash
@@ -149,6 +160,7 @@ Typical deployed layout:
 /home/pycluster/pyCluster/          # live runtime tree
 ├── config/
 │   ├── pycluster.toml              # active node configuration
+│   ├── pycluster.local.toml        # optional untracked local override
 │   └── strings.toml                # hot-reloadable operator text
 ├── data/
 │   └── pycluster.db                # live SQLite database
@@ -168,6 +180,8 @@ sudo ./deploy/upgrade.sh
 sudo ./deploy/doctor.sh
 ```
 
+For git-based upgrades, move site-local changes out of the tracked `config/pycluster.toml` file and into `config/pycluster.local.toml` first. That keeps `git pull --ff-only` clean while preserving local runtime settings.
+
 For upgrades from `1.0.0` through `1.0.3`, `deploy/upgrade.sh` performs the required cumulative state conversion for older installs:
 
 - hashes any legacy plaintext passwords still stored in `user_prefs`
@@ -273,19 +287,33 @@ Auth-failure log retention:
 
 - shipped logrotate policy for `/var/log/pycluster/authfail.log`
 
-## 🌍 CTY Data
+## 🌍 Country Data
 
-pyCluster ships with a bundled `cty.dat`, and install/upgrade perform a best-effort refresh from Country Files.
+pyCluster supports both `CTY.DAT` and `wpxloc.raw`.
+
+That data is used for:
+
+- DXCC/entity and zone enrichment
+- heading and lookup fallbacks
+- operational review cues for unusual spot prefixes
+- sysop visibility into currently loaded country-data versions
+
+pyCluster ships with bundled country-data fixtures, and install/upgrade can perform a best-effort refresh from Country Files.
 
 Manual refresh:
 
 ```bash
 python3 ./scripts/update_cty.py --config ./config/pycluster.toml
 ```
 
+By default this refreshes both `CTY.DAT` and `wpxloc.raw`. Use `--cty-only` if you intentionally want to skip the `wpxloc.raw` update.
+
 Automatic refresh:
 
 - `pycluster-cty-refresh.timer`
+  - refreshes both `CTY.DAT` and `wpxloc.raw`
+
+The System Operator web console and telnet `show/configuration` also report dataset load state, path, and version/date when available.
 
 ## 🧹 Retention and Cleanup
 

config/pycluster.local.toml.example

@@ -0,0 +1,15 @@
+[node]
+# qth = "Boston, MA"
+# node_locator = "FN42LI"
+
+[telnet]
+# port = 7300
+
+[web]
+# admin_token = "change-me"
+
+[public_web]
+# enabled = true
+
+[store]
+# sqlite_path = "./data/pycluster.db"

config/pycluster.toml

@@ -26,6 +26,7 @@ host = "127.0.0.1"
 port = 8081
 static_dir = "./web/public_dxweb/static"
 cty_dat_path = "./fixtures/live/dxspider/cty.dat"
+wpxloc_raw_path = ""
 
 [store]
 sqlite_path = "./data/pycluster.db"