files_for_layer_range() silently dropped required weight files that were
missing from the tracker's local snapshot directory, so a snapshot with
zero (or partial) shard files downloaded still reported back a "complete"
file list (metadata only, or a partial subset). Nodes then trusted that
subset as fully cached and skipped the real download, only discovering
the missing weight shards at model-load time.
Now, if any weight file required for the requested layer range is absent
on disk, the tracker returns an empty file list for that range so it
isn't offered as a source at all, letting the node fall through to
peers/HuggingFace for the real data.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2868fc0d56