[LouisHaftmann]

📝 Summary

A Range request on an empty Cache Entry got a different answer depending on the storage driver: 416 on filesystem and GCS, 200 or 416 on Azure depending on the start, and an empty 200 on S3. Now every driver answers with an empty 200. RFC 9110 §14.2 allows ignoring Range, and the route already does that for unmerged entries.

 download = storage.download(locationId, range)
 catch RangeNotSatisfiableError
+  if entry is empty
+    return 200, content-length: 0
   return 416, content-range: bytes */size

This also adds the missing test for the client-abort half of #282: if the client hangs up mid-download, the route destroys the storage stream, which releases the Storage Reader Lease.

Both commits are by @peter-svensson, cherry-picked unchanged from their fork.

✅ Verification

sqlite + filesystem, tests/range-download.test.ts and tests/proxy-backpressure.test.ts:

• Before: an empty merged entry answers bytes=0- / bytes=5- with an empty 200 fails with expected 416 to be 200
  After: passes
• Before: with sendStream in place of pipeline, download destroys the storage stream when the client hangs up fails with expected false to be true
  After: passes with pipeline (13/13 tests pass in both files)

S3, GCS, and Azure Blob were not run locally; CI's matrix covers them.

🔗 Issues

Closes #290

💥 Merge danger

Door: two-way

Blast Radius: small

Only affects Range requests on empty Cache Entries, which used to get a 416 on some drivers.

🤖 Generated with Claude Code