fix: make trace_include_sensitive_data default to False for security

[OpenSourceSoul]

Problem

By default, was set to , which meant sensitive data (tool inputs/outputs, LLM generations) was automatically included in traces without explicit user consent. This violates the security principle of "secure by default" and could lead to:

• Accidental data leakage of PII, secrets, or confidential information in production traces
• Compliance violations for organizations with strict data handling requirements
• Security incidents where developers unknowingly expose sensitive data

Changes

This PR makes the SDK secure-by-default by changing the default value from to :

1. src/agents/run_config.py: Changed environment variable default from to
2. src/agents/voice/pipeline_config.py: Changed default from to with improved documentation
3. tests/test_run_config.py: Updated test expectations to reflect new secure-by-default behavior

Impact

• Breaking change: Users relying on the old default will need to explicitly opt-in by setting or passing to their config
• Security improvement: Prevents accidental exposure of sensitive data in production deployments
• Total diff: ~15 lines changed (well within the 10-100 line limit)

Migration for existing users

Users who want to maintain the previous behavior can:

This change aligns with security best practices and protects users from unintentional data exposure.