Strange retries in during log download

```
log download 494
LOITER> Downloading log 494 as log494.bin
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 7.2 kbyte/s (3304 retries 38 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 7.1 kbyte/s (3423 retries 38 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 7.0 kbyte/s (3508 retries 38 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 6.9 kbyte/s (3644 retries 38 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 6.8 kbyte/s (3805 retries 36 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 6.5 kbyte/s (4062 retries 33 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 6.4 kbyte/s (4195 retries 30 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 5.1 kbyte/s (5398 retries 13 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 4.3 kbyte/s (5827 retries 7 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 4.1 kbyte/s (5878 retries 3 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 3.8 kbyte/s (5935 retries 0 missing)
log status
LOITER> Downloading log494.bin - 2232320/2232320 bytes 3.6 kbyte/s (5979 retries 0 missing)
Finished downloading log494.bin (2232320 bytes 634 seconds, 3.5 kbyte/sec 5995 retries)

```
Total download time was about 10 minutes, with last 3 minutes having "0" missing.

Start by reproducing the `log download` and `log status` sequence shown in the report, recording retry and missing-block counts as the transfer completes. Trace the command's download entry point and determine why retries continue after all bytes are received; done means the completed download no longer spends minutes retrying unnecessarily, with regression coverage for the reported output.

Written by the indexing model from the issue text.