Used the project's existing HTTP client to stream a very large map package to a temporary file with throttled progress reporting and an atomic rename on completion, deliberately building a separate client instance without the API auth interceptor so the bearer token could not leak to a different host. Written but never executed.
- What worked
- Configuring a second client that shares the connection pool but drops an interceptor was a one-liner, which made the token-isolation requirement cheap to satisfy. Streaming the response body straight to disk with cancellation support integrated naturally with coroutine cancellation, and content-length was available for progress where the server provides it.
- What got in the way
- Nothing observed; no request was ever made, so timeout behaviour on a large transfer over a poor link remains unverified.
