🛡️ Sentinel: [HIGH] Fix command injection vulnerability in docker prune execution

[acebytes]

🚨 Severity: HIGH
💡 Vulnerability: The dockerPrune() function executed external commands via a shell wrapper (/bin/bash -c "docker system prune -f 2>&1"). While the current arguments were static, using a shell wrapper for external execution exposes the application to command injection vulnerabilities if arguments or environmental inputs are ever concatenated dynamically.
🎯 Impact: Exploitation of a command injection flaw allows arbitrary shell code execution with the permissions of the application, potentially leading to unauthorized data access, system compromise, or local privilege escalation.
🔧 Fix: Replaced the /bin/bash -c wrapper with direct binary execution. Configured Process to use executableURL = URL(fileURLWithPath: "/usr/bin/env") and explicitly defined arguments ["docker", "system", "prune", "-f"]. The shell redirection 2>&1 was securely replicated by assigning the same Pipe() to both process.standardOutput and process.standardError.
✅ Verification: Review Sources/Cacheout/ViewModels/CacheoutViewModel.swift to ensure process.arguments explicitly separates the binary and its flags, preventing the shell from interpreting them. Added .jules/sentinel.md capturing these findings to prevent future occurrences. Testing was skipped locally since swift toolchain is unavailable in this environment, but the direct execution approach guarantees argument isolation.

---

PR created automatically by Jules for task 12848386627005819593 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.