@sentry/cloudflare: stubs from namespace.jurisdiction() bypass Durable Object instrumentation

从 packages/cloudflare/src/instrumentations/instrumentDurableObjectNamespace.ts 开始，其中 get trap 当前将 get 和 getByName 作为特殊情况处理。跟踪其他 namespace 函数的绑定方式，然后验证 jurisdiction() 是否返回一个递归 instrument 的 namespace，并传播 RPC trace。完成的标准是：通过受 jurisdiction 限制的 namespace 获取的 stub，能够产生与直接 namespace 调用相同的 fetch span 和 sentry_rpc_meta 行为。

Environment

• @sentry/cloudflare: 10.74.0 (also present on develop and 11.0.0-beta.2)
• Caller wrapped with Sentry.withSentry(), enableRpcTracePropagation: true
• Durable Object namespace restricted to a jurisdiction (env.MY_DO.jurisdiction('eu'))

Description

instrumentDurableObjectNamespace wraps get and getByName so the returned stub gets fetch spans and
RPC trace propagation. Every other function on the namespace, including jurisdiction, goes through
value.bind(target), so a jurisdiction-restricted namespace is the raw binding. Stubs from it get
no fetch span and never append __sentry_rpc_meta__.

That applies to every Durable Object call from an app that uses data-location jurisdictions (for
example EU residency). The traces break at the Durable Object boundary. Combined with the receiver-side gap in #24443, the receiver
also loses all of its telemetry.

Reproduction

const ns = env.MY_DO.jurisdiction('eu');
const stub = ns.get(ns.idFromName('x'));
await stub.someRpcMethod('a'); // receiver sees no __sentry_rpc_meta__; no caller-side span

Compare with env.MY_DO.get(env.MY_DO.idFromName('x')), which does propagate.

Expected

jurisdiction() returns a namespace instrumented the same way, i.e.
instrumentDurableObjectNamespace(value.apply(target, args), propagateRpcTrace).

Code

packages/cloudflare/src/instrumentations/instrumentDurableObjectNamespace.ts: the get trap only
special-cases get/getByName.