fix: exclude DiskSage from active-use probes

[seonghobae]

Outcome

• exclude the current DiskSage PID and bounded probe PIDs from active-use results
• preserve every external handle and command-path blocker
• document the live self-blocking cache-audit gap and decision boundary

Live proof

Before the fix, each generated-cache audit reported its own transient CLI PID as process-active. After the fix, the inactive Homebrew API/bootsnap and Playwright caches produced complete blocker-free fresh plans; active uv remained protected by external processes and its lock.

Validation

• cargo test --manifest-path src-tauri/Cargo.toml active_use_pid_filter_excludes_probe_and_disksage_processes --lib
• fresh plan and immediate re-plan through disksage-generated-cache-reclaim
• git diff --check

Stacked on #320.

---

Protected prerequisite status

This PR remains Draft while the generated-cache owner PR #295 and its protected safety prerequisites remain Proposed and unmerged. Parent-handle checks reduce a reproduced gap; they do not prove exclusion of arbitrary late writers. Atomic no-replace restoration and current-head validation remain acceptance work. Unique changes are preserved through normal non-force parent integration; this status change is not a close or a shipped-safety claim.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

Devin Review found 1 new potential issue.