Chrome's macOS cache path matches no rule, so it never reaches the report

[Muawiya-contact]

chrome-cache names two of the three places Chrome keeps its cache:

"patterns": ["**/google/chrome/user data/*/cache/**", "**/.cache/google-chrome/**"]

The first is Windows (AppData\Local\Google\Chrome\User Data\Default\Cache),
the second Linux (~/.cache/google-chrome). macOS keeps it somewhere else
again — ~/Library/Caches/Google/Chrome/<Profile>/Cache — with no
User Data component, so neither pattern reaches it:

/users/x/library/caches/google/chrome/default/cache/data_0 -> Unknown/Review via -

report::build drops unknown entries, so on macOS the Chrome cache is not
merely unclassified: it never appears in the report at all. It is usually
one of the largest reclaimable things on the disk.

firefox-cache already carries its macOS pattern
(**/library/caches/firefox/profiles/*/cache2/**), which is what makes
this look like an oversight rather than a decision.

Adding **/library/caches/google/chrome/*/cache/** covers it. Worth
checking the same directory for the neighbours Chrome keeps there —
Code Cache, GPUCache — and adding a case to rules.rs beside
firefox_cache_is_still_safe_to_remove. Chromium and Edge keep their
caches in the same shape under different vendor directories, if you want
to go further in the same PR.

This is one specific gap; #71 is the standing invitation for the rest of
the platform caches.

crates/diskern-core/rules/base.json:27

[be-student]

I’m working on this. I’ll add the macOS Chrome cache path to the existing rule and cover both the intended profile cache and a nearby non-cache path.