Request correlation and trace context propagation

[VaishnaviHire]

Description

Add request correlation and traceparent propagation so forwarded requests and subrequests share the same request-scoped context.

A single downstream request can produce multiple outbound legs, such as:

• the forwarded upstream request
• subrequests/callouts made while handling the request
• Today, X-Request-ID support exists, but there is no shared request-scoped traceparent context used consistently across forwarded requests and subrequests. This can make debugging latency or failures across Praxis, AI callouts, and backend services harder.

Proposed scope

• add a trace_context observability filter
• resolve or generate x-request-id
• validate or generate W3C traceparent
• store trace context in request extensions
• inject x-request-id and traceparent into forwarded upstream requests
• propagate the same context through the subrequest path using FrameworkHeaders
• make the default subrequest path context-aware so callsites do not manually add tracing headers

Related Updates

• proposal: Introduce Trace context Propogation enhancements#4
• feat(correlation): propagate request ID and trace context across all legs ai#654