Golden Fixture Co.Field notes
This page exists at a nested path and for no other reason. Everything a single-segment route proves is proved four times over elsewhere on this site; nothing else here proves that a route two segments deep survives the builder, the manifest and the serving lookup.
A nested route makes the builder derive an entry id with a slash in it, which is the only place bundler entry naming and on-disk output paths can diverge from the route string a visitor typed.
Route resolution is manifest-driven: nothing probes the filesystem for a directory index. A nested route is where an accidental return to index-probing would show up first, because that is the shape where guessing and looking up finally disagree.