fix(core): buffer chat compression telemetry until SDK is initialized

[AriaZhao-coder]

Summary

logChatCompression() in packages/core/src/telemetry/loggers.ts emitted its OpenTelemetry log record and recorded its metrics directly, bypassing the bufferTelemetryEvent() wrapper that every other logging function in the file uses.

bufferTelemetryEvent() defers telemetry emission until the OTel SDK has finished initializing. Without it, if chat compression fires before initialization completes — which is likely, since compression happens during early, history-heavy sessions — the log event and the recordChatCompressionMetrics() data point are emitted against a no-op provider and silently dropped.

Fix

Wrap the OTel emit and metrics call in bufferTelemetryEvent(), matching the established pattern (e.g. logApiResponse, logMalformedJsonResponse). The ClearcutLogger call stays outside the wrapper, unchanged — consistent with the rest of the file.

ClearcutLogger.getInstance(config)?.logChatCompressionEvent(event);
bufferTelemetryEvent(() => {
  const logger = logs.getLogger(SERVICE_NAME);
  logger.emit(logRecord);
  recordChatCompressionMetrics(config, { ... });
});

Tests

Added a regression test to the existing logChatCompression block: when the buffered callback is held back (simulating the SDK not yet initialized), the OTel emit and recordChatCompressionMetrics must not be called directly.

Verified locally (Node 20):

• The new test fails without the fix and passes with it (red/green)
• loggers.test.ts — all 53 tests pass
• prettier --check, eslint --max-warnings 0, tsc --noEmit — all clean

Fixes #23445

[github-actions]

📊 PR Size: size/S

• Lines changed: 42
• Additions: +32
• Deletions: -10
• Files changed: 2