The application port (best-effort-telemetry) and the feature port (feature-telemetry pipeline) each posted to TELEMETRY_ENDPOINT on their own: 20+20 sends per minute, cookies on the application side, no pagehide flush or dispose abort on the feature side, and no deadline on any fetch, so a hung collector held activeFlush forever (6.3-10). New src/adapters/telemetry/telemetry-collector.ts is the one transport: shared send-rate window (createTelemetrySendRate, now in the platform pipeline and injectable via `sendRate`), credentials "omit", cache "no-store", a per-request deadline through the kernel createAbortableOperation, and one pagehide fan-out. runtime-adapters builds one collector and passes it to both ports. Body projections are unchanged and pinned by characterization tests first. Verified: new tests in tests/unit/telemetry.test.ts (5 RED before wiring: credentials/cache, hung collector timeout, shared rate, feature pagehide flush, feature dispose abort); all gates pass except the known tests/unit/removal-fixture.test.ts (artifacts/ absent); check:adapter-inventory 137/137; FE-RB-004 drill PASS. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19 lines
615 B
TypeScript
19 lines
615 B
TypeScript
export {
|
|
createTelemetryAdapter,
|
|
MAX_TELEMETRY_QUEUE,
|
|
noOpTelemetry,
|
|
type TelemetryAdapter,
|
|
type TelemetryAdapterOptions,
|
|
} from "./best-effort-telemetry.ts";
|
|
/** Spec §24–§27. 기능 소유 텔레메트리의 수집기 전송(공급자 중립 포트 뒤). */
|
|
export {
|
|
createFeatureTelemetry,
|
|
createFetchTelemetryTransport,
|
|
} from "./feature-telemetry.ts";
|
|
/** Q-6.9-4. 두 텔레메트리 포트가 공유하는 수집기 전송(rate·타임아웃·pagehide). */
|
|
export {
|
|
createTelemetryCollector,
|
|
type TelemetryCollector,
|
|
type TelemetryCollectorOptions,
|
|
} from "./telemetry-collector.ts";
|