@alwaysmeticulous/backend-recorder-workerd 2.325.0 → 2.327.0

package/dist/sidecar-client.js.map

@@ -1 +1 @@
-{"version":3,"file":"sidecar-client.js","sources":["../src/sidecar-client.ts"],"sourcesContent":["import { warnOnce } from \"./log\";\nimport {\n  type CaptureEvent,\n  type CaptureEventsPayload,\n  type OutboundFetchLookupRequest,\n  type OutboundFetchLookupResponse,\n  type ReplaySessionInfoResponse,\n  SIDECAR_EVENTS_PATH,\n  SIDECAR_PROTOCOL_VERSION,\n  SIDECAR_PROTOCOL_VERSION_HEADER,\n  SIDECAR_REPLAY_OUTBOUND_FETCH_PATH,\n  SIDECAR_REPLAY_SESSION_PATH,\n} from \"./protocol\";\n\ntype FetchFn = typeof globalThis.fetch;\n\n/**\n * Replay calls sit in the request path, unlike record mode's fire-and-forget reporting, so\n * they must be bounded: without a timeout a wedged sidecar would hang every outbound fetch\n * the app makes, and therefore the whole replay, with nothing to look at.\n */\nconst SESSION_INFO_TIMEOUT_MS = 10_000;\nconst LOOKUP_TIMEOUT_MS = 5_000;\n\n/**\n * Capture reporting is off the response path (it runs under `ctx.waitUntil`), so a timeout\n * here is not about latency the app can see — it is about not holding the request context\n * open on a sidecar that will never answer. A refused connection rejects immediately, but a\n * sidecar URL pointing at a host that drops packets rather than refusing them (a firewalled\n * container or LAN address instead of loopback) would otherwise leave the POST pending until\n * the runtime tears the context down, on every captured call.\n *\n * Generous relative to what it bounds: the sidecar is always loopback or the docker gateway\n * and answers a single small event in single-digit milliseconds, so this only ever fires on\n * a sidecar that is wedged or unreachable — never on one that is merely busy. Being generous\n * costs nothing because {@link withTimeout} clears the timer the moment the POST settles.\n */\nconst CAPTURE_POST_TIMEOUT_MS = 2_000;\n\n/** POSTs capture events to the sidecar. Never rejects — reporting failures only warn (once). */\nexport const postCaptureEvents = async (\n  fetchFn: FetchFn,\n  sidecarUrl: string,\n  events: CaptureEvent[],\n): Promise<void> => {\n  try {\n    const payload: CaptureEventsPayload = { events };\n    await withTimeout(CAPTURE_POST_TIMEOUT_MS, async (signal) => {\n      const response = await fetchFn(`${sidecarUrl}${SIDECAR_EVENTS_PATH}`, {\n        method: \"POST\",\n        headers: {\n          \"content-type\": \"application/json\",\n          [SIDECAR_PROTOCOL_VERSION_HEADER]: SIDECAR_PROTOCOL_VERSION,\n        },\n        body: JSON.stringify(payload),\n        signal,\n      });\n      if (!response.ok) {\n        warnOnce(\n          \"sidecar-rejected\",\n          `Meticulous sidecar rejected capture events (HTTP ${response.status}).`,\n        );\n      }\n      await response.arrayBuffer().catch(() => undefined);\n    });\n  } catch (error) {\n    warnOnce(\n      \"sidecar-unreachable\",\n      \"Could not reach the Meticulous backend recorder sidecar — backend session events are not being recorded.\",\n      error,\n    );\n  }\n};\n\n/**\n * Outcome of the session handshake.\n *\n * `unavailable` and `unreachable` both mean \"do not replay\", but they are kept apart\n * because only the first is a settled answer. The caller caches per isolate, and caching a\n * one-off network blip would disable mocking for the rest of the session — silently sending\n * every later outbound call to the real service.\n */\nexport type ReplaySessionInfoResult =\n  /** The sidecar holds mocks for this session. */\n  | { outcome: \"found\"; clockAnchorMs: number | undefined }\n  /** The sidecar answered and will never serve this session: no mocks, or no such route. */\n  | { outcome: \"unavailable\" }\n  /** Could not get an answer — timeout, transport error, 5xx. May succeed later. */\n  | { outcome: \"unreachable\" };\n\n/**\n * Asks whether the sidecar holds mocks for a session, and at what instant to freeze the\n * clock while serving it.\n *\n * A 404 is how a record-only sidecar answers, so it counts as a settled `unavailable` and\n * the shim degrades to pass-through against an older sidecar rather than failing.\n */\nexport const getReplaySessionInfo = async (\n  fetchFn: FetchFn,\n  sidecarUrl: string,\n  frontendSessionId: string,\n): Promise<ReplaySessionInfoResult> => {\n  const url = `${sidecarUrl}${SIDECAR_REPLAY_SESSION_PATH}?sessionId=${encodeURIComponent(\n    frontendSessionId,\n  )}`;\n  try {\n    return await withTimeout(SESSION_INFO_TIMEOUT_MS, async (signal) => {\n      const response = await fetchFn(url, {\n        headers: {\n          [SIDECAR_PROTOCOL_VERSION_HEADER]: SIDECAR_PROTOCOL_VERSION,\n        },\n        signal,\n      });\n      if (!response.ok) {\n        await response.arrayBuffer().catch(() => undefined);\n        // 4xx is the sidecar telling us something definitive — no such route (a record-only\n        // sidecar), or a protocol version it will not speak. Retrying cannot change either.\n        // 5xx may well be a sidecar still finding its feet, so leave it retryable.\n        if (response.status >= 500) {\n          warnOnce(\n            \"replay-session-unreachable\",\n            `Meticulous replay sidecar failed the replay session handshake (HTTP ${response.status}) — will retry on the next request.`,\n          );\n          return { outcome: \"unreachable\" };\n        }\n        warnOnce(\n          \"replay-session-unavailable\",\n          `Meticulous replay sidecar did not recognise the replay session route (HTTP ${response.status}) — outbound calls will not be mocked.`,\n        );\n        return { outcome: \"unavailable\" };\n      }\n      const info = (await response.json()) as ReplaySessionInfoResponse;\n      if (info.found !== true) {\n        warnOnce(\n          \"replay-session-unknown\",\n          \"Meticulous replay sidecar holds no mocks for this session — outbound calls will not be mocked.\",\n        );\n        return { outcome: \"unavailable\" };\n      }\n      return {\n        outcome: \"found\",\n        clockAnchorMs:\n          typeof info.clockAnchorMs === \"number\"\n            ? info.clockAnchorMs\n            : undefined,\n      };\n    });\n  } catch (error) {\n    warnOnce(\n      \"replay-session-unreachable\",\n      \"Could not reach the Meticulous replay sidecar — will retry on the next request.\",\n      error,\n    );\n    return { outcome: \"unreachable\" };\n  }\n};\n\n/**\n * Looks up a recorded response for one outbound call. Never rejects; returns undefined when\n * the sidecar could not be consulted, which the caller fails the request on — an unanswered\n * lookup is not evidence that a real call is safe.\n */\nexport const postOutboundFetchLookup = async (\n  fetchFn: FetchFn,\n  sidecarUrl: string,\n  payload: OutboundFetchLookupRequest,\n): Promise<OutboundFetchLookupResponse | undefined> => {\n  try {\n    return await withTimeout(LOOKUP_TIMEOUT_MS, async (signal) => {\n      const response = await fetchFn(\n        `${sidecarUrl}${SIDECAR_REPLAY_OUTBOUND_FETCH_PATH}`,\n        {\n          method: \"POST\",\n          headers: {\n            \"content-type\": \"application/json\",\n            [SIDECAR_PROTOCOL_VERSION_HEADER]: SIDECAR_PROTOCOL_VERSION,\n          },\n          body: JSON.stringify(payload),\n          signal,\n        },\n      );\n      if (!response.ok) {\n        warnOnce(\n          \"replay-lookup-rejected\",\n          `Meticulous replay sidecar rejected a mock lookup (HTTP ${response.status}).`,\n        );\n        await response.arrayBuffer().catch(() => undefined);\n        return undefined;\n      }\n      return (await response.json()) as OutboundFetchLookupResponse;\n    });\n  } catch (error) {\n    warnOnce(\n      \"replay-lookup-unreachable\",\n      \"Could not reach the Meticulous replay sidecar for a mock lookup — the call will fail.\",\n      error,\n    );\n    return undefined;\n  }\n};\n\n/**\n * Runs `send` under an abort signal that fires after `ms`, clearing the timer as soon as the\n * call settles — including the response body read, which an abort must still cut short.\n *\n * Deliberately not `AbortSignal.timeout`: its timer cannot be cancelled, and a pending timer\n * keeps workerd's request context alive. Bounding a 5ms POST at 2s would then pin the context\n * for the remaining ~2s on every captured call — worse than the unbounded wait it exists to\n * prevent, and on the healthy path rather than the broken one. `body-capture.ts` uses this\n * same clearable shape, for the same reason.\n */\nconst withTimeout = async <T>(\n  ms: number,\n  send: (signal: AbortSignal) => Promise<T>,\n): Promise<T> => {\n  const controller = new AbortController();\n  const timer = setTimeout(() => controller.abort(), ms);\n  try {\n    return await send(controller.signal);\n  } finally {\n    clearTimeout(timer);\n  }\n};\n"],"names":[],"mappings":";;;;;;;;;;AAqBA,MAAM,0BAA0B;AAChC,MAAM,oBAAoB;;;;;;;;;;;;;;AAe1B,MAAM,0BAA0B;;AAGhC,MAAa,oBAAoB,OAC/B,SACA,YACA,WACkB;AAClB,KAAI;EACF,MAAM,UAAgC,EAAE,QAAQ;AAChD,QAAM,YAAY,yBAAyB,OAAO,WAAW;GAC3D,MAAM,WAAW,MAAM,QAAQ,GAAG,aAAa,uBAAuB;IACpE,QAAQ;IACR,SAAS;KACP,gBAAgB;MACf,kCAAA;KACF;IACD,MAAM,KAAK,UAAU,QAAQ;IAC7B;IACD,CAAC;AACF,OAAI,CAAC,SAAS,GACZ,UACE,oBACA,oDAAoD,SAAS,OAAO,IACrE;AAEH,SAAM,SAAS,aAAa,CAAC,YAAY,KAAA,EAAU;IACnD;UACK,OAAO;AACd,WACE,uBACA,4GACA,MACD;;;;;;;;;;AA2BL,MAAa,uBAAuB,OAClC,SACA,YACA,sBACqC;CACrC,MAAM,MAAM,GAAG,aAAa,4BAA4B,aAAa,mBACnE,kBACD;AACD,KAAI;AACF,SAAO,MAAM,YAAY,yBAAyB,OAAO,WAAW;GAClE,MAAM,WAAW,MAAM,QAAQ,KAAK;IAClC,SAAS,GACN,kCAAA,KACF;IACD;IACD,CAAC;AACF,OAAI,CAAC,SAAS,IAAI;AAChB,UAAM,SAAS,aAAa,CAAC,YAAY,KAAA,EAAU;AAInD,QAAI,SAAS,UAAU,KAAK;AAC1B,cACE,8BACA,uEAAuE,SAAS,OAAO,qCACxF;AACD,YAAO,EAAE,SAAS,eAAe;;AAEnC,aACE,8BACA,8EAA8E,SAAS,OAAO,wCAC/F;AACD,WAAO,EAAE,SAAS,eAAe;;GAEnC,MAAM,OAAQ,MAAM,SAAS,MAAM;AACnC,OAAI,KAAK,UAAU,MAAM;AACvB,aACE,0BACA,iGACD;AACD,WAAO,EAAE,SAAS,eAAe;;AAEnC,UAAO;IACL,SAAS;IACT,eACE,OAAO,KAAK,kBAAkB,WAC1B,KAAK,gBACL,KAAA;IACP;IACD;UACK,OAAO;AACd,WACE,8BACA,mFACA,MACD;AACD,SAAO,EAAE,SAAS,eAAe;;;;;;;;AASrC,MAAa,0BAA0B,OACrC,SACA,YACA,YACqD;AACrD,KAAI;AACF,SAAO,MAAM,YAAY,mBAAmB,OAAO,WAAW;GAC5D,MAAM,WAAW,MAAM,QACrB,GAAG,aAAa,sCAChB;IACE,QAAQ;IACR,SAAS;KACP,gBAAgB;MACf,kCAAA;KACF;IACD,MAAM,KAAK,UAAU,QAAQ;IAC7B;IACD,CACF;AACD,OAAI,CAAC,SAAS,IAAI;AAChB,aACE,0BACA,0DAA0D,SAAS,OAAO,IAC3E;AACD,UAAM,SAAS,aAAa,CAAC,YAAY,KAAA,EAAU;AACnD;;AAEF,UAAQ,MAAM,SAAS,MAAM;IAC7B;UACK,OAAO;AACd,WACE,6BACA,yFACA,MACD;AACD;;;;;;;;;;;;;AAcJ,MAAM,cAAc,OAClB,IACA,SACe;CACf,MAAM,aAAa,IAAI,iBAAiB;CACxC,MAAM,QAAQ,iBAAiB,WAAW,OAAO,EAAE,GAAG;AACtD,KAAI;AACF,SAAO,MAAM,KAAK,WAAW,OAAO;WAC5B;AACR,eAAa,MAAM","debugId":"89e7f190-1d19-5653-b03e-60d14140c4fc"}
+{"version":3,"file":"sidecar-client.js","sources":["../src/sidecar-client.ts"],"sourcesContent":["import { warnOnce } from \"./log\";\nimport { getOriginalFetch } from \"./original-fetch\";\nimport {\n  type CaptureEvent,\n  type CaptureEventsPayload,\n  type OutboundFetchLookupRequest,\n  type OutboundFetchLookupResponse,\n  type ReplaySessionInfoResponse,\n  SIDECAR_EVENTS_PATH,\n  SIDECAR_PROTOCOL_VERSION,\n  SIDECAR_PROTOCOL_VERSION_HEADER,\n  SIDECAR_REPLAY_OUTBOUND_FETCH_PATH,\n  SIDECAR_REPLAY_SESSION_PATH,\n} from \"./protocol\";\nimport { sidecarFetch, type SidecarTransport } from \"./sidecar-transport\";\n\ntype FetchFn = typeof globalThis.fetch;\n\n/**\n * Replay calls sit in the request path, unlike record mode's fire-and-forget reporting, so\n * they must be bounded: without a timeout a wedged sidecar would hang every outbound fetch\n * the app makes, and therefore the whole replay, with nothing to look at.\n */\nconst SESSION_INFO_TIMEOUT_MS = 10_000;\nconst LOOKUP_TIMEOUT_MS = 5_000;\n\n/**\n * Capture reporting is off the response path (it runs under `ctx.waitUntil`), so a timeout here\n * is not about latency the app can see — it is about not holding the request context open on a\n * sidecar that will never answer. A refused connection rejects immediately, but a sidecar URL\n * pointing at a host that drops packets rather than refusing them (a firewalled container or LAN\n * address instead of loopback) would otherwise leave the POST pending until the runtime tears the\n * context down, on every captured call.\n *\n * Generous relative to what it bounds: a local sidecar answers a small batch in single-digit\n * milliseconds, so this only ever fires on one that is wedged or unreachable — never on one that\n * is merely busy. Being generous costs nothing because {@link withTimeout} clears the timer the\n * moment the POST settles.\n */\nconst CAPTURE_POST_TIMEOUT_MS = 2_000;\n\n/**\n * The same bound for a service-binding transport, where the sidecar is a Worker that hands the\n * batch to a Durable Object before answering. That object may live in another region and is\n * single-threaded, so a busy one can legitimately take far longer than a loopback process — and\n * failing the report early would drop spans a slightly longer wait would have recorded.\n * `waitUntil` allows 30s past the response, so this stays well inside its budget.\n */\nconst CAPTURE_POST_BINDING_TIMEOUT_MS = 10_000;\n\n/** POSTs capture events to the sidecar. Never rejects — reporting failures only warn (once). */\nexport const postCaptureEvents = async (\n  transport: SidecarTransport,\n  events: CaptureEvent[],\n): Promise<void> => {\n  const timeoutMs =\n    transport.kind === \"binding\"\n      ? CAPTURE_POST_BINDING_TIMEOUT_MS\n      : CAPTURE_POST_TIMEOUT_MS;\n  try {\n    const payload: CaptureEventsPayload = { events };\n    await withTimeout(timeoutMs, async (signal) => {\n      const response = await sidecarFetch(\n        transport,\n        getOriginalFetch(),\n        SIDECAR_EVENTS_PATH,\n        {\n          method: \"POST\",\n          headers: {\n            \"content-type\": \"application/json\",\n            [SIDECAR_PROTOCOL_VERSION_HEADER]: SIDECAR_PROTOCOL_VERSION,\n          },\n          body: JSON.stringify(payload),\n          signal,\n        },\n      );\n      if (!response.ok) {\n        warnOnce(\n          \"sidecar-rejected\",\n          `Meticulous sidecar rejected capture events (HTTP ${response.status}).`,\n        );\n      }\n      await response.arrayBuffer().catch(() => undefined);\n    });\n  } catch (error) {\n    warnOnce(\n      \"sidecar-unreachable\",\n      \"Could not reach the Meticulous backend recorder sidecar — backend session events are not being recorded.\",\n      error,\n    );\n  }\n};\n\n/**\n * Outcome of the session handshake.\n *\n * `unavailable` and `unreachable` both mean \"do not replay\", but they are kept apart\n * because only the first is a settled answer. The caller caches per isolate, and caching a\n * one-off network blip would disable mocking for the rest of the session — silently sending\n * every later outbound call to the real service.\n */\nexport type ReplaySessionInfoResult =\n  /** The sidecar holds mocks for this session. */\n  | { outcome: \"found\"; clockAnchorMs: number | undefined }\n  /** The sidecar answered and will never serve this session: no mocks, or no such route. */\n  | { outcome: \"unavailable\" }\n  /** Could not get an answer — timeout, transport error, 5xx. May succeed later. */\n  | { outcome: \"unreachable\" };\n\n/**\n * Asks whether the sidecar holds mocks for a session, and at what instant to freeze the\n * clock while serving it.\n *\n * A 404 is how a record-only sidecar answers, so it counts as a settled `unavailable`\n * rather than a retryable blip.\n */\nexport const getReplaySessionInfo = async (\n  fetchFn: FetchFn,\n  sidecarUrl: string,\n  frontendSessionId: string,\n): Promise<ReplaySessionInfoResult> => {\n  const url = `${sidecarUrl}${SIDECAR_REPLAY_SESSION_PATH}?sessionId=${encodeURIComponent(\n    frontendSessionId,\n  )}`;\n  try {\n    return await withTimeout(SESSION_INFO_TIMEOUT_MS, async (signal) => {\n      const response = await fetchFn(url, {\n        headers: {\n          [SIDECAR_PROTOCOL_VERSION_HEADER]: SIDECAR_PROTOCOL_VERSION,\n        },\n        signal,\n      });\n      if (!response.ok) {\n        await response.arrayBuffer().catch(() => undefined);\n        // 4xx is the sidecar telling us something definitive — no such route (a record-only\n        // sidecar), or a protocol version it will not speak. Retrying cannot change either.\n        // 5xx may well be a sidecar still finding its feet, so leave it retryable.\n        if (response.status >= 500) {\n          warnOnce(\n            \"replay-session-unreachable\",\n            `Meticulous replay sidecar failed the replay session handshake (HTTP ${response.status}) — will retry on the next request.`,\n          );\n          return { outcome: \"unreachable\" };\n        }\n        warnOnce(\n          \"replay-session-unavailable\",\n          `Meticulous replay sidecar did not recognise the replay session route (HTTP ${response.status}) — outbound calls will not be mocked.`,\n        );\n        return { outcome: \"unavailable\" };\n      }\n      const info = (await response.json()) as ReplaySessionInfoResponse;\n      if (info.found !== true) {\n        warnOnce(\n          \"replay-session-unknown\",\n          \"Meticulous replay sidecar holds no mocks for this session — outbound calls will not be mocked.\",\n        );\n        return { outcome: \"unavailable\" };\n      }\n      return {\n        outcome: \"found\",\n        clockAnchorMs:\n          typeof info.clockAnchorMs === \"number\"\n            ? info.clockAnchorMs\n            : undefined,\n      };\n    });\n  } catch (error) {\n    warnOnce(\n      \"replay-session-unreachable\",\n      \"Could not reach the Meticulous replay sidecar — will retry on the next request.\",\n      error,\n    );\n    return { outcome: \"unreachable\" };\n  }\n};\n\n/**\n * Looks up a recorded response for one outbound call. Never rejects; returns undefined when\n * the sidecar could not be consulted, which the caller fails the request on — an unanswered\n * lookup is not evidence that a real call is safe.\n */\nexport const postOutboundFetchLookup = async (\n  fetchFn: FetchFn,\n  sidecarUrl: string,\n  payload: OutboundFetchLookupRequest,\n): Promise<OutboundFetchLookupResponse | undefined> => {\n  try {\n    return await withTimeout(LOOKUP_TIMEOUT_MS, async (signal) => {\n      const response = await fetchFn(\n        `${sidecarUrl}${SIDECAR_REPLAY_OUTBOUND_FETCH_PATH}`,\n        {\n          method: \"POST\",\n          headers: {\n            \"content-type\": \"application/json\",\n            [SIDECAR_PROTOCOL_VERSION_HEADER]: SIDECAR_PROTOCOL_VERSION,\n          },\n          body: JSON.stringify(payload),\n          signal,\n        },\n      );\n      if (!response.ok) {\n        warnOnce(\n          \"replay-lookup-rejected\",\n          `Meticulous replay sidecar rejected a mock lookup (HTTP ${response.status}).`,\n        );\n        await response.arrayBuffer().catch(() => undefined);\n        return undefined;\n      }\n      return (await response.json()) as OutboundFetchLookupResponse;\n    });\n  } catch (error) {\n    warnOnce(\n      \"replay-lookup-unreachable\",\n      \"Could not reach the Meticulous replay sidecar for a mock lookup — the call will fail.\",\n      error,\n    );\n    return undefined;\n  }\n};\n\n/**\n * Runs `send` under an abort signal that fires after `ms`, clearing the timer as soon as the\n * call settles — including the response body read, which an abort must still cut short.\n *\n * Deliberately not `AbortSignal.timeout`: its timer cannot be cancelled, and a pending timer\n * keeps workerd's request context alive. Bounding a 5ms POST at 2s would then pin the context\n * for the remaining ~2s on every captured call — worse than the unbounded wait it exists to\n * prevent, and on the healthy path rather than the broken one. `body-capture.ts` uses this\n * same clearable shape, for the same reason.\n */\nconst withTimeout = async <T>(\n  ms: number,\n  send: (signal: AbortSignal) => Promise<T>,\n): Promise<T> => {\n  const controller = new AbortController();\n  const timer = setTimeout(() => controller.abort(), ms);\n  try {\n    return await send(controller.signal);\n  } finally {\n    clearTimeout(timer);\n  }\n};\n"],"names":[],"mappings":";;;;;;;;;;;;AAuBA,MAAM,0BAA0B;AAChC,MAAM,oBAAoB;;;;;;;;;;;;;;AAe1B,MAAM,0BAA0B;;;;;;;;AAShC,MAAM,kCAAkC;;AAGxC,MAAa,oBAAoB,OAC/B,WACA,WACkB;CAClB,MAAM,YACJ,UAAU,SAAS,YACf,kCACA;AACN,KAAI;EACF,MAAM,UAAgC,EAAE,QAAQ;AAChD,QAAM,YAAY,WAAW,OAAO,WAAW;GAC7C,MAAM,WAAW,MAAM,aACrB,WACA,kBAAkB,EAClB,qBACA;IACE,QAAQ;IACR,SAAS;KACP,gBAAgB;MACf,kCAAA;KACF;IACD,MAAM,KAAK,UAAU,QAAQ;IAC7B;IACD,CACF;AACD,OAAI,CAAC,SAAS,GACZ,UACE,oBACA,oDAAoD,SAAS,OAAO,IACrE;AAEH,SAAM,SAAS,aAAa,CAAC,YAAY,KAAA,EAAU;IACnD;UACK,OAAO;AACd,WACE,uBACA,4GACA,MACD;;;;;;;;;;AA2BL,MAAa,uBAAuB,OAClC,SACA,YACA,sBACqC;CACrC,MAAM,MAAM,GAAG,aAAa,4BAA4B,aAAa,mBACnE,kBACD;AACD,KAAI;AACF,SAAO,MAAM,YAAY,yBAAyB,OAAO,WAAW;GAClE,MAAM,WAAW,MAAM,QAAQ,KAAK;IAClC,SAAS,GACN,kCAAA,KACF;IACD;IACD,CAAC;AACF,OAAI,CAAC,SAAS,IAAI;AAChB,UAAM,SAAS,aAAa,CAAC,YAAY,KAAA,EAAU;AAInD,QAAI,SAAS,UAAU,KAAK;AAC1B,cACE,8BACA,uEAAuE,SAAS,OAAO,qCACxF;AACD,YAAO,EAAE,SAAS,eAAe;;AAEnC,aACE,8BACA,8EAA8E,SAAS,OAAO,wCAC/F;AACD,WAAO,EAAE,SAAS,eAAe;;GAEnC,MAAM,OAAQ,MAAM,SAAS,MAAM;AACnC,OAAI,KAAK,UAAU,MAAM;AACvB,aACE,0BACA,iGACD;AACD,WAAO,EAAE,SAAS,eAAe;;AAEnC,UAAO;IACL,SAAS;IACT,eACE,OAAO,KAAK,kBAAkB,WAC1B,KAAK,gBACL,KAAA;IACP;IACD;UACK,OAAO;AACd,WACE,8BACA,mFACA,MACD;AACD,SAAO,EAAE,SAAS,eAAe;;;;;;;;AASrC,MAAa,0BAA0B,OACrC,SACA,YACA,YACqD;AACrD,KAAI;AACF,SAAO,MAAM,YAAY,mBAAmB,OAAO,WAAW;GAC5D,MAAM,WAAW,MAAM,QACrB,GAAG,aAAa,sCAChB;IACE,QAAQ;IACR,SAAS;KACP,gBAAgB;MACf,kCAAA;KACF;IACD,MAAM,KAAK,UAAU,QAAQ;IAC7B;IACD,CACF;AACD,OAAI,CAAC,SAAS,IAAI;AAChB,aACE,0BACA,0DAA0D,SAAS,OAAO,IAC3E;AACD,UAAM,SAAS,aAAa,CAAC,YAAY,KAAA,EAAU;AACnD;;AAEF,UAAQ,MAAM,SAAS,MAAM;IAC7B;UACK,OAAO;AACd,WACE,6BACA,yFACA,MACD;AACD;;;;;;;;;;;;;AAcJ,MAAM,cAAc,OAClB,IACA,SACe;CACf,MAAM,aAAa,IAAI,iBAAiB;CACxC,MAAM,QAAQ,iBAAiB,WAAW,OAAO,EAAE,GAAG;AACtD,KAAI;AACF,SAAO,MAAM,KAAK,WAAW,OAAO;WAC5B;AACR,eAAa,MAAM","debugId":"4dc68be9-c4fd-55b2-bd89-c85b8f37cd8d"}

package/dist/sidecar-transport.d.ts

@@ -0,0 +1,38 @@
+//#region src/sidecar-transport.d.ts
+/**
+ * Anything with a `fetch` — a Cloudflare service binding (`Fetcher`), or a Durable Object stub.
+ * Structural so the shim needs no `@cloudflare/workers-types` dependency.
+ */
+interface SidecarFetcher {
+  fetch: (...args: unknown[]) => Promise<Response>;
+}
+/**
+ * How capture events reach the sidecar.
+ *
+ * A local `wrangler dev` recording posts to a loopback URL. A deployed Worker cannot: there is
+ * no sidecar process at the edge, and one HTTPS round trip per event to a distant host would be
+ * both slow and a subrequest per captured call. So a deployed Worker instead talks to a
+ * Meticulous sidecar Worker in the same account through a **service binding**, which stays
+ * inside the colo and needs neither DNS nor TLS.
+ */
+type SidecarTransport = {
+  kind: "url";
+  url: string;
+} | {
+  kind: "binding";
+  fetcher: SidecarFetcher;
+  instance: object;
+};
+/**
+ * Origin the shim addresses a service-binding request to. A service binding delivers to the
+ * bound Worker whatever the host is, so only the path is load-bearing — but the URL still has to
+ * parse, and using a reserved-by-RFC TLD makes it obvious in a log that no DNS was involved.
+ */
+declare const SIDECAR_BINDING_ORIGIN = "https://meticulous-sidecar.invalid";
+/** Env key holding a service binding to the Meticulous recorder sidecar Worker. */
+declare const SIDECAR_BINDING_ENV_KEY = "METICULOUS_SIDECAR";
+/** Env key holding the URL of a local recorder sidecar process. */
+declare const SIDECAR_URL_ENV_KEY = "METICULOUS_SIDECAR_URL";
+//#endregion
+export { SIDECAR_BINDING_ENV_KEY, SIDECAR_BINDING_ORIGIN, SIDECAR_URL_ENV_KEY, SidecarFetcher, SidecarTransport };
+//# sourceMappingURL=sidecar-transport.d.ts.map

package/dist/sidecar-transport.js

@@ -0,0 +1,52 @@
+//#region src/sidecar-transport.ts
+/**
+* Origin the shim addresses a service-binding request to. A service binding delivers to the
+* bound Worker whatever the host is, so only the path is load-bearing — but the URL still has to
+* parse, and using a reserved-by-RFC TLD makes it obvious in a log that no DNS was involved.
+*/
+
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="4c3fd120-a382-55e7-8105-c6ff77ac4d6e")}catch(e){}}();
+const SIDECAR_BINDING_ORIGIN = "https://meticulous-sidecar.invalid";
+/** Env key holding a service binding to the Meticulous recorder sidecar Worker. */
+const SIDECAR_BINDING_ENV_KEY = "METICULOUS_SIDECAR";
+/** Env key holding the URL of a local recorder sidecar process. */
+const SIDECAR_URL_ENV_KEY = "METICULOUS_SIDECAR_URL";
+/** The origin the shim's own sidecar requests go to, for the self-capture guards. */
+const transportOrigin = (transport) => transport.kind === "url" ? transport.url : SIDECAR_BINDING_ORIGIN;
+/**
+* Sends one request to the sidecar, whichever transport is in use.
+*
+* `fetchFn` is the unpatched global fetch, passed in rather than imported so this module stays
+* free of the patch machinery; it is unused for a binding, whose `fetch` is its own method.
+*/
+const sidecarFetch = (transport, fetchFn, path, init) => {
+	const url = `${transportOrigin(transport)}${path}`;
+	return transport.kind === "url" ? fetchFn(url, init) : transport.fetcher.fetch(new Request(url, init));
+};
+/**
+* Picks the transport for a recording, or undefined when recording is not configured.
+*
+* A binding wins over a URL. The two are only ever both present by accident — a `.dev.vars`
+* left in an image, say — and the binding is the deliberate one: it can only exist because
+* someone added it to the wrangler configuration of this deployment.
+*/
+const resolveSidecarTransport = (options, env) => {
+	const envRecord = env !== null && typeof env === "object" ? env : {};
+	const binding = options?.sidecarBinding ?? envRecord["METICULOUS_SIDECAR"];
+	if (isFetcher(binding)) return {
+		kind: "binding",
+		fetcher: binding,
+		instance: binding
+	};
+	const rawUrl = options?.sidecarUrl ?? envRecord["METICULOUS_SIDECAR_URL"];
+	if (typeof rawUrl === "string" && rawUrl.length > 0) return {
+		kind: "url",
+		url: rawUrl.replace(/\/+$/, "")
+	};
+};
+const isFetcher = (value) => value !== null && typeof value === "object" && typeof value.fetch === "function";
+//#endregion
+export { SIDECAR_BINDING_ENV_KEY, SIDECAR_BINDING_ORIGIN, SIDECAR_URL_ENV_KEY, resolveSidecarTransport, sidecarFetch, transportOrigin };
+
+//# sourceMappingURL=sidecar-transport.js.map
+//# debugId=4c3fd120-a382-55e7-8105-c6ff77ac4d6e

package/dist/sidecar-transport.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sidecar-transport.js","sources":["../src/sidecar-transport.ts"],"sourcesContent":["/**\n * Anything with a `fetch` — a Cloudflare service binding (`Fetcher`), or a Durable Object stub.\n * Structural so the shim needs no `@cloudflare/workers-types` dependency.\n */\nexport interface SidecarFetcher {\n  fetch: (...args: unknown[]) => Promise<Response>;\n}\n\n/**\n * How capture events reach the sidecar.\n *\n * A local `wrangler dev` recording posts to a loopback URL. A deployed Worker cannot: there is\n * no sidecar process at the edge, and one HTTPS round trip per event to a distant host would be\n * both slow and a subrequest per captured call. So a deployed Worker instead talks to a\n * Meticulous sidecar Worker in the same account through a **service binding**, which stays\n * inside the colo and needs neither DNS nor TLS.\n */\nexport type SidecarTransport =\n  | { kind: \"url\"; url: string }\n  | { kind: \"binding\"; fetcher: SidecarFetcher; instance: object };\n\n/**\n * Origin the shim addresses a service-binding request to. A service binding delivers to the\n * bound Worker whatever the host is, so only the path is load-bearing — but the URL still has to\n * parse, and using a reserved-by-RFC TLD makes it obvious in a log that no DNS was involved.\n */\nexport const SIDECAR_BINDING_ORIGIN = \"https://meticulous-sidecar.invalid\";\n\n/** Env key holding a service binding to the Meticulous recorder sidecar Worker. */\nexport const SIDECAR_BINDING_ENV_KEY = \"METICULOUS_SIDECAR\";\n\n/** Env key holding the URL of a local recorder sidecar process. */\nexport const SIDECAR_URL_ENV_KEY = \"METICULOUS_SIDECAR_URL\";\n\n/** The origin the shim's own sidecar requests go to, for the self-capture guards. */\nexport const transportOrigin = (transport: SidecarTransport): string =>\n  transport.kind === \"url\" ? transport.url : SIDECAR_BINDING_ORIGIN;\n\n/**\n * Sends one request to the sidecar, whichever transport is in use.\n *\n * `fetchFn` is the unpatched global fetch, passed in rather than imported so this module stays\n * free of the patch machinery; it is unused for a binding, whose `fetch` is its own method.\n */\nexport const sidecarFetch = (\n  transport: SidecarTransport,\n  fetchFn: typeof globalThis.fetch,\n  path: string,\n  init: RequestInit,\n): Promise<Response> => {\n  const url = `${transportOrigin(transport)}${path}`;\n  return transport.kind === \"url\"\n    ? fetchFn(url, init)\n    : transport.fetcher.fetch(new Request(url, init));\n};\n\nexport interface ResolveSidecarOptions {\n  /** Explicit binding, taking precedence over anything found on `env`. */\n  sidecarBinding?: SidecarFetcher;\n  /** Explicit URL, taking precedence over the env var. */\n  sidecarUrl?: string;\n}\n\n/**\n * Picks the transport for a recording, or undefined when recording is not configured.\n *\n * A binding wins over a URL. The two are only ever both present by accident — a `.dev.vars`\n * left in an image, say — and the binding is the deliberate one: it can only exist because\n * someone added it to the wrangler configuration of this deployment.\n */\nexport const resolveSidecarTransport = (\n  options: ResolveSidecarOptions | undefined,\n  env: unknown,\n): SidecarTransport | undefined => {\n  const envRecord =\n    env !== null && typeof env === \"object\"\n      ? (env as Record<string, unknown>)\n      : {};\n\n  const binding = options?.sidecarBinding ?? envRecord[SIDECAR_BINDING_ENV_KEY];\n  if (isFetcher(binding)) {\n    return { kind: \"binding\", fetcher: binding, instance: binding };\n  }\n\n  const rawUrl = options?.sidecarUrl ?? envRecord[SIDECAR_URL_ENV_KEY];\n  if (typeof rawUrl === \"string\" && rawUrl.length > 0) {\n    return { kind: \"url\", url: rawUrl.replace(/\\/+$/, \"\") };\n  }\n  return undefined;\n};\n\nconst isFetcher = (value: unknown): value is SidecarFetcher & object =>\n  value !== null &&\n  typeof value === \"object\" &&\n  typeof (value as Partial<SidecarFetcher>).fetch === \"function\";\n"],"names":[],"mappings":";;;;;;;;AA0BA,MAAa,yBAAyB;;AAGtC,MAAa,0BAA0B;;AAGvC,MAAa,sBAAsB;;AAGnC,MAAa,mBAAmB,cAC9B,UAAU,SAAS,QAAQ,UAAU,MAAM;;;;;;;AAQ7C,MAAa,gBACX,WACA,SACA,MACA,SACsB;CACtB,MAAM,MAAM,GAAG,gBAAgB,UAAU,GAAG;AAC5C,QAAO,UAAU,SAAS,QACtB,QAAQ,KAAK,KAAK,GAClB,UAAU,QAAQ,MAAM,IAAI,QAAQ,KAAK,KAAK,CAAC;;;;;;;;;AAiBrD,MAAa,2BACX,SACA,QACiC;CACjC,MAAM,YACJ,QAAQ,QAAQ,OAAO,QAAQ,WAC1B,MACD,EAAE;CAER,MAAM,UAAU,SAAS,kBAAkB,UAAA;AAC3C,KAAI,UAAU,QAAQ,CACpB,QAAO;EAAE,MAAM;EAAW,SAAS;EAAS,UAAU;EAAS;CAGjE,MAAM,SAAS,SAAS,cAAc,UAAA;AACtC,KAAI,OAAO,WAAW,YAAY,OAAO,SAAS,EAChD,QAAO;EAAE,MAAM;EAAO,KAAK,OAAO,QAAQ,QAAQ,GAAG;EAAE;;AAK3D,MAAM,aAAa,UACjB,UAAU,QACV,OAAO,UAAU,YACjB,OAAQ,MAAkC,UAAU","debugId":"4c3fd120-a382-55e7-8105-c6ff77ac4d6e"}

package/dist/spans/attributes.d.ts

@@ -0,0 +1,84 @@
+//#region src/spans/attributes.d.ts
+/**
+ * Span attribute names and technology tags shared by the two recording surfaces.
+ *
+ * These live here, in the package the in-worker shim ships from, for the same reason
+ * `kv-capture.ts` does: a session recorded through workerd and one recorded through the Node
+ * recorder have to be attribute-for-attribute identical, or a recording made on one cannot be
+ * replayed by the other. `packages/backend-recorder-js/src/constants.ts` re-exports every name
+ * below, so the Node recorder keeps one import site and there is one definition.
+ */
+/** Tags which client library produced a CLIENT span. Absent on native `node:http` spans. */
+declare const CLIENT_TECHNOLOGY_ATTR = "meticulous.client_technology";
+/** Ties a backend span to the frontend session whose request produced it. */
+declare const FRONTEND_SESSION_ID_ATTR = "meticulous.frontend_session_id";
+/**
+ * Where the session id on a span came from. Absent means the browser minted it and sent it on
+ * the request, which is the normal case. `"backend"` means we minted it ourselves for a document
+ * navigation the browser could not tag (see provisional-session-id.ts), and the page may or may
+ * not have gone on to adopt it.
+ *
+ * The distinction is load-bearing for ingestion: an unadopted backend-minted id names a session
+ * that will never exist, and must be treated as *unstamped* so those spans stay eligible for
+ * time-window attachment — otherwise stamping them makes attribution worse than leaving them
+ * bare. See `hasAnySessionId` in lambda-upload-sessions.
+ */
+declare const SESSION_ID_ORIGIN_ATTR = "meticulous.session_id_origin";
+declare const SESSION_ID_ORIGIN_BACKEND = "backend";
+/**
+ * An outgoing `fetch` from a Worker. Served back on replay by a `MockStore("workerd-fetch")`
+ * living in the replay sidecar, which the in-worker shim queries over plain HTTP (workerd cannot
+ * run the Node mock instrumentations).
+ *
+ * This value travels in recorded session data, so it is a wire contract: the replay orchestrator
+ * reads it back as `WORKERD_FETCH_CLIENT_TECHNOLOGY` in `@alwaysmeticulous/api` to decide whether
+ * a recording needs a workerd replay sidecar. Keep the two in step.
+ */
+declare const CLIENT_TECHNOLOGY_WORKERD_FETCH = "workerd-fetch";
+/**
+ * A `fetch` through a Cloudflare binding — a service binding or a Durable Object stub. Recorded
+ * from two places: the in-worker shim, and `withMeticulousCloudflareEnv` in a Node process whose
+ * bindings come from wrangler's `getPlatformProxy`. Kept distinct from `workerd-fetch` because a
+ * binding call never leaves the isolate and its URL is caller-invented, so the two must never be
+ * matched against each other.
+ */
+declare const CLIENT_TECHNOLOGY_WORKERD_BINDING = "workerd-binding";
+/**
+ * An operation on a Cloudflare KV namespace binding, from the same two places. Its own technology
+ * because a KV operation is not Request/Response-shaped at all — there is no method, URL or status
+ * to match on, only a binding, an operation and a key.
+ */
+declare const CLIENT_TECHNOLOGY_WORKERD_KV = "workerd-kv";
+/**
+ * A postgres.js query, whether captured in Node (by the require hook or `withMeticulousPostgres`)
+ * or in a deployed Worker. Deliberately distinct from `postgres` (node-postgres) so the two stores
+ * never match each other's spans even though both talk to Postgres.
+ */
+declare const CLIENT_TECHNOLOGY_POSTGRES_JS = "postgres-js";
+/**
+ * The `env` key a binding call went through. Absent when the binding instance was never seen on
+ * `env` — most commonly a Durable Object stub, which `namespace.get()` returns. Shared by
+ * `fetch`-shaped binding spans and KV spans: both identify the binding this way.
+ */
+declare const WORKERD_BINDING_NAME_ATTR = "meticulous.workerd.binding";
+/** Which KV method was called: `get`, `getWithMetadata`, `put`, `delete` or `list`. */
+declare const WORKERD_KV_OPERATION_ATTR = "meticulous.workerd.kv.operation";
+/** The key operated on. Absent for `list` and for a bulk `get`, whose keys are in the args. */
+declare const WORKERD_KV_KEY_ATTR = "meticulous.workerd.kv.key";
+/** JSON of the call's arguments; a `put` value appears as null (it lives in the value attr). */
+declare const WORKERD_KV_ARGS_ATTR = "meticulous.workerd.kv.args";
+declare const WORKERD_KV_ARGS_TRUNCATED_ATTR = "meticulous.workerd.kv.args.truncated";
+/** JSON of the value a `put` wrote, with secret-looking fields redacted. */
+declare const WORKERD_KV_VALUE_ATTR = "meticulous.workerd.kv.value";
+declare const WORKERD_KV_VALUE_TRUNCATED_ATTR = "meticulous.workerd.kv.value.truncated";
+/** JSON of what the operation returned. Absent for `put`/`delete`, which return nothing. */
+declare const WORKERD_KV_RESULT_ATTR = "meticulous.workerd.kv.result";
+declare const WORKERD_KV_RESULT_TRUNCATED_ATTR = "meticulous.workerd.kv.result.truncated";
+/**
+ * Why a value is missing: `"stream"` (reading it would take the bytes from the app) or `"binary"`
+ * (skipped deliberately — KV blobs are large and not UTF-8).
+ */
+declare const WORKERD_KV_OMITTED_ATTR = "meticulous.workerd.kv.omitted";
+//#endregion
+export { CLIENT_TECHNOLOGY_ATTR, CLIENT_TECHNOLOGY_POSTGRES_JS, CLIENT_TECHNOLOGY_WORKERD_BINDING, CLIENT_TECHNOLOGY_WORKERD_FETCH, CLIENT_TECHNOLOGY_WORKERD_KV, FRONTEND_SESSION_ID_ATTR, SESSION_ID_ORIGIN_ATTR, SESSION_ID_ORIGIN_BACKEND, WORKERD_BINDING_NAME_ATTR, WORKERD_KV_ARGS_ATTR, WORKERD_KV_ARGS_TRUNCATED_ATTR, WORKERD_KV_KEY_ATTR, WORKERD_KV_OMITTED_ATTR, WORKERD_KV_OPERATION_ATTR, WORKERD_KV_RESULT_ATTR, WORKERD_KV_RESULT_TRUNCATED_ATTR, WORKERD_KV_VALUE_ATTR, WORKERD_KV_VALUE_TRUNCATED_ATTR };
+//# sourceMappingURL=attributes.d.ts.map

package/dist/spans/attributes.js

@@ -0,0 +1,88 @@
+//#region src/spans/attributes.ts
+/**
+* Span attribute names and technology tags shared by the two recording surfaces.
+*
+* These live here, in the package the in-worker shim ships from, for the same reason
+* `kv-capture.ts` does: a session recorded through workerd and one recorded through the Node
+* recorder have to be attribute-for-attribute identical, or a recording made on one cannot be
+* replayed by the other. `packages/backend-recorder-js/src/constants.ts` re-exports every name
+* below, so the Node recorder keeps one import site and there is one definition.
+*/
+/** Tags which client library produced a CLIENT span. Absent on native `node:http` spans. */
+
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="9c7bae2d-7e8a-57e2-9065-56765d8c547b")}catch(e){}}();
+const CLIENT_TECHNOLOGY_ATTR = "meticulous.client_technology";
+/** Ties a backend span to the frontend session whose request produced it. */
+const FRONTEND_SESSION_ID_ATTR = "meticulous.frontend_session_id";
+/**
+* Where the session id on a span came from. Absent means the browser minted it and sent it on
+* the request, which is the normal case. `"backend"` means we minted it ourselves for a document
+* navigation the browser could not tag (see provisional-session-id.ts), and the page may or may
+* not have gone on to adopt it.
+*
+* The distinction is load-bearing for ingestion: an unadopted backend-minted id names a session
+* that will never exist, and must be treated as *unstamped* so those spans stay eligible for
+* time-window attachment — otherwise stamping them makes attribution worse than leaving them
+* bare. See `hasAnySessionId` in lambda-upload-sessions.
+*/
+const SESSION_ID_ORIGIN_ATTR = "meticulous.session_id_origin";
+const SESSION_ID_ORIGIN_BACKEND = "backend";
+/**
+* An outgoing `fetch` from a Worker. Served back on replay by a `MockStore("workerd-fetch")`
+* living in the replay sidecar, which the in-worker shim queries over plain HTTP (workerd cannot
+* run the Node mock instrumentations).
+*
+* This value travels in recorded session data, so it is a wire contract: the replay orchestrator
+* reads it back as `WORKERD_FETCH_CLIENT_TECHNOLOGY` in `@alwaysmeticulous/api` to decide whether
+* a recording needs a workerd replay sidecar. Keep the two in step.
+*/
+const CLIENT_TECHNOLOGY_WORKERD_FETCH = "workerd-fetch";
+/**
+* A `fetch` through a Cloudflare binding — a service binding or a Durable Object stub. Recorded
+* from two places: the in-worker shim, and `withMeticulousCloudflareEnv` in a Node process whose
+* bindings come from wrangler's `getPlatformProxy`. Kept distinct from `workerd-fetch` because a
+* binding call never leaves the isolate and its URL is caller-invented, so the two must never be
+* matched against each other.
+*/
+const CLIENT_TECHNOLOGY_WORKERD_BINDING = "workerd-binding";
+/**
+* An operation on a Cloudflare KV namespace binding, from the same two places. Its own technology
+* because a KV operation is not Request/Response-shaped at all — there is no method, URL or status
+* to match on, only a binding, an operation and a key.
+*/
+const CLIENT_TECHNOLOGY_WORKERD_KV = "workerd-kv";
+/**
+* A postgres.js query, whether captured in Node (by the require hook or `withMeticulousPostgres`)
+* or in a deployed Worker. Deliberately distinct from `postgres` (node-postgres) so the two stores
+* never match each other's spans even though both talk to Postgres.
+*/
+const CLIENT_TECHNOLOGY_POSTGRES_JS = "postgres-js";
+/**
+* The `env` key a binding call went through. Absent when the binding instance was never seen on
+* `env` — most commonly a Durable Object stub, which `namespace.get()` returns. Shared by
+* `fetch`-shaped binding spans and KV spans: both identify the binding this way.
+*/
+const WORKERD_BINDING_NAME_ATTR = "meticulous.workerd.binding";
+/** Which KV method was called: `get`, `getWithMetadata`, `put`, `delete` or `list`. */
+const WORKERD_KV_OPERATION_ATTR = "meticulous.workerd.kv.operation";
+/** The key operated on. Absent for `list` and for a bulk `get`, whose keys are in the args. */
+const WORKERD_KV_KEY_ATTR = "meticulous.workerd.kv.key";
+/** JSON of the call's arguments; a `put` value appears as null (it lives in the value attr). */
+const WORKERD_KV_ARGS_ATTR = "meticulous.workerd.kv.args";
+const WORKERD_KV_ARGS_TRUNCATED_ATTR = "meticulous.workerd.kv.args.truncated";
+/** JSON of the value a `put` wrote, with secret-looking fields redacted. */
+const WORKERD_KV_VALUE_ATTR = "meticulous.workerd.kv.value";
+const WORKERD_KV_VALUE_TRUNCATED_ATTR = "meticulous.workerd.kv.value.truncated";
+/** JSON of what the operation returned. Absent for `put`/`delete`, which return nothing. */
+const WORKERD_KV_RESULT_ATTR = "meticulous.workerd.kv.result";
+const WORKERD_KV_RESULT_TRUNCATED_ATTR = "meticulous.workerd.kv.result.truncated";
+/**
+* Why a value is missing: `"stream"` (reading it would take the bytes from the app) or `"binary"`
+* (skipped deliberately — KV blobs are large and not UTF-8).
+*/
+const WORKERD_KV_OMITTED_ATTR = "meticulous.workerd.kv.omitted";
+//#endregion
+export { CLIENT_TECHNOLOGY_ATTR, CLIENT_TECHNOLOGY_POSTGRES_JS, CLIENT_TECHNOLOGY_WORKERD_BINDING, CLIENT_TECHNOLOGY_WORKERD_FETCH, CLIENT_TECHNOLOGY_WORKERD_KV, FRONTEND_SESSION_ID_ATTR, SESSION_ID_ORIGIN_ATTR, SESSION_ID_ORIGIN_BACKEND, WORKERD_BINDING_NAME_ATTR, WORKERD_KV_ARGS_ATTR, WORKERD_KV_ARGS_TRUNCATED_ATTR, WORKERD_KV_KEY_ATTR, WORKERD_KV_OMITTED_ATTR, WORKERD_KV_OPERATION_ATTR, WORKERD_KV_RESULT_ATTR, WORKERD_KV_RESULT_TRUNCATED_ATTR, WORKERD_KV_VALUE_ATTR, WORKERD_KV_VALUE_TRUNCATED_ATTR };
+
+//# sourceMappingURL=attributes.js.map
+//# debugId=9c7bae2d-7e8a-57e2-9065-56765d8c547b

package/dist/spans/attributes.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"attributes.js","sources":["../../src/spans/attributes.ts"],"sourcesContent":["/**\n * Span attribute names and technology tags shared by the two recording surfaces.\n *\n * These live here, in the package the in-worker shim ships from, for the same reason\n * `kv-capture.ts` does: a session recorded through workerd and one recorded through the Node\n * recorder have to be attribute-for-attribute identical, or a recording made on one cannot be\n * replayed by the other. `packages/backend-recorder-js/src/constants.ts` re-exports every name\n * below, so the Node recorder keeps one import site and there is one definition.\n */\n\n/** Tags which client library produced a CLIENT span. Absent on native `node:http` spans. */\nexport const CLIENT_TECHNOLOGY_ATTR = \"meticulous.client_technology\";\n\n/** Ties a backend span to the frontend session whose request produced it. */\nexport const FRONTEND_SESSION_ID_ATTR = \"meticulous.frontend_session_id\";\n\n/**\n * Where the session id on a span came from. Absent means the browser minted it and sent it on\n * the request, which is the normal case. `\"backend\"` means we minted it ourselves for a document\n * navigation the browser could not tag (see provisional-session-id.ts), and the page may or may\n * not have gone on to adopt it.\n *\n * The distinction is load-bearing for ingestion: an unadopted backend-minted id names a session\n * that will never exist, and must be treated as *unstamped* so those spans stay eligible for\n * time-window attachment — otherwise stamping them makes attribution worse than leaving them\n * bare. See `hasAnySessionId` in lambda-upload-sessions.\n */\nexport const SESSION_ID_ORIGIN_ATTR = \"meticulous.session_id_origin\";\nexport const SESSION_ID_ORIGIN_BACKEND = \"backend\";\n\n/**\n * An outgoing `fetch` from a Worker. Served back on replay by a `MockStore(\"workerd-fetch\")`\n * living in the replay sidecar, which the in-worker shim queries over plain HTTP (workerd cannot\n * run the Node mock instrumentations).\n *\n * This value travels in recorded session data, so it is a wire contract: the replay orchestrator\n * reads it back as `WORKERD_FETCH_CLIENT_TECHNOLOGY` in `@alwaysmeticulous/api` to decide whether\n * a recording needs a workerd replay sidecar. Keep the two in step.\n */\nexport const CLIENT_TECHNOLOGY_WORKERD_FETCH = \"workerd-fetch\";\n\n/**\n * A `fetch` through a Cloudflare binding — a service binding or a Durable Object stub. Recorded\n * from two places: the in-worker shim, and `withMeticulousCloudflareEnv` in a Node process whose\n * bindings come from wrangler's `getPlatformProxy`. Kept distinct from `workerd-fetch` because a\n * binding call never leaves the isolate and its URL is caller-invented, so the two must never be\n * matched against each other.\n */\nexport const CLIENT_TECHNOLOGY_WORKERD_BINDING = \"workerd-binding\";\n\n/**\n * An operation on a Cloudflare KV namespace binding, from the same two places. Its own technology\n * because a KV operation is not Request/Response-shaped at all — there is no method, URL or status\n * to match on, only a binding, an operation and a key.\n */\nexport const CLIENT_TECHNOLOGY_WORKERD_KV = \"workerd-kv\";\n\n/**\n * A postgres.js query, whether captured in Node (by the require hook or `withMeticulousPostgres`)\n * or in a deployed Worker. Deliberately distinct from `postgres` (node-postgres) so the two stores\n * never match each other's spans even though both talk to Postgres.\n */\nexport const CLIENT_TECHNOLOGY_POSTGRES_JS = \"postgres-js\";\n\n/**\n * The `env` key a binding call went through. Absent when the binding instance was never seen on\n * `env` — most commonly a Durable Object stub, which `namespace.get()` returns. Shared by\n * `fetch`-shaped binding spans and KV spans: both identify the binding this way.\n */\nexport const WORKERD_BINDING_NAME_ATTR = \"meticulous.workerd.binding\";\n\n/** Which KV method was called: `get`, `getWithMetadata`, `put`, `delete` or `list`. */\nexport const WORKERD_KV_OPERATION_ATTR = \"meticulous.workerd.kv.operation\";\n/** The key operated on. Absent for `list` and for a bulk `get`, whose keys are in the args. */\nexport const WORKERD_KV_KEY_ATTR = \"meticulous.workerd.kv.key\";\n/** JSON of the call's arguments; a `put` value appears as null (it lives in the value attr). */\nexport const WORKERD_KV_ARGS_ATTR = \"meticulous.workerd.kv.args\";\nexport const WORKERD_KV_ARGS_TRUNCATED_ATTR =\n  \"meticulous.workerd.kv.args.truncated\";\n/** JSON of the value a `put` wrote, with secret-looking fields redacted. */\nexport const WORKERD_KV_VALUE_ATTR = \"meticulous.workerd.kv.value\";\nexport const WORKERD_KV_VALUE_TRUNCATED_ATTR =\n  \"meticulous.workerd.kv.value.truncated\";\n/** JSON of what the operation returned. Absent for `put`/`delete`, which return nothing. */\nexport const WORKERD_KV_RESULT_ATTR = \"meticulous.workerd.kv.result\";\nexport const WORKERD_KV_RESULT_TRUNCATED_ATTR =\n  \"meticulous.workerd.kv.result.truncated\";\n/**\n * Why a value is missing: `\"stream\"` (reading it would take the bytes from the app) or `\"binary\"`\n * (skipped deliberately — KV blobs are large and not UTF-8).\n */\nexport const WORKERD_KV_OMITTED_ATTR = \"meticulous.workerd.kv.omitted\";\n"],"names":[],"mappings":";;;;;;;;;;;;;AAWA,MAAa,yBAAyB;;AAGtC,MAAa,2BAA2B;;;;;;;;;;;;AAaxC,MAAa,yBAAyB;AACtC,MAAa,4BAA4B;;;;;;;;;;AAWzC,MAAa,kCAAkC;;;;;;;;AAS/C,MAAa,oCAAoC;;;;;;AAOjD,MAAa,+BAA+B;;;;;;AAO5C,MAAa,gCAAgC;;;;;;AAO7C,MAAa,4BAA4B;;AAGzC,MAAa,4BAA4B;;AAEzC,MAAa,sBAAsB;;AAEnC,MAAa,uBAAuB;AACpC,MAAa,iCACX;;AAEF,MAAa,wBAAwB;AACrC,MAAa,kCACX;;AAEF,MAAa,yBAAyB;AACtC,MAAa,mCACX;;;;;AAKF,MAAa,0BAA0B","debugId":"9c7bae2d-7e8a-57e2-9065-56765d8c547b"}

package/dist/spans/readable-span.d.ts

@@ -0,0 +1,78 @@
+//#region src/spans/readable-span.d.ts
+/**
+ * The span shape both recording surfaces produce, and the serialization that turns it into the
+ * JSON a recorded session is stored as.
+ *
+ * Lives here rather than in the Node recorder because a Worker-hosted sidecar has to write the
+ * same wire format from inside workerd, where neither `@opentelemetry/api` nor the Node
+ * recorder's bundle can be loaded. `packages/backend-recorder-js/src/exporters/span-serializer.ts`
+ * re-exports all of this and layers its richer, per-instrumentation attribute types on top, so
+ * the *logic* has exactly one implementation while the documentation types stay where they are
+ * used.
+ */
+/**
+ * OpenTelemetry's `SpanKind`, inlined. The shim has no runtime dependencies — pulling in
+ * `@opentelemetry/api` for two numeric enums would put it in every customer's worker bundle.
+ */
+declare const SPAN_KIND_INTERNAL = 0;
+declare const SPAN_KIND_SERVER = 1;
+declare const SPAN_KIND_CLIENT = 2;
+/** OpenTelemetry's `SpanStatusCode`, inlined for the same reason. */
+declare const SPAN_STATUS_UNSET = 0;
+declare const SPAN_STATUS_OK = 1;
+declare const SPAN_STATUS_ERROR = 2;
+interface SpanStatus {
+  code: number;
+  message?: string;
+}
+/** `[seconds, nanoseconds]` — OpenTelemetry's `HrTime`. */
+type HrTime = [number, number];
+interface ReadableSpan {
+  name: string;
+  /**
+   * Set by the hand-built spans in `span-builder.ts`. OTel-SDK spans carry the parent in
+   * {@link ReadableSpan.parentSpanContext} instead.
+   */
+  parentSpanId?: string;
+  /**
+   * How an OTel-SDK span reports its parent since `@opentelemetry/sdk-trace-base` v2, which
+   * dropped the flat `parentSpanId` field.
+   */
+  parentSpanContext?: {
+    spanId: string;
+  };
+  kind: number;
+  status: unknown;
+  startTime: HrTime;
+  endTime: HrTime;
+  duration: HrTime;
+  attributes?: Record<string, unknown>;
+  spanContext(): {
+    traceId: string;
+    spanId: string;
+  };
+}
+/**
+ * A serialized span, with the attribute bag left open. The Node recorder narrows `attributes`
+ * to its union of per-instrumentation contracts; nothing about the wire format depends on that
+ * narrowing.
+ */
+interface SerializedSpanBase {
+  name: string;
+  traceId: string;
+  spanId: string;
+  parentSpanId: string | undefined;
+  kind: number;
+  status: unknown;
+  startTimeMs: number;
+  endTimeMs: number;
+  durationMs: number;
+  clientTechnology?: string;
+  frontendSessionId?: string;
+  attributes: Record<string, unknown>;
+}
+declare const hrTimeToMs: (hrTime: HrTime) => number;
+declare const msToHrTime: (ms: number) => HrTime;
+//#endregion
+export { HrTime, ReadableSpan, SPAN_KIND_CLIENT, SPAN_KIND_INTERNAL, SPAN_KIND_SERVER, SPAN_STATUS_ERROR, SPAN_STATUS_OK, SPAN_STATUS_UNSET, SerializedSpanBase, SpanStatus, hrTimeToMs, msToHrTime };
+//# sourceMappingURL=readable-span.d.ts.map

package/dist/spans/readable-span.js

@@ -0,0 +1,35 @@
+//#region src/spans/readable-span.ts
+/**
+* The span shape both recording surfaces produce, and the serialization that turns it into the
+* JSON a recorded session is stored as.
+*
+* Lives here rather than in the Node recorder because a Worker-hosted sidecar has to write the
+* same wire format from inside workerd, where neither `@opentelemetry/api` nor the Node
+* recorder's bundle can be loaded. `packages/backend-recorder-js/src/exporters/span-serializer.ts`
+* re-exports all of this and layers its richer, per-instrumentation attribute types on top, so
+* the *logic* has exactly one implementation while the documentation types stay where they are
+* used.
+*/
+/**
+* OpenTelemetry's `SpanKind`, inlined. The shim has no runtime dependencies — pulling in
+* `@opentelemetry/api` for two numeric enums would put it in every customer's worker bundle.
+*/
+
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="4b8da1fb-2c09-5543-acf1-a30e8b358116")}catch(e){}}();
+const SPAN_KIND_INTERNAL = 0;
+const SPAN_KIND_SERVER = 1;
+const SPAN_KIND_CLIENT = 2;
+/** OpenTelemetry's `SpanStatusCode`, inlined for the same reason. */
+const SPAN_STATUS_UNSET = 0;
+const SPAN_STATUS_OK = 1;
+const SPAN_STATUS_ERROR = 2;
+const hrTimeToMs = (hrTime) => hrTime[0] * 1e3 + hrTime[1] / 1e6;
+const msToHrTime = (ms) => {
+	const seconds = Math.floor(ms / 1e3);
+	return [seconds, Math.round((ms - seconds * 1e3) * 1e6)];
+};
+//#endregion
+export { SPAN_KIND_CLIENT, SPAN_KIND_INTERNAL, SPAN_KIND_SERVER, SPAN_STATUS_ERROR, SPAN_STATUS_OK, SPAN_STATUS_UNSET, hrTimeToMs, msToHrTime };
+
+//# sourceMappingURL=readable-span.js.map
+//# debugId=4b8da1fb-2c09-5543-acf1-a30e8b358116

package/dist/spans/readable-span.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"readable-span.js","sources":["../../src/spans/readable-span.ts"],"sourcesContent":["/**\n * The span shape both recording surfaces produce, and the serialization that turns it into the\n * JSON a recorded session is stored as.\n *\n * Lives here rather than in the Node recorder because a Worker-hosted sidecar has to write the\n * same wire format from inside workerd, where neither `@opentelemetry/api` nor the Node\n * recorder's bundle can be loaded. `packages/backend-recorder-js/src/exporters/span-serializer.ts`\n * re-exports all of this and layers its richer, per-instrumentation attribute types on top, so\n * the *logic* has exactly one implementation while the documentation types stay where they are\n * used.\n */\n\n/**\n * OpenTelemetry's `SpanKind`, inlined. The shim has no runtime dependencies — pulling in\n * `@opentelemetry/api` for two numeric enums would put it in every customer's worker bundle.\n */\nexport const SPAN_KIND_INTERNAL = 0;\nexport const SPAN_KIND_SERVER = 1;\nexport const SPAN_KIND_CLIENT = 2;\n\n/** OpenTelemetry's `SpanStatusCode`, inlined for the same reason. */\nexport const SPAN_STATUS_UNSET = 0;\nexport const SPAN_STATUS_OK = 1;\nexport const SPAN_STATUS_ERROR = 2;\n\nexport interface SpanStatus {\n  code: number;\n  message?: string;\n}\n\n/** `[seconds, nanoseconds]` — OpenTelemetry's `HrTime`. */\nexport type HrTime = [number, number];\n\nexport interface ReadableSpan {\n  name: string;\n  /**\n   * Set by the hand-built spans in `span-builder.ts`. OTel-SDK spans carry the parent in\n   * {@link ReadableSpan.parentSpanContext} instead.\n   */\n  parentSpanId?: string;\n  /**\n   * How an OTel-SDK span reports its parent since `@opentelemetry/sdk-trace-base` v2, which\n   * dropped the flat `parentSpanId` field.\n   */\n  parentSpanContext?: { spanId: string };\n  kind: number;\n  status: unknown;\n  startTime: HrTime;\n  endTime: HrTime;\n  duration: HrTime;\n  attributes?: Record<string, unknown>;\n  spanContext(): { traceId: string; spanId: string };\n}\n\n/**\n * A serialized span, with the attribute bag left open. The Node recorder narrows `attributes`\n * to its union of per-instrumentation contracts; nothing about the wire format depends on that\n * narrowing.\n */\nexport interface SerializedSpanBase {\n  name: string;\n  traceId: string;\n  spanId: string;\n  parentSpanId: string | undefined;\n  kind: number;\n  status: unknown;\n  startTimeMs: number;\n  endTimeMs: number;\n  durationMs: number;\n  clientTechnology?: string;\n  frontendSessionId?: string;\n  attributes: Record<string, unknown>;\n}\n\nexport const hrTimeToMs = (hrTime: HrTime): number =>\n  hrTime[0] * 1000 + hrTime[1] / 1e6;\n\nexport const msToHrTime = (ms: number): HrTime => {\n  const seconds = Math.floor(ms / 1000);\n  return [seconds, Math.round((ms - seconds * 1000) * 1e6)];\n};\n"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;AAgBA,MAAa,qBAAqB;AAClC,MAAa,mBAAmB;AAChC,MAAa,mBAAmB;;AAGhC,MAAa,oBAAoB;AACjC,MAAa,iBAAiB;AAC9B,MAAa,oBAAoB;AAmDjC,MAAa,cAAc,WACzB,OAAO,KAAK,MAAO,OAAO,KAAK;AAEjC,MAAa,cAAc,OAAuB;CAChD,MAAM,UAAU,KAAK,MAAM,KAAK,IAAK;AACrC,QAAO,CAAC,SAAS,KAAK,OAAO,KAAK,UAAU,OAAQ,IAAI,CAAC","debugId":"4b8da1fb-2c09-5543-acf1-a30e8b358116"}

package/dist/spans/serialize-span.d.ts

@@ -0,0 +1,14 @@
+import { ReadableSpan, SerializedSpanBase } from "./readable-span.js";
+
+//#region src/spans/serialize-span.d.ts
+/**
+ * Turns a span into the JSON shape a recorded backend session stores.
+ *
+ * Shared by the Node exporter and the Worker-hosted sidecar so the two cannot drift: ingestion
+ * and every replay mock store read these field names, and a sidecar writing a near-miss of
+ * this shape would produce recordings that load but never match.
+ */
+declare const serializeSpan: (span: ReadableSpan) => SerializedSpanBase;
+//#endregion
+export { serializeSpan };
+//# sourceMappingURL=serialize-span.d.ts.map

package/dist/spans/serialize-span.js

@@ -0,0 +1,38 @@
+
+!function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="e12748a8-3496-5830-8c8f-229beae7068b")}catch(e){}}();
+import { CLIENT_TECHNOLOGY_ATTR, FRONTEND_SESSION_ID_ATTR } from "./attributes.js";
+import { hrTimeToMs } from "./readable-span.js";
+//#region src/spans/serialize-span.ts
+/**
+* Turns a span into the JSON shape a recorded backend session stores.
+*
+* Shared by the Node exporter and the Worker-hosted sidecar so the two cannot drift: ingestion
+* and every replay mock store read these field names, and a sidecar writing a near-miss of
+* this shape would produce recordings that load but never match.
+*/
+const serializeSpan = (span) => {
+	const ctx = span.spanContext();
+	const attributes = { ...span.attributes ?? {} };
+	const clientTechnology = attributes[CLIENT_TECHNOLOGY_ATTR];
+	const frontendSessionId = attributes[FRONTEND_SESSION_ID_ATTR];
+	delete attributes[CLIENT_TECHNOLOGY_ATTR];
+	return {
+		name: span.name,
+		traceId: ctx.traceId,
+		spanId: ctx.spanId,
+		parentSpanId: span.parentSpanId ?? span.parentSpanContext?.spanId,
+		kind: span.kind,
+		status: span.status,
+		startTimeMs: hrTimeToMs(span.startTime),
+		endTimeMs: hrTimeToMs(span.endTime),
+		durationMs: hrTimeToMs(span.duration),
+		...clientTechnology ? { clientTechnology } : {},
+		...frontendSessionId ? { frontendSessionId } : {},
+		attributes
+	};
+};
+//#endregion
+export { serializeSpan };
+
+//# sourceMappingURL=serialize-span.js.map
+//# debugId=e12748a8-3496-5830-8c8f-229beae7068b

package/dist/spans/serialize-span.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"serialize-span.js","sources":["../../src/spans/serialize-span.ts"],"sourcesContent":["import { CLIENT_TECHNOLOGY_ATTR, FRONTEND_SESSION_ID_ATTR } from \"./attributes\";\nimport {\n  hrTimeToMs,\n  type ReadableSpan,\n  type SerializedSpanBase,\n} from \"./readable-span\";\n\n/**\n * Turns a span into the JSON shape a recorded backend session stores.\n *\n * Shared by the Node exporter and the Worker-hosted sidecar so the two cannot drift: ingestion\n * and every replay mock store read these field names, and a sidecar writing a near-miss of\n * this shape would produce recordings that load but never match.\n */\nexport const serializeSpan = (span: ReadableSpan): SerializedSpanBase => {\n  const ctx = span.spanContext();\n  // Copy so we never mutate the live OTel span's attributes.\n  const attributes = { ...(span.attributes ?? {}) };\n\n  const clientTechnology = attributes[CLIENT_TECHNOLOGY_ATTR] as\n    | string\n    | undefined;\n  const frontendSessionId = attributes[FRONTEND_SESSION_ID_ATTR] as\n    | string\n    | undefined;\n\n  // client_technology moves to the top level; frontend_session_id is copied (left in place for\n  // backward compatibility — see download-sessions.ts in the webapp repo).\n  delete attributes[CLIENT_TECHNOLOGY_ATTR];\n\n  return {\n    name: span.name,\n    traceId: ctx.traceId,\n    spanId: ctx.spanId,\n    parentSpanId: span.parentSpanId ?? span.parentSpanContext?.spanId,\n    kind: span.kind,\n    status: span.status,\n    startTimeMs: hrTimeToMs(span.startTime),\n    endTimeMs: hrTimeToMs(span.endTime),\n    durationMs: hrTimeToMs(span.duration),\n    // Spread conditionally so we never emit `key: undefined` (exactOptionalPropertyTypes).\n    ...(clientTechnology ? { clientTechnology } : {}),\n    ...(frontendSessionId ? { frontendSessionId } : {}),\n    attributes,\n  };\n};\n"],"names":[],"mappings":";;;;;;;;;;;;AAcA,MAAa,iBAAiB,SAA2C;CACvE,MAAM,MAAM,KAAK,aAAa;CAE9B,MAAM,aAAa,EAAE,GAAI,KAAK,cAAc,EAAE,EAAG;CAEjD,MAAM,mBAAmB,WAAW;CAGpC,MAAM,oBAAoB,WAAW;AAMrC,QAAO,WAAW;AAElB,QAAO;EACL,MAAM,KAAK;EACX,SAAS,IAAI;EACb,QAAQ,IAAI;EACZ,cAAc,KAAK,gBAAgB,KAAK,mBAAmB;EAC3D,MAAM,KAAK;EACX,QAAQ,KAAK;EACb,aAAa,WAAW,KAAK,UAAU;EACvC,WAAW,WAAW,KAAK,QAAQ;EACnC,YAAY,WAAW,KAAK,SAAS;EAErC,GAAI,mBAAmB,EAAE,kBAAkB,GAAG,EAAE;EAChD,GAAI,oBAAoB,EAAE,mBAAmB,GAAG,EAAE;EAClD;EACD","debugId":"e12748a8-3496-5830-8c8f-229beae7068b"}

package/dist/spans/span-builder.d.ts

@@ -0,0 +1,61 @@
+import { CaptureEvent } from "../protocol.js";
+import { ReadableSpan } from "./readable-span.js";
+
+//#region src/spans/span-builder.d.ts
+/**
+ * Builds spans from shim capture events.
+ *
+ * Each inbound request becomes a SERVER span and the root of its own trace; every other event of
+ * that request becomes a CLIENT span parented under it. The shim supplies the trace and
+ * server-span ids (see `CorrelatedEvent`), so building a span needs no memory of earlier events
+ * — which is what lets a Worker-hosted sidecar be evicted between two batches of one request
+ * without splitting its trace.
+ *
+ * The `requestId → ids` fallback below exists only for a shim that predates those fields. It is
+ * the reason this is a class rather than a function.
+ *
+ * Shared with the Node recorder's sidecar (`packages/backend-recorder-js/src/sidecar/`), which
+ * re-exports it: both sidecars must produce identical spans or a recording made through one
+ * cannot be replayed by the machinery built for the other.
+ */
+declare class SpanBuilder {
+  /**
+   * Legacy fallback ids, keyed by `requestId`. Outbound events usually arrive BEFORE their
+   * inbound event (the inbound is only reported once the handler completes), so an entry is
+   * created lazily on first sight from either event kind.
+   */
+  private readonly traceContexts;
+  build(event: CaptureEvent): ReadableSpan | null;
+  private buildInboundSpan;
+  private buildOutboundSpan;
+  /**
+   * A binding call. Named after the binding rather than the bare method, since the `env` key is
+   * what identifies the call — the URL is whatever the app invented.
+   */
+  private buildBindingSpan;
+  /**
+   * A KV operation. Named `kv.<binding>.<operation>` after the Prisma convention
+   * (`prisma.<model>.<operation>`) rather than the `METHOD TARGET` shape the HTTP-like spans use
+   * — nothing about a KV call is an HTTP method, and the dotted name keeps a `get` on a
+   * namespace distinguishable from a `GET` through a service binding at a glance.
+   */
+  private buildKvSpan;
+  /**
+   * A postgres.js query. Name and attributes match what the Node instrumentation emits
+   * (`postgresjs.<command>`), because the same store loads both.
+   */
+  private buildPostgresSpan;
+  private buildHttpClientSpan;
+  private buildClientSpan;
+  /**
+   * The trace and server-span ids for an event: the shim's, when it sent them, and otherwise a
+   * pair invented per `requestId` and remembered — the pre-`traceId` behaviour.
+   */
+  private resolveIds;
+  private pruneTraceContexts;
+}
+/** WebCrypto rather than `node:crypto`, so this runs in a Worker as well as in Node. */
+declare const randomHex: (bytes: number) => string;
+//#endregion
+export { SpanBuilder, randomHex };
+//# sourceMappingURL=span-builder.d.ts.map