Track verified files nested under the indexed target namespace
A target name may contain a directory separator: VerifyDirectory names each target after its path within the tree, and SanitizeFilePath deliberately keeps separators. Those files land under a '{prefix}#' directory, which the flat EnumerateFiles scan could not see.
So a verified file below that directory was never added to the stale set, and removing or renaming a file inside a verified tree left its snapshot behind with the test still green. Received files in the same place were never swept either.
The scan now also walks '{prefix}#' subdirectories. The prefix is carried by the directory name, so a neighbouring test whose name merely starts with the same text keeps its own namespace.
Deletes the one file in this repo that the gap was hiding: an orphan added by #1547 alongside the sanitized name that replaced it. The suite now reports it, which is how it was found.