notifier::build_client and the Highport client both said their fallback arm keeps the timeout. The notifier's falls back to reqwest::Client::new(), which has no timeout. The Highport one does retry with the timeout set, but that retry fails for the same reason the first build did and unwrap_or_default() then panics, and it drops the no-redirect policy besides. Both comments now say what the PLC client's already says: the arm does not run in practice and exists to keep the constructor infallible. No behaviour change.
Refs atproto-crates#qpde.