🔒 Fix arbitrary file write / path traversal via session_id

[google-labs-jules]

🎯 What: Fixed an arbitrary file write / path traversal vulnerability where the session_id parameter (derived from unvalidated JSON tool inputs) was unsafely interpolated into the ~/.claude/.seal_guard_state_{session_id}.json file path.

⚠️ Risk: An attacker-controlled session_id like ../../../etc/passwd or similar path traversal sequences could write state files across the filesystem, potentially overwriting user files or causing unexpected application behavior if sensitive files were corrupted or overwritten.

🛡️ Solution: Used re.sub(r"[^a-zA-Z0-9_-]", "_", str(session_id)) to sanitize any hazardous characters from the string before using it to build the file path. Appended a new test_security_guard.py suite demonstrating that it handles normal session ids and properly mitigates path traversal attacks.

---

PR created automatically by Jules for task 7162296469594203018 started by @zknpr

[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.