chore: tighten the changeset

Author: ericallam

.changeset/chat-transport-onevent.md

@@ -2,22 +2,11 @@
 "@trigger.dev/sdk": patch
 ---
 
-Add an `onEvent` observability callback to `TriggerChatTransport` / `useTriggerChatTransport` that emits typed lifecycle events: `message-sent` and `message-send-failed` (durable send outcomes with source, duration, payload size, and the append's idempotency key), `stream-connected`, `first-chunk` and `turn-completed` (with built-in time-to-first-token and turn latency via `sinceSendMs`), and `stream-error`. Send-success metrics, TTFT, and "sent but never answered" watchdogs become a few lines of client code.
+Add an `onEvent` callback to `TriggerChatTransport` / `useTriggerChatTransport` that emits typed lifecycle events for sends, stream connects, first chunk, and turn completion. Send-success metrics, time-to-first-token, and "sent but never answered" watchdogs become a few lines of client code.
 
 ```ts
-const transport = useTriggerChatTransport({
-  task: "my-chat",
-  accessToken,
-  onEvent: (event) => {
-    if (event.type === "message-sent") {
-      metrics.timing("chat.send_duration_ms", event.durationMs);
-    }
-    if (event.type === "first-chunk") {
-      metrics.timing("chat.ttft_ms", event.sinceSendMs ?? 0);
-    }
-    if (event.type === "message-send-failed") {
-      metrics.increment("chat.send_failed", { status: event.status });
-    }
-  },
-});
+onEvent: (event) => {
+  if (event.type === "message-sent") metrics.timing("chat.send_ms", event.durationMs);
+  if (event.type === "first-chunk") metrics.timing("chat.ttft_ms", event.sinceSendMs ?? 0);
+},
 ```