v3.7.3-beta2

Beta pre-release. DWD server-error handling fix. Continues the 3.7.3 beta line — drop-in upgrade from 3.7.3-beta1, no config changes required.

Fixed

• A source's own server errors (502/503/504) no longer show as "Rate limited." A tile fetch that failed with a generic non-OK status wasn't tagged with its HTTP status code, so it fell into the same handling as a rate-limit response — wrong banner, wrong retry pacing for a server that's up but struggling rather than one we're self-throttling against. 5xx responses now get their own "Radar server error — retrying" banner and a longer, capped exponential backoff (up to ~30s between attempts) better suited to a transient outage. (#223)
• Both the rate-limit and server-error banners now clear themselves as soon as a tile loads successfully again, instead of the rate-limit banner sitting there indefinitely (it previously had no hide path at all) or waiting on a fixed 10-second timer. Recovering also cancels the rate-limit path's fallback full-reinit, so a freshly-recovered loop isn't torn down and rebuilt for no reason. If both conditions are detected at once, each still shows its own banner, but a confirmed server error suppresses the disruptive fallback reinit, since the per-tile backoff is already handling recovery.

Full Changelog: v3.7.3-beta1...v3.7.3-beta2