Fix
Corrected a cosmetic bug in the version-check message. The Update Available log line and UI toast rendered the latest version with a doubled v prefix (e.g. vv1.26.1362003) because the message interpolated v{latest_version} while latest_version already carried the GitHub release tag's own v.
Both the parsed and fallback message branches now use the already-stripped version values (latest_clean / current_clean), and the fallback equality check compares stripped values so it can no longer report a spurious update for an identical version.
Display-only change — no effect on stream checking, scheduling, or Dispatcharr integration.