feat: add a logger filtering flag

[zilin]

📝 Description

🗣️ Type of Change

• 🐞 Bug fix (non-breaking change which fixes an issue)
• [*] ✨ New feature (non-breaking change which adds functionality)
• 📖 Documentation update
• ⚡ Code refactoring (no functional changes, no api changes)

🤖 AI Code Generation

• 🤖 Fully AI-generated (100% AI, 0% Human)
• [*] 🛠️ Mostly AI-generated (AI draft, Human verified/modified)
• 👨‍💻 Mostly Human-written (Human lead, AI assisted or none)

🔗 Related Issue

📚 Technical Context (Skip for Docs)

• Reference URL:
• Reasoning:

🧪 Test Environment

• Hardware:
• OS:
• Model/Provider:
• Channels:

📸 Evidence (Optional)

Click to view Logs/Screenshots

☑️ Checklist

• My code/docs follow the style of this project.
• I have performed a self-review of my own changes.
• I have updated the documentation accordingly.

[nikolasdehor]

Clean implementation of a useful debugging feature. A few minor notes: (1) Performance: logMessage now takes mu.RLock() on every call. Under heavy logging this could become a bottleneck. Consider using atomic.Pointer for the filter map so the hot path avoids the lock entirely. Not a blocker. (2) PR description: Please fill in the template. (3) Test isolation: The test does not reset currentLevel — consider adding cleanup in t.Cleanup to restore defaults. LGTM.