v2.0.0

Added

• Configurable polling interval ("Update interval", in minutes) for every area/route, replacing the previous fixed, quota-derived interval. Defaults to 10 minutes for an area; for a route, to the route's sample-point count × 8 minutes (shown to you, recalculated live if you adjust the corridor width). Setting it to 0 disables automatic polling entirely for that entry.
• lufop_radar.refresh action ("Lufop Refresh"), for on-demand polling - most useful for entries with a manual-only (0) update interval, e.g. triggered from an automation, but works for any entry. Immediately fetches the latest radars, updates that entry's geo_location entities exactly like a normal poll, and returns the radars found so an automation can use them directly (e.g. in a notification) without a separate template step. See the README's new automation example.
• The route wizard's corridor-width step is now separate from the rest of the route's settings, so the following step can show an accurate, live "N sample points / requests per poll at this corridor width" explanation and a matching suggested update interval. An "Adjust corridor width instead of saving" option loops back to revise it without redrawing the whole route.

Changed

• Entries created before the update-interval option existed keep their previous (quota-safe, ~10 min × requests-per-poll) polling behavior until next saved via Configure, rather than silently switching to the new default.
• When update interval is 0, entities start empty instead of the integration making an API call on every Home Assistant startup/reload - the whole point of manual-only mode is avoiding automatic requests.
• The total-count sensor's name no longer has a stray German word ("Anzahl") left over from an earlier translation pass.

See CHANGELOG.md for the full history.