[ibnbd]

Summary

Ninth pass at the 0.3.5 list. The headline is a new antivirus detection engine, wired so it actually inspects the machine, plus Security-tab removal that now exists in both UIs with one shared policy.

Nothing here has been compiled (no Rust toolchain in this sandbox) - this PR is the CI gateway: cargo fmt --check, cargo clippy --workspace --all-targets --all-features -- -D warnings, cargo test --workspace --all-features, cargo audit.

Antivirus: new persistence engine

Every other engine asks is this code malicious? This one asks has something already made itself at home? It inspects the four families of files whose only job is to run something later (launchd plists, shell startup files, cron drops, systemd user units) and fires only on the payload, never on existence:

• PERSIST_LAUNCHD_DOWNLOAD_EXEC / _DECODE_EXEC - agent fetches or decodes and runs code
• PERSIST_LAUNCHD_TEMP_EXEC[_RUNATLOAD] - executable in /tmp or a hidden dir
• PERSIST_LAUNCHD_INLINE_SCRIPT - -c/-e body that downloads, decodes, or hides
• PERSIST_SHELLRC_* - curl|sh, base64-eval, launchctl load, detached nohup
• PERSIST_CRON_* / PERSIST_SYSTEMD_* - @reboot and short-interval beacons

24 unit tests, including the true negatives that matter: a normal LaunchAgent, an ordinary .zshrc, a commented-out payload, a normal crontab, and a binary plist all stay clean. Dot-directories that are the ordinary home for user tooling (~/.local, ~/.cargo, ~/.cache) are explicitly not treated as hidden, which is where a naive version of this check produces false positives.

Crucially it is wired to real host state: new SecurityTargetKind::HostPersistence scans ~/Library/LaunchAgents, ~/.config/systemd/user, and the nine shell-rc names in $HOME. Without this the engine would only ever fire on packages that ship persistence files.

Security removal, in both UIs from one policy

SecurityRemoval now lives in cleanton-engine as the single source of truth for what is removable and how, so the Slint app and the TUI cannot drift:

• Slint: two-step arm, then confirm/cancel on each row; npm/pip through PackageManagers::uninstall, everything else through the executor's reviewed trash_suggestion. ActionButton gained a danger tint so a destructive control never reads as an ordinary secondary button.
• TUI: [r] arms, [y] runs, [n] cancels; moving the cursor disarms. Same two paths, same engine copy.

Host persistence files get no Remove button and an "open it and delete the flagged line" remedy. Trashing a user's .zshrc to fix one line would be the wrong fix, so Cleanton refuses it in both UIs, with a defence-in-depth guard in the removal runner too.

Background helper: disk/memory cleanup

resource_pressure_events was emitting whitespace-mangled strings ("...and clean <many spaces> caches") from broken string continuations. Replaced with a real measurement: a bounded (20k-entry budget) walk names the top-3 reclaimable directories plus the Trash.

Disk is 93% full (48 GB available). Biggest reclaimable right now: Xcode (18.4 GB), Trash (6.1 GB), ms-playwright (2.2 GB).

Edge-triggered as before, and the budget means it can never stall the watcher.

Recipes: 141 to 153

• 22 macOS-only recipes gained Linux ~/.cache/* alternatives (pip, poetry, Go, Deno, Cypress, Playwright, Yarn, Coursier, JetBrains, Firefox, Slack, Zoom, Spotify, Android Studio...). This is the biggest single fix for "the scanner misses things on Ubuntu".
• 12 new: Edge/Brave/Vivaldi HTTP caches, Discord, node bundler caches, thumbnails, Trivy/Grype/Snyk caches, apt/snap/flatpak caches, Helm, Firebase emulators, Nim, Dune. All documented in doc/RECIPES.md.

Slint UI fixes

• Caught before shipping: cross-axis-self-alignment only exists in Slint 1.18; this tree pins 1.17.1. Centring now uses cross-axis-alignment on the container or a wrapper HorizontalLayout { alignment: center; }.
• Transient spinners and the activity bar are conditional if, not visible: false (which still occupies layout and shifts rows).
• Duplicate sets render as a set header plus one row per copy, capped at 12 copies / 25 sets.

Also

• Version 0.3.5.
• scripts/check-ui-copy.py (em-dash guard for user-visible copy) is wired into CI as a copy job ahead of audit; it passes.

Known gaps

• Scanner performance is untouched this round. The prior generation's hot paths are already fixed; the remaining wins are allocation/traversal in walker.rs / metadata.rs, and guessing at them without a profiler seemed worse than leaving them.
• doc/*.md prose still carries em dashes (the guard covers shipped UI copy, not developer docs).
• cleanton-antivirus is vendored from rb-antivirus. The new engine is a self-contained engines/persistence.rs touching only three lines of upstream engines/mod.rs, so it should sync cleanly in either direction.