The generated listing at the TOP of a resource root (<root>/contents.json) — the authoritative
statement of what the root contains: every file and every folder under it, no more, no less.
(The one exception is itself: a listing does not list itself.)
This is what makes a miss impossible by construction for a served root: one fetch of this file and
the resolver knows exactly which packages and files the root holds, so it never has to ask for a
file that is not there. A root without one (a hand-assembled folder) still works — the resolver
falls back to probing, exactly as before this file existed.
The generated listing at the TOP of a resource root (
<root>/contents.json) — the authoritative statement of what the root contains: every file and every folder under it, no more, no less. (The one exception is itself: a listing does not list itself.)This is what makes a miss impossible by construction for a served root: one fetch of this file and the resolver knows exactly which packages and files the root holds, so it never has to ask for a file that is not there. A root without one (a hand-assembled folder) still works — the resolver falls back to probing, exactly as before this file existed.