pathmemo 0.2.4

Windows 10 1809 or later, x64 or arm64. One file, self-contained - no installer, and
no runtime to install alongside it.

1. Download pathmemo-0.2.4-win-x64.zip, or -win-arm64 on an ARM machine.
2. Unpack it anywhere.
3. Double-click pathmemo.exe for the window, or run it from a terminal:
   pathmemo scan, pathmemo top --min 1GB, pathmemo audit.

Windows will warn that the publisher is unknown, because the executable is not
code-signed. Choose More info -> Run anyway, or check your download against the
SHA-256 below first.

Administrator rights are optional, and change what the scanner can see: with them it
reads $MFT directly, which is roughly 40x faster and reaches paths a directory walk is
denied.

Nothing is deleted without an explicit confirmation, and what is deleted goes to a
quarantine that pathmemo restore reverses.

---

Two rules that named the wrong thing, and one piece of advice that could cost a Solana
program its address.

Fixed

• dev.cargo advised cargo clean. A bare cargo clean deletes the whole target,
  target\deploy included, and that folder holds the Solana program keypairs the rule
  itself is written never to touch. The rule now gives no command: pathmemo deletes only
  the build directories it lists.
• dev.cargo also claimed ~\.cargo\registry and offered cargo clean for it, which
  never touches the registry. The registry is its own rule now, dev.cargo_registry
  (safe, redownload): the next build fetches what it needs.
• VS Code's extension packages were reported as Visual Studio's state.
  CachedExtensionVSIXs is VS Code's store of downloaded .vsix files, not a Visual
  Studio folder. It has its own rule, dev.vscode_vsix_cache (safe, redownload);
  dev.vs_artifacts keeps .vs.
• README: the release publishes zips, not bare pathmemo-win-*.exe files, and a winget
  install keeps the exe in winget's own packages folder. The rules table (§7.2) had drifted
  from the rules and now matches them again: Unity's Library and its two conditions, the
  shader and Electron cache paths, Chromium's Code Cache, Explorer's icon cache, the
  pyvenv.cfg that makes a venv a virtual environment, Docker's vhdx paths, the
  1 MB floor on old logs and installers, git gc from 500 MB and large media from 1 GB inclusive, installers in
  subfolders of Downloads, and %TEMP% emptied rather than removed.

Changed

• 38 rules. A config.json that disables dev.cargo or dev.vs_artifacts to keep the
  registry or the VSIX cache out of the report now needs dev.cargo_registry or
  dev.vscode_vsix_cache in rules.disabled as well.

408 tests; the two new ones pin the split rules and that no Rust rule advises
cargo clean.

---

SHA-256

ec6cbff61e2fe712cf668c1c8582066f116bbf636a9327a8b74037bc5142e6c9  pathmemo-0.2.4-win-arm64.zip
e2d753cd5ff8cb523e1ef2ff8c4d96fb9334d1ca00c0740c088cef95f01a2a4c  pathmemo-0.2.4-win-x64.zip