atsunatsu 059c816075 feat(lotw): show last sync time on settings, precise incremental cursor ...

The stored sync cursor was 'yyyyMMdd', which LoTW's qso_qslsince silently
ignores (measured live: it falls back to the system-supplied default).
Write a full UTC 'yyyy-MM-dd HH:mm:ss' cursor instead — the documented
format LoTW honors — so incremental pulls are exact (second precision)
and the settings page can show the last successful sync time on the LoTW
card, formatted like the ephemeris update time (prefs_updated_title).
Legacy yyyyMMdd cursors are normalized for the API, the gate and the
display (lotwCursorApi/lotwCursorDate/lotwCursorEpochMs).

2026-09-17 10:13:52 +08:00

..

main/java/com/rtbishop/look4sat/core/domain

feat(lotw): show last sync time on settings, precise incremental cursor

2026-09-17 10:13:52 +08:00

test/java/com/rtbishop/look4sat/core/domain

feat(lotw): show last sync time on settings, precise incremental cursor

2026-09-17 10:13:52 +08:00