CALL_TIMEOUT_MS

Whole-call budget for one manifest fetch.

OkHttp's DEFAULTS are 10s connect and 10s read, which sounds covered but is not: both are per-operation. A server that accepts the connection and then dribbles bytes — one byte inside every read window — satisfies each timeout forever and the call never returns. callTimeout is the only one that bounds the whole thing, and it defaults to 0, meaning no limit. The initial fetch is awaited by startSession, so an unbounded call there is a startSession that never resolves and reports nothing.

15s leaves room for a slow-but-real mobile fetch (connect + TLS + body) while staying inside the harness's 30s per-command budget, so the device fails with a specific manifest error rather than a generic timeout.