SaveURL rejected the response on its Content-Type before it looked at
the status code, so any error the server returned as HTML (a reverse
proxy 502, an auth redirect, a wrong endpoint) surfaced as
"unexpected content type response: text/html; charset=utf-8" with no
mention of the status. Users had nothing to act on.
The check was also the only one of its kind in internal/integration:
every other client, including attachTags in this same file, decides on
the status code alone and lets json.Unmarshal report a body it cannot
read. Drop it so a failed save names its status.