source-mtime-key globbed src/**/*.rs from the cwd and the cache path was
relative, so completion started in a subdirectory (src/) failed the globs,
keyed the entry "unknown" and wrote <subdir>/target/... under a key that
never goes stale.
The globs (via glob, since ls only expands literal patterns) and the cache
path are anchored on the script's repo root, and an unusable key (unknown or
none) is neither read nor written. check-filter-cache now proves the key and
path are the same from src/ as from the root, and that an unknown key leaves
no file behind.