Listing memory files can page through the new storage layer instead of walking the directory.
What's wrong with this entry?
Listing memory files gained a second path that pages through the storage layer and reads only the head of each file rather than walking the directory. It runs only when a storage backend is handed to the scan; otherwise the existing filesystem walk is used, unchanged.
- Failures on the new path report
memory_scan_storage_list_failed, kept separate from directory-read failures so the two can be told apart.
memory_scan_storage_list_failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.