0.1.3 — Honest lyrics errors

Linea reported "No synced lyrics for this track" for every track, including tracks that definitely have lyrics.

What was wrong

Two things, and only one of them was Linea's fault.

The trigger was external. lrclib.net, the lyrics source, can be blocked at the network level by ISP content filtering. When that happens no request ever reaches it. Confirmed on a Charter/Spectrum connection, where the CUJO filter intercepts the TLS handshake by SNI — the server itself is healthy and answers normally when the hostname is not inspected.

The bug was the reporting. Every failure — DNS, TLS, timeout, server error, network block — collapsed into an empty result, which the panel rendered as "No synced lyrics for this track". That is a confident claim about the track made from a request that never got an answer, and it made a blocked network indistinguishable from a broken app.

Changes

• Lyrics lookups now distinguish "this track has no synced lyrics" from "we never reached the service". Only a genuine 404 claims the former. The latter now reads "Can't reach the lyrics service — check your connection".
• Sends a User-Agent. lrclib asks clients to identify themselves and fronts its API with a WAF that drops requests it cannot attribute; Linea was sending the runtime default.

This makes the failure legible — it does not unblock a filtered network. If you see the new message, lyrics are being blocked before they reach Linea: check your router or ISP content filtering for lrclib.net. Changing DNS will not help when the filtering is inline. Tracking a fallback source in #25.

Includes everything from 0.1.1 and 0.1.2.