This change switches the new Radio Browser path over to a dedicated server variable and persists resumed searches in a separate request file so old and new API formats don’t collide. It also threads the selected server through search, metadata, and playlist URL generation, which is important now that the new API recommends using randomized hosts and HTTPS-only endpoints. The result is a safer migration path for the incompatible API without breaking the ability to resume previous searches.