feat(interrupts): AG-UI interrupt lifecycle overhaul (ephemeral)

.changeset/ag-ui-interrupts.md

@@ -0,0 +1,21 @@
+---
+'@tanstack/ai': minor
+'@tanstack/ai-client': minor
+'@tanstack/ai-react': minor
+'@tanstack/ai-preact': minor
+'@tanstack/ai-solid': minor
+'@tanstack/ai-vue': minor
+'@tanstack/ai-svelte': minor
+'@tanstack/ai-angular': minor
+---
+
+Adopt the AG-UI interrupt lifecycle for tool approvals, generic responses, and
+client-tool execution, with typed bound resolvers, atomic batches, and
+structured errors. Interrupts run ephemerally by resuming from the full client
+message history in a fresh child run — no persistence required.
+
+This changes native approval and client-tool streams from legacy custom events
+to snapshot-plus-`RUN_FINISHED` interrupt outcomes. Deprecated
+`pendingInterrupts`, `addToolApprovalResponse`, raw `resumeInterrupts`, and
+legacy event readers remain as limited compatibility surfaces for migration;
+`addToolResult` remains supported.

.changeset/interrupts-validation-ownership.md

@@ -0,0 +1,20 @@
+---
+'@tanstack/ai': minor
+'@tanstack/ai-client': minor
+---
+
+Interrupts: the application owns wire-schema validation, and the hashing
+dependency is gone.
+
+The library no longer transforms a generic interrupt's wire JSON Schema into a
+validator or validates the resolved value against it, on either the client or
+the server. Whatever you pass to `resolveInterrupt` (client) or send in the
+`resume` batch (server) flows through as-is. Validate it yourself if you need to
+trust it, e.g. with `z.fromJSONSchema(interrupt.responseSchema).safeParse(value)`
+on the client and your own check on the server. Validation of a tool's
+code-authored Standard Schema (`approvalSchema` / `inputSchema`) is unchanged.
+
+This drops the `ajv` and `ajv-formats` dependencies. Interrupt binding hashes and
+resolution fingerprints now use a small bundled SHA-256 instead of
+`@noble/hashes`, so that dependency is gone too. The wire hash shape
+(`sha256:<hex>`) is unchanged.