After figuring out why any configuration stopped working for mozilla/bedrock (currently suspecting tag pagination in /shas and following all the result pages separately), I've realized the /shas response eventually arrives according to network devtools, however the JS client already gave up waiting for it at that point.

(Yes, the API timeout is 10s, and the JS timeout is 10s too, but the /shas happily loads dozens of individual /tags API calls, so the real limit is the app/server timeout in this case…)

The ky post() can be easily configured, what about going from implicit retries: 2, timeout: 10000 to retries: 3, timeout: 30000 to at least consume what the server had to prepare? O:)

(This won't change the load really, as all the hard work's been done anyways, currently it's just thrown away as the client's not interested any more…)