v0.5.44

Highlights

OTLP traces sent as JSON with base64 ids now link to their audit request.

• The OTLP/JSON spec encodes trace and span ids as hex. Some exporters send protobuf's JSON mapping instead, with base64 ids. Studio stored those ids as they arrived, so the spans never matched the request's traceparent: the connection page's Test OTLP reported "no trace reached Studio" even though spans were arriving, and audits could not pick up the target's spans. The receiver now converts base64 ids to hex; hex ids are unchanged.
• Copy env vars on an OTLP credential now sets OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf (was http/json). It is the OpenTelemetry default, and the Python and JavaScript SDKs export it without a custom exporter. The receiver still accepts both formats, so existing targets need no change.