[Labreo]

🎯 What: Hardcoded debugMode = true flag in content.js resulted in sensitive track metadata, listening activity, and blocklist events being logged to the browser console.

⚠️ Risk: When active, verbose debug messages containing track titles, artist names, album details, and user blocklist actions are printed to the developer console, potentially exposing user listening habits and preferences.

🛡️ Solution: Set this.debugMode = false by default in YTMBlockController (content.js). Added unit tests in tests/debugMode.test.js to ensure debugMode defaults to false and suppresses debug logs unless explicitly enabled.

---

PR created automatically by Jules for task 4167052389380397264 started by @Labreo

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