Fix NoneType decorator crash when tracing system is unavailable

[Copilot]

When tracing_system fails to import, the fallback lambdas returned None, causing a TypeError at module load time because @trace_fastapi_operation("health_check") expects the call to return a decorator, not None.

Change

server/main.py — fallback lambdas now return an identity decorator instead of None:

# Before — returns None, crashes when used as @decorator_factory(...)
trace_fastapi_operation = lambda *args, **kwargs: None

# After — returns a no-op pass-through decorator
trace_fastapi_operation = lambda *args, **kwargs: (lambda f: f)

Applied to all four tracing fallbacks: trace_consciousness_stream, trace_fastapi_operation, trace_payment_processing, trace_payment_visualization_flow.

[Copilot]

🟡 Not ready to approve

The new fallbacks return decorators for all tracing helpers, but at least one (trace_consciousness_stream) is used as a context manager (with ...:), which will still fail when tracing is unavailable.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

This PR aims to prevent module-load crashes when tracing_system can’t be imported by ensuring tracing fallbacks are safe to use (especially when used as decorator factories).

Changes:

• Updated tracing fallback callables in server/main.py to avoid returning None when tracing_system import fails.
• Intended to make @trace_fastapi_operation("...") safe even when tracing is unavailable.

File summaries

File	Description
server/main.py	Adjusts tracing fallbacks used when tracing_system import fails.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Low

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.