Yichen Jiang 13daefe073 revert(session-telemetry-otel): leave telemetry on its own transport ...

Telemetry was the only call site this PR could not cover without changing
the SDK transport underneath it, and both ways of doing that cost more
than the channel is worth.

Routing an `http.Agent` needs Node's `proxyEnv`, added in 22.21 and 24.5
— inside the engines range, so three supported runtimes stayed direct
anyway, and the proxy package had to keep a `createNodeHttpAgent` export
for a path that only sometimes worked. Replacing the transport with the
SDK's `fetch` delegate covered every runtime but has no compression,
while the shipped `base` bundle enables gzip and a realistic OTLP batch
is 6.4x smaller with it; keeping both meant gzipping at the serializer,
which put transport code inside a telemetry plugin.

Telemetry is the one outbound channel whose loss costs the user nothing:
no tool, model request, or session depends on it, and an export that
cannot connect is already dropped silently. A user behind a mandatory
proxy is left where they were rather than regressed.

`src/index.ts`, `otel.spec.ts`, and `tsconfig.json` return to their state
on master; the package keeps only a dev dependency on the proxy library.
`egress.spec.ts` inverts: it installs a policy and asserts the fake proxy
saw nothing, so an SDK upgrade that moved the exporter onto `fetch` would
surface as a failing test rather than silently routing telemetry.

2026-09-01 21:51:29 +08:00

..

develop

docs: describe runtime dependency ownership

2026-08-30 02:29:53 +08:00

guide

revert(session-telemetry-otel): leave telemetry on its own transport

2026-09-01 21:51:29 +08:00

index.i18n.yaml

Route documentation home to quick start

2026-08-11 17:50:37 +08:00

index.md

Route documentation home to quick start

2026-08-11 17:50:37 +08:00

index.zh.md

Route documentation home to quick start

2026-08-11 17:50:37 +08:00