⚡ Bolt: Optimize SwiftUI View Model Array Computations

[acebytes]

💡 What: Replaced eager .filter usage in selectedSize and hasSelection computed properties with .lazy.filter and .contains(where:).
🎯 Why: Accessing the selectedResults property previously forced an immediate evaluation and allocation of a new filtered array just to calculate a sum or check if the array was empty. This caused unnecessary memory allocations and CPU cycles on every re-render.
📊 Impact: Eliminates O(N) memory allocations during selectedSize and hasSelection reads. hasSelection now short-circuits instead of fully filtering the collection, reducing overhead.
🔬 Measurement: Verify by interacting with checkboxes in the main view. CPU profiling will show fewer array allocations during updates.

---

PR created automatically by Jules for task 13140707354478696127 started by @acebytes

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[acebytes]

Closing as duplicate of canonical #404.

#404 makes both selectedSize use scanResults.lazy.filter AND hasSelection use contains(where:) on both scanResults and nodeModulesItems — full short-circuit on both arrays. The two PRs differ from #404 only by keypath idiom (#404 uses \.isSelected, slightly cleaner) and (for #399) by leaving hasSelection still calling selectedNodeModulesSize > 0, which forces a full reduce of nodeModulesItems to check for existence.

[google-labs-jules]

Closing as duplicate of canonical #404.

#404 makes both selectedSize use scanResults.lazy.filter AND hasSelection use contains(where:) on both scanResults and nodeModulesItems — full short-circuit on both arrays. The two PRs differ from #404 only by keypath idiom (#404 uses \.isSelected, slightly cleaner) and (for #399) by leaving hasSelection still calling selectedNodeModulesSize > 0, which forces a full reduce of nodeModulesItems to check for existence.

Understood. Acknowledging that this work is a duplicate of #404 and stopping work on this task.