⚡ Bolt: Optimize recursive chown in cidata_ingest.py

[WHYCRASH]

💡 What: Replaced the external os.system("chown -R 1000:1000 /target/home/shane/") call in cidata_ingest.py with a native Python implementation using os.walk and os.lchown.

🎯 Why: Shelling out to chown creates unnecessary subprocess spawn overhead. Further, since the code was immediately following up with a native os.walk loop to apply restrictive chmod permissions to specific secrets files (rclone.conf, claude.json), it was forcing the system to traverse the /target/home/shane directory tree twice. By merging the ownership and permission logic into a single native os.walk traversal pass, we eliminate the subprocess fork and reduce filesystem I/O operations. os.lchown was chosen over os.chown to safely mirror chown -R's behavior of ignoring symlink targets by default.

📊 Impact: Reduces directory traversals for ingested secrets from 2x to 1x and removes the overhead of a system fork.

🔬 Measurement: Verify by executing the cidata_ingest.py tests with python3 -m pytest and ensuring correct ownership mapping against test stubs.

---

PR created automatically by Jules for task 5266368640206949669 started by @WHYCRASH

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