0.7.0 – Strava-first activities at once, HRV trend experiment, Synology guide

Strava-first activities enriched at once, a calmer second training advice to compare
with ImReady4's, and guides for Synology and a Windows that blocks unknown programs.

Upgrading needs no change to the configuration; the trend advice stays off until
BRIDGE_HRVTREND_ENABLED=true. Windows users: start the bridge with
py -m garmin_intervals_bridge … (also in run-bridge.cmd).

Added

• Experimental HRV trend advice (off by default, BRIDGE_HRVTREND_ENABLED):
  a second advice in a field of its own, HRVTrendAdvice (Rest / LIT /
  Planned), from the 7-day ln(rMSSD) mean against a 60-day normal range (±0.5
  SD), the night's average heart rate and a two-bad-nights rule – the way the
  HRV-guided training studies judged the trend (Plews, Kiviniemi, Vesterinen,
  Javaloyes, Nuuttila). HRVTrendCV holds the week's coefficient of
  variation. The bridge creates both fields; TrainingAdvice is never
  touched. hrvtrend previews, compares with ImReady4 (--compare) and fills
  the past (--apply). See docs/HRV_TREND.md.

Changed

• ImReady4 and the trend advice share their write and once-a-morning rules
  (advice.py); ImReady4's behaviour is unchanged.
• An activity the watch first saw as Strava's copy and that Intervals then
  replaced with Garmin's is enriched within the minute, no longer only by the
  next full scan (up to two hours later).
• The gear plan names retired Garmin gear that --create leaves out, and
  how to add it (--include-retired).

Documentation

• A step-by-step guide for Synology NAS (Container Manager), after @darken's
  write-up: the container, the Garmin login in its terminal while it runs, gear,
  the one-off history backfill, updating (docs/SYNOLOGY.md).
• The Windows guide starts the bridge with py -m garmin_intervals_bridge
  everywhere, run-bridge.cmd included: Windows' Smart App Control blocks the
  unsigned garmin-intervals-bridge.exe launcher pip creates (issue #5);
  Python itself is signed.

Fixed

• Intervals' rate limit (HTTP 429) no longer ends a wellness write: the same
  values are sent again after the wait Intervals asks for, and filling a range
  of days (imready4 / hrvtrend --apply) pauses briefly between writes.

Guides: Synology · Windows · HRV trend advice. Thanks to @darken for the Synology write-up and the Strava-first report.

Install: pip install -U garmin-intervals-bridge (Windows: py -m pip install --upgrade garmin-intervals-bridge), or the image ghcr.io/futureweb/garmin-intervals-bridge:0.7.0 / futurewebat/garmin-intervals-bridge:0.7.0 (Docker Hub).