@raindrop-ai/ai-sdk 0.0.19 → 0.0.21

package/README.md

@@ -5,6 +5,7 @@ Standalone Vercel AI SDK integration for Raindrop:
 - **Events**: sends a `track_partial` payload to `POST /v1/events/track_partial` when the model finishes
 - **Standalone traces**: ships spans directly to `POST /v1/traces` as **OTLP/HTTP JSON**
 - **No OpenTelemetry SDK init**: avoids global OTEL registration conflicts
+- **Native v7 telemetry**: opt-in callback-based integration via AI SDK v7's `TelemetryIntegration` interface (no Proxy wrapping)
 
 ## Install
 
@@ -54,6 +55,27 @@ await raindrop.users.identify({
 await raindrop.flush();
 ```
 
+### AI SDK v7+ native telemetry (opt-in)
+
+On AI SDK v7+, you can use the native `TelemetryIntegration` callback interface instead of Proxy wrapping. This avoids Proxy overhead and works with all AI SDK entry points (including `ToolLoopAgent`).
+
+```ts
+// Option A: wrap() with nativeTelemetry flag
+const { generateText } = raindrop.wrap(ai, {
+  context: { userId: "user_123" },
+  nativeTelemetry: true,
+});
+
+// Option B: direct registration (no wrap needed)
+import { registerTelemetryIntegration } from "ai";
+
+registerTelemetryIntegration(
+  raindrop.createTelemetryIntegration({ userId: "user_123" })
+);
+```
+
+Setting `nativeTelemetry: true` on pre-v7 throws a clear error. The Proxy path remains the default and supports features not yet available on the native path (`buildEvent`, output attachment extraction).
+
 If `userId` is missing from both `wrap()` context and `eventMetadata()`, the SDK logs a warning (once) and skips sending events.
 
 ## Runtime support
@@ -101,11 +123,12 @@ but it uses the same synchronous fallback described above rather than real
 
 This package is tested against multiple Vercel AI SDK versions:
 
-| Version | Status |
-|---------|--------|
-| v4.x    | ✅ Supported |
-| v5.x    | ✅ Supported |
-| v6.x    | ✅ Supported |
+| Version | Status | Integration |
+|---------|--------|-------------|
+| v4.x    | ✅ Supported | Proxy |
+| v5.x    | ✅ Supported | Proxy |
+| v6.x    | ✅ Supported | Proxy |
+| v7.x (beta) | ✅ Supported | Proxy (default) or native `TelemetryIntegration` (opt-in) |
 
 ### Version Differences Handled
 
@@ -130,10 +153,15 @@ packages/ai-sdk/
 │   │   ├── ai-sdk.v5.test.ts
 │   │   ├── wrapper.test.ts
 │   │   └── http-payloads.test.ts
-│   └── v6/                 # AI SDK v6 (pins ai@^6.0.0)
-│       ├── ai-sdk.v6.test.ts
-│       ├── wrapper.test.ts
-│       └── http-payloads.test.ts
+│   ├── v6/                 # AI SDK v6 (pins ai@^6.0.0)
+│   │   ├── ai-sdk.v6.test.ts
+│   │   ├── wrapper.test.ts
+│   │   └── http-payloads.test.ts
+│   └── v7/                 # AI SDK v7 beta (native telemetry + proxy)
+│       ├── telemetry-integration.test.ts   # Unit tests for all callbacks
+│       ├── e2e-native-telemetry.test.ts    # E2E with real AI SDK + MSW
+│       ├── e2e-subagent-nesting.test.ts    # Subagent span hierarchy
+│       └── wrapper.test.ts
 ```
 
 ### Running Tests
@@ -146,6 +174,7 @@ pnpm test
 pnpm test:v4
 pnpm test:v5
 pnpm test:v6
+pnpm test:v7
 
 # Quick smoke test (real LLM calls, single version)
 pnpm smoke:min
@@ -158,6 +187,11 @@ Each version runs:
 - **HTTP payload tests** - MSW-based payload validation for each spec version
 - **Version-specific tests** - API differences (finishReason format, usage naming)
 
+v7 additionally runs:
+- **Telemetry integration tests** - All callback lifecycles with mock shippers
+- **E2E native telemetry** - Real AI SDK v7 with MSW-intercepted payloads
+- **Subagent nesting** - Span hierarchy for nested generateText inside tool execution
+
 ## Notes
 
 - Spans include `ai.telemetry.metadata.raindrop.eventId` for correlation, and **omit** `ai.telemetry.metadata.raindrop.userId` to prevent duplicate span→event creation server-side.