Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(sentry): propagate distributed trace headers from renderer to thv

The hey-api client routes API requests through ipcFetch (Electron IPC →
UNIX socket / named pipe) instead of window.fetch, so Sentry browser
tracing cannot auto-inject trace headers on outgoing requests. Inject
them manually in the renderer using Sentry.getTraceData with
propagateTraceparent: true so the W3C traceparent header is emitted
alongside sentry-trace / baggage — thv API server uses otelhttp which
reads traceparent.

In the main process, wrap the socket call in Sentry.suppressTracing to
keep @sentry/node httpIntegration from replacing the renderer headers
with main own (parentless) trace context.