fix: remove FilteredStream stdout/stderr wrapper

[greysonlalonde]

Summary

• Removes FilteredStream class that wrapped sys.stdout and sys.stderr at import time to suppress LiteLLM noise
• litellm.suppress_debug_info = True already handles this
• The wrapper added a threading.Lock + string comparison to every print() call in the process and was not fork-safe for Celery prefork workers

Test plan

• Verify no LiteLLM banner noise appears in output
• Verify Rich console formatting still works correctly
• Run existing test suite

---

Note

Low Risk
Low risk: removes an import-time sys.stdout/sys.stderr wrapper, mainly affecting console/log output; primary potential regression is LiteLLM banner noise reappearing in some environments.

Overview
Removes the FilteredStream proxy and the import-time wrapping of sys.stdout/sys.stderr that previously filtered LiteLLM-related banner output.

Cleans up related imports, relying solely on litellm.suppress_debug_info = True for noise suppression instead of intercepting all process output.

^{Reviewed by Cursor Bugbot for commit e68975e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[iris-clawd]

Review: Remove FilteredStream

Excellent cleanup. This is the kind of change that silently fixes a whole class of bugs.

✅ Strong approve

• The FilteredStream was wrapping sys.stdout/sys.stderr at import time — every print() in the entire process went through a threading.Lock + str.lower() + substring match. That's measurable overhead on hot paths.
• Not fork-safe: Celery prefork workers would inherit the locked stream, risking deadlocks if a fork happened while the lock was held.
• __getattr__ delegation on IO streams is a footgun — libraries like Rich, logging handlers, and anything checking stream.buffer or stream.encoding can behave unpredictably with proxied streams.
• litellm.suppress_debug_info = True (already set at line 98) is the correct upstream solution.

No concerns. Ship it. 💬 175

[iris-clawd]

Approved. Ship it. ✅