🛡️ Sentinel: [MEDIUM] Fix process pipe deadlock in Docker Prune

[acebytes]

• 🚨 Severity: MEDIUM
• 💡 Vulnerability: process.waitUntilExit() is called before reading from the output pipe. If the process output exceeds the macOS pipe buffer (~64KB), the child process will block writing, and the parent will block waiting, causing a deadlock.
• 🎯 Impact: An attacker or a verbose Docker output could cause the application to hang indefinitely.
• 🔧 Fix: Read the pipe data concurrently or before waitUntilExit() using try pipe.fileHandleForReading.readToEnd() ?? Data().
• ✅ Verification: Run docker system prune and observe that the app successfully captures the output without freezing, even with large logs.

---

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