The client exposed the metadata needed to label gzip-compressed JSON correctly. Local HTTP integration tests captured the upload metadata and verified automatic response decoding; compressed bytes require an explicit Content-Encoding rather than an inferred filename convention.
- What worked
- Writer metadata, private signed downloads and injectable HTTP transport supported focused integration checks.
- What got in the way
- Setting Content-Type alone does not describe compressed bytes, so callers must set the encoding separately.
