pathmemo 0.2.3

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.3-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.

---

The Reclaim tab, in the window, and five rules for a JavaScript and Solana machine.

Added

• Reclaim in the window. The tab that said not in the window yet now shows the report:
  the rules that matched the last scan, largest first, each with what deleting it gives
  back, its share, both axes (safe redownload, caution irreversible), a note and the
  number of places. A double-click or Enter lists the paths behind a rule; the word
  Reclaim above the list leads back, and the cursor returns to the rule it left. The risk
  ceiling is three segments — safe, caution, danger — and t cycles it; y copies the
  paths under the cursor.
• It reports and does not delete. Deleting is still pathmemo reclaim --apply and the
  terminal's Reclaim screen, where the guard checks every path first, and the tab says so.
  The headline counts only what pathmemo can delete itself; what needs another tool
  (git gc) or a person (a disk image) is listed, dimmed, and named beside the total
  rather than added to it. It ends in the id of the scan the numbers came from, and over a
  scan that was stopped early the tab says so: what was not read is not listed, so every
  number is a floor.
• The rules run on a worker, so the tab opens at once and says Applying 36 rules… until
  they are done: from the key to the list is under a second on a 1.2M-file snapshot,
  loading the snapshot included.
• Five rules for a JavaScript and Solana machine. dev.bun_cache (bun's global cache),
  dev.next (a .next beside a package.json), dev.playwright_browsers
  (%LOCALAPPDATA%\ms-playwright), dev.solana_tools (the platform tools in
  ~\.cache\solana, a copy per version) and dev.rustup_toolchains, which only reports
  and names rustup toolchain uninstall. dev.cargo also takes Solana's
  target\sbpf-solana-solana and target\sbf-solana-solana, and never target\deploy,
  where the program keypairs live. 36 rules now.

Fixed

• After a scan, the Tree tab said "run a scan first". A scan drops the snapshot the tab
  was showing, and nothing loaded the new one until the tab was left and re-entered. The
  Tree and Reclaim tabs now reload when a scan finishes under them.
• The scan card's Stop button sat on top of the path being read. The card was one line
  shorter than its contents; its height is now added up from them.

Known limitations

Audit and duplicates are still the commands and the terminal screens, and the window has no
delete dialog, which is why its Reclaim tab only reports. The rest is unchanged from 0.2.2.

406 tests; ten of the new ones drive the Reclaim tab through the shell, two hold the
scan card's lines clear of its button, and four pin the new rules.

---

SHA-256

1545e6fa37915b7ac0c92481d9625835e4b10445dd2481175902db67419f7fcf  pathmemo-0.2.3-win-arm64.zip
bbb65a7192ea8afd2aee765cb39918ad8892aef6c1c9d9b002e6372ef2b5eabc  pathmemo-0.2.3-win-x64.zip