fix(server-utils): Ensure all orchestrion instrumentation lazy registers

[isaacs]

This ports and refactors the intent of #22387, using the mechanisms landed on develop in #22094, rather than the mechanisms in #22386 which are similar in intent, but substantially different in implementation.

The difference from #22387 is entirely in the plumbing underneath the helper. The way that "is my module injected?" and "tell me when it gets injected" are answered, both now use the machinery that already landed.

Beyond that, the actual registration, event emitting, double-wrap guard, and integration refactoring, should all look very familiar.

[github-actions]

size-limit report 📦

Path	Size	% Change	Change
@sentry/browser	27.95 kB	-	-
@sentry/browser - with treeshaking flags	26.39 kB	-	-
@sentry/browser (incl. Tracing)	46.41 kB	-	-
@sentry/browser (incl. Tracing + Span Streaming)	48.18 kB	-	-
@sentry/browser (incl. Tracing, Profiling)	51.21 kB	-	-
@sentry/browser (incl. Tracing, Replay)	85.69 kB	-	-
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	75.33 kB	-	-
@sentry/browser (incl. Tracing, Replay with Canvas)	90.4 kB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback)	103.06 kB	-	-
@sentry/browser (incl. Feedback)	45.13 kB	-	-
@sentry/browser (incl. sendFeedback)	32.74 kB	-	-
@sentry/browser (incl. FeedbackAsync)	37.8 kB	-	-
@sentry/browser (incl. Metrics)	29.04 kB	-	-
@sentry/browser (incl. Logs)	29.26 kB	-	-
@sentry/browser (incl. Metrics & Logs)	29.97 kB	-	-
@sentry/react	29.75 kB	-	-
@sentry/react (incl. Tracing)	48.71 kB	-	-
@sentry/vue	33.38 kB	-	-
@sentry/vue (incl. Tracing)	48.4 kB	-	-
@sentry/svelte	27.97 kB	-	-
CDN Bundle	30.28 kB	-	-
CDN Bundle (incl. Tracing)	48.26 kB	-	-
CDN Bundle (incl. Logs, Metrics)	31.85 kB	-	-
CDN Bundle (incl. Tracing, Logs, Metrics)	49.58 kB	-	-
CDN Bundle (incl. Replay, Logs, Metrics)	71.13 kB	-	-
CDN Bundle (incl. Tracing, Replay)	85.83 kB	-	-
CDN Bundle (incl. Tracing, Replay, Logs, Metrics)	87.14 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback)	91.6 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics)	92.89 kB	-	-
CDN Bundle - uncompressed	90.15 kB	-	-
CDN Bundle (incl. Tracing) - uncompressed	145.22 kB	-	-
CDN Bundle (incl. Logs, Metrics) - uncompressed	94.86 kB	-	-
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed	149.2 kB	-	-
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed	219.62 kB	-	-
CDN Bundle (incl. Tracing, Replay) - uncompressed	264.46 kB	-	-
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed	268.42 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	278.16 kB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed	282.11 kB	-	-
@sentry/nextjs (client)	51.24 kB	-	-
@sentry/sveltekit (client)	46.84 kB	-	-
@sentry/core/server	80.05 kB	-	-
@sentry/core/browser	52.01 kB	-	-
@sentry/node	123.14 kB	-	-
@sentry/node (incl. diagnostics channel injection)	167.41 kB	+0.16%	+267 B 🔺
@sentry/node/import (ESM hook with diagnostics-channel injection)	166 B	-	-
@sentry/node - without tracing	73.3 kB	-0.01%	-2 B 🔽
@sentry/aws-serverless	82.81 kB	-0.01%	-1 B 🔽
@sentry/cloudflare (withSentry) - minified	197.05 kB	-	-
@sentry/cloudflare (withSentry)	484.73 kB	-	-

View base workflow run

[isaacs]

Going to port this atop #22443 once that lands, since there are some conflicts.

---

UPDATE: this is now done. Single commit can base cleanly on develop if CI goes green and reviewers approve.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d48f476. Configure here.}

[sentry]

Bug: When using multiple Sentry clients, the langChainChannelIntegration only applies options from the first client. Subsequent client configurations are ignored due to a global instrumentation guard.
_{Severity: MEDIUM}

Suggested Fix

The instrumentation guard should be scoped per-client or per-integration instance rather than globally on the callback function reference. This would allow instrumentChatModels and instrumentEmbeddings to be re-invoked with different options for each distinct Sentry client, respecting their individual configurations.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: packages/server-utils/src/integrations/tracing-channel/langchain.ts#L56-L61

Potential issue: When multiple Sentry clients are initialized with different
`LangChainOptions`, only the options from the first client are actually used. This
occurs because the instrumentation functions, `instrumentChatModels` and
`instrumentEmbeddings`, are marked with a global `INSTRUMENTED` guard after being called
for the first client. When a second client is initialized, the
`invokeOrchestrionInstrumentation` function sees this global guard and exits early,
preventing the new options from being applied. As a result, all subsequent LangChain
instrumentation incorrectly uses the configuration from the first client, breaking the
expected per-client setup behavior.