@eigenpal/docx-editor-agents 0.5.1 → 1.0.1

package/README.md

@@ -1,94 +1,126 @@
+<p align="center">
+  <a href="https://www.docx-editor.dev/">
+    <img src="https://raw.githubusercontent.com/eigenpal/docx-editor/main/assets/header.png" alt="DOCX Editor — .docx in, .docx out. Open source, agent ready, client-side." width="500" />
+  </a>
+</p>
+
+<p align="center">
+  <a href="https://www.npmjs.com/package/@eigenpal/docx-editor-agents"><img src="https://img.shields.io/npm/v/@eigenpal/docx-editor-agents.svg?style=flat-square&color=3B5BDB" alt="npm version" /></a>
+  <a href="https://www.npmjs.com/package/@eigenpal/docx-editor-agents"><img src="https://img.shields.io/npm/dm/@eigenpal/docx-editor-agents.svg?style=flat-square&color=3B5BDB" alt="npm downloads" /></a>
+  <a href="https://github.com/eigenpal/docx-editor/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-Apache_2.0-blue.svg?style=flat-square&color=3B5BDB" alt="license" /></a>
+  <a href="https://docx-editor.dev/editor"><img src="https://img.shields.io/badge/Live_Demo-3B5BDB?style=flat-square&logo=vercel&logoColor=white" alt="Demo" /></a>
+  <a href="https://www.docx-editor.dev/docs"><img src="https://img.shields.io/badge/Docs-3B5BDB?style=flat-square&logo=readthedocs&logoColor=white" alt="Documentation" /></a>
+</p>
+
 # @eigenpal/docx-editor-agents
 
-[![License: AGPL-3.0](https://img.shields.io/badge/License-AGPL--3.0-blue.svg)](./LICENSE)
+Word-like API for AI agents to review DOCX documents. Read, comment, suggest tracked changes, accept/reject. Headless, server-friendly, browser-friendly. The library you build your AI document features on top of.
 
-Word-like API for AI agents to review DOCX documents. Read, comment, suggest tracked changes, accept/reject. Headless. Server-friendly. Browser-friendly. **The library you build your AI document features on top of.**
+## Quick Start
 
 ```bash
 npm install @eigenpal/docx-editor-agents
 ```
 
-## Three ways to use this package
-
-### 1. Static review (`DocxReviewer`) — single function call against a parsed DOCX
-
 ```ts
+import { readFile, writeFile } from 'node:fs/promises';
 import { DocxReviewer } from '@eigenpal/docx-editor-agents';
 
+const buffer = await readFile('contract.docx');
 const reviewer = await DocxReviewer.fromBuffer(buffer, 'AI Reviewer');
+
 reviewer.addComment(5, 'This cap seems too low.');
 reviewer.replace(5, '$50k', '$500k');
-const output = await reviewer.toBuffer();
+
+await writeFile('contract.reviewed.docx', new Uint8Array(await reviewer.toBuffer()));
 ```
 
-Drop into a CI bot, a queue worker, a Lambda. No editor needed. ~50 KB.
+That's the static-review path: drop into a CI bot, queue worker, or Lambda. No editor needed. ~50 KB.
 
-### 2. Live editor bridge (`createEditorBridge`) — wire AI tools into a running `<DocxEditor>` instance
+## Packages
 
-```ts
-import { useAgentChat } from '@eigenpal/docx-editor-agents/bridge';
+| Package                                                                                      | Description                                                                                                                                |
+| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| [`@eigenpal/docx-editor-react`](https://www.npmjs.com/package/@eigenpal/docx-editor-react)   | <img src="https://cdn.simpleicons.org/react/61DAFB" width="20" align="middle" /> &nbsp; React adapter. Toolbar, paged editor, plugins.     |
+| [`@eigenpal/docx-editor-vue`](https://www.npmjs.com/package/@eigenpal/docx-editor-vue)       | <img src="https://cdn.simpleicons.org/vuedotjs/4FC08D" width="20" align="middle" /> &nbsp; Vue 3 adapter. Toolbar, paged editor, plugins.  |
+| [`@eigenpal/docx-editor-core`](https://www.npmjs.com/package/@eigenpal/docx-editor-core)     | Framework-agnostic core: OOXML parser, serializer, layout engine, ProseMirror schema. Depend on this if you fork the React or Vue adapter. |
+| [`@eigenpal/docx-editor-i18n`](https://www.npmjs.com/package/@eigenpal/docx-editor-i18n)     | Shared locale strings and types consumed by both adapters.                                                                                 |
+| [`@eigenpal/docx-editor-agents`](https://www.npmjs.com/package/@eigenpal/docx-editor-agents) | Agent SDK and chat UI: framework-agnostic bridge, MCP server, AI SDK adapters, plus React UI.                                              |
+
+> **Forking the adapter?** Keep your fork thin. Depend on `@eigenpal/docx-editor-core` directly so parser, serializer, and rendering fixes land in your build automatically, without backporting each upstream change by hand.
+
+## Live editor bridge
 
+Wire AI tools into a running `<DocxEditor>` so `add_comment`, `suggest_change`, `find_text` etc. show up live in the user's editor.
+
+```ts
+// React
+import { useAgentChat } from '@eigenpal/docx-editor-agents/react';
 const { executeToolCall, toolSchemas } = useAgentChat({ editorRef, author: 'Assistant' });
+
+// Vue
+import { useAgentBridge } from '@eigenpal/docx-editor-agents/vue';
+const { executeToolCall, toolSchemas } = useAgentBridge({ editorRef, author: 'Assistant' });
 ```
 
-The agent's `add_comment`, `suggest_change`, `find_text` etc. show up live in the user's editor. Used by Eigenpal's chat panel; published for anyone building an AI document UX.
+Both share the same `EditorRefLike` contract from `/bridge`, the same tool catalog, and the same `AgentMessage[]` chat shape. For other frameworks, build the bridge directly via `createEditorBridge` from `@eigenpal/docx-editor-agents/bridge`.
 
-### 3. Build your own MCP server (`McpServer` + `createReviewerBridge`) — the SaaS path
+## MCP server
 
-This is the one most teams want. The published library exposes a transport-agnostic MCP server core. **You wrap it inside your own auth, storage, and transport layer.** Stdio, HTTP-SSE, WebSocket, queue-worker — your call.
+Transport-agnostic core. Wrap it with your own auth, storage, and transport (HTTP-SSE, WebSocket, queue worker, anything).
 
 ```ts
-// Your /api/mcp/sse route — Express, Hono, Next.js, whatever
 import { McpServer, createReviewerBridge, DocxReviewer } from '@eigenpal/docx-editor-agents';
 
 app.post('/api/mcp', requireAuth, async (req, res) => {
-  // 1. Pull the DOCX from your storage (S3, Postgres bytea, etc.)
   const buffer = await loadDocxForUser(req.user, req.params.docId);
-
-  // 2. Wire it through the bridge
   const reviewer = await DocxReviewer.fromBuffer(buffer, req.user.name);
-  const bridge = createReviewerBridge(reviewer);
-  const server = new McpServer(bridge, {
-    name: 'acme-contract-review',
+  const server = new McpServer(createReviewerBridge(reviewer), {
+    name: 'acme-review',
     version: '1.0.0',
   });
 
-  // 3. Drive MCP messages over your transport. server.handle() is sync,
-  //    transport-free, and never throws.
-  const reply = server.handle(JSON.parse(req.body));
-  res.json(reply);
+  res.json(server.handle(JSON.parse(req.body))); // sync, transport-free, never throws
 
-  // 4. After the agent's done, persist the modified DOCX back to your storage.
   await saveDocxForUser(req.user, req.params.docId, await reviewer.toBuffer());
 });
 ```
 
-That's the whole shape. Ten built-in agent tools (`read_document`, `find_text`, `add_comment`, `suggest_change`, `read_comments`, `read_changes`, `reply_comment`, `resolve_comment`, `read_selection`, `scroll`) are exposed automatically through MCP `tools/list` and `tools/call`. MCP spec version: `2025-06-18`.
+Ten built-in agent tools (`read_document`, `find_text`, `add_comment`, `suggest_change`, `read_comments`, `read_changes`, `reply_comment`, `resolve_comment`, `read_selection`, `scroll`) are exposed automatically via MCP `tools/list` and `tools/call`. MCP spec version: `2025-06-18`.
 
-#### Why server-side, why not a local stdio bin?
+> A local stdio MCP bin is one-document-per-config (Claude Desktop loads its list at startup), which doesn't fit a multi-doc product. Host the server yourself with your own auth and storage.
 
-A local-installed stdio MCP server only works for one document per config — Claude Desktop loads its MCP server list at startup. That's a useless shape for a contract-review product where users have many documents. The right deployment is **a hosted MCP server you operate**, with your own auth and storage. The library gives you the engine; you bring the chassis.
+## Subpaths
 
-## Word JS API parity
+| Subpath                                      | Use when                                                       |
+| -------------------------------------------- | -------------------------------------------------------------- |
+| `@eigenpal/docx-editor-agents`               | Server-side review, library glue                               |
+| `@eigenpal/docx-editor-agents/bridge`        | Wiring AI tools into a running editor adapter                  |
+| `@eigenpal/docx-editor-agents/server`        | Backend routes needing agent tooling without the MCP transport |
+| `@eigenpal/docx-editor-agents/mcp`           | Building an MCP server (any transport)                         |
+| `@eigenpal/docx-editor-agents/ai-sdk/server` | Server-side streaming chat with the Vercel `ai` package        |
+| `@eigenpal/docx-editor-agents/react`         | React apps wiring `<DocxEditor>` to an agent                   |
+| `@eigenpal/docx-editor-agents/ai-sdk/react`  | React chat UI over the bridge                                  |
+| `@eigenpal/docx-editor-agents/vue`           | Vue apps wiring `<DocxEditor>` to an agent                     |
+| `@eigenpal/docx-editor-agents/ai-sdk/vue`    | Vue chat UI over the bridge                                    |
 
-The bridge mirrors the Office.js Word API pattern — locate a stable handle (`paraId`) first, then mutate. The parity contract is enforced at compile time:
+Each subpath tree-shakes independently. Vue and AI SDK peers are optional via `peerDependenciesMeta`.
+
+## Word API parity
+
+The bridge mirrors the Office.js Word API pattern: locate a stable handle (`paraId`) first, then mutate. The contract is type-enforced at compile time:
 
 ```ts
 import type { WordCompatBridge } from '@eigenpal/docx-editor-agents';
 ```
 
-`WordCompatBridge` is a TypeScript interface that `EditorBridge` is statically required to satisfy. If we ever drop a method that maps to a Word API call, typecheck breaks.
-
-## What's in the package
+`EditorBridge` is statically required to satisfy `WordCompatBridge`. Drop a method that maps to a Word API call and typecheck breaks.
 
-| Subpath                               | What                                                              | Use when                                                  |
-| ------------------------------------- | ----------------------------------------------------------------- | --------------------------------------------------------- |
-| `@eigenpal/docx-editor-agents`        | `DocxReviewer`, `createReviewerBridge`, agent tool catalog, types | Server-side review, building your own MCP server          |
-| `@eigenpal/docx-editor-agents/bridge` | `useAgentChat`, `createEditorBridge`, `EditorBridge` interface    | Wiring AI tools into a live `<DocxEditor>` in the browser |
-| `@eigenpal/docx-editor-agents/mcp`    | `McpServer`, JSON-RPC types, stdio adapter                        | Building an MCP server (any transport)                    |
+## Contributing
 
-Zero new runtime dependencies. Tree-shakes cleanly per subpath.
+Contributions welcome. See [CONTRIBUTING.md](https://github.com/eigenpal/docx-editor/blob/main/CONTRIBUTING.md) for setup, tests, and the one-time CLA signature.
 
-## License
+## Commercial Support
 
-[AGPL-3.0](./LICENSE) — free to use and modify, but you must open-source your code. For commercial licensing without AGPL obligations, contact [founders@eigenpal.com](mailto:founders@eigenpal.com).
+> [!TIP]
+> Questions or custom features? Email **[docx-editor@eigenpal.com](mailto:docx-editor@eigenpal.com)**.

package/dist/agent-types-C8RvQB7n.d.mts

@@ -0,0 +1,36 @@
+/**
+ * Shared agent UI types — framework-agnostic. Both React and Vue
+ * adapters (and the AI SDK adapters) consume this single declaration.
+ *
+ * Keeping the types here lets us tweak the chat schema without writing
+ * the same drift fix in four files.
+ */
+interface AgentToolCall {
+    /** Stable id for keying. */
+    id: string;
+    /** Tool name (e.g. `read_document`, `add_comment`). */
+    name: string;
+    /** JSON-able input the agent passed. Rendered in the expanded view. */
+    input?: unknown;
+    /** Result text or summary. Set after the call completes. */
+    result?: string;
+    /** Set when the call errored — surfaces in the timeline as failed. */
+    error?: string;
+    /** `running` while in flight, `done` on success, `error` on failure. */
+    status: 'running' | 'done' | 'error';
+}
+interface AgentMessage {
+    id: string;
+    role: 'user' | 'assistant';
+    text: string;
+    /**
+     * Tool calls the assistant made for this turn, in order. The timeline
+     * stays expanded while `status === 'streaming'` and auto-collapses to
+     * an "N steps" summary when the message hits `status === 'done'`.
+     */
+    toolCalls?: AgentToolCall[];
+    /** `streaming` while the model is still calling tools / writing text; `done` once the turn is final. */
+    status?: 'streaming' | 'done';
+}
+
+export type { AgentMessage as A, AgentToolCall as a };

package/dist/agent-types-C8RvQB7n.d.ts

@@ -0,0 +1,36 @@
+/**
+ * Shared agent UI types — framework-agnostic. Both React and Vue
+ * adapters (and the AI SDK adapters) consume this single declaration.
+ *
+ * Keeping the types here lets us tweak the chat schema without writing
+ * the same drift fix in four files.
+ */
+interface AgentToolCall {
+    /** Stable id for keying. */
+    id: string;
+    /** Tool name (e.g. `read_document`, `add_comment`). */
+    name: string;
+    /** JSON-able input the agent passed. Rendered in the expanded view. */
+    input?: unknown;
+    /** Result text or summary. Set after the call completes. */
+    result?: string;
+    /** Set when the call errored — surfaces in the timeline as failed. */
+    error?: string;
+    /** `running` while in flight, `done` on success, `error` on failure. */
+    status: 'running' | 'done' | 'error';
+}
+interface AgentMessage {
+    id: string;
+    role: 'user' | 'assistant';
+    text: string;
+    /**
+     * Tool calls the assistant made for this turn, in order. The timeline
+     * stays expanded while `status === 'streaming'` and auto-collapses to
+     * an "N steps" summary when the message hits `status === 'done'`.
+     */
+    toolCalls?: AgentToolCall[];
+    /** `streaming` while the model is still calling tools / writing text; `done` once the turn is final. */
+    status?: 'streaming' | 'done';
+}
+
+export type { AgentMessage as A, AgentToolCall as a };

package/dist/ai-sdk/react.d.mts

@@ -1,36 +1,36 @@
 /**
- * Vercel AI SDK adapter (React side) — opt-in.
+ * @eigenpal/docx-editor-agents/ai-sdk/react
  *
- * Use this only if you're driving the chat with `useChat` from
- * `@ai-sdk/react`. The library's `<AgentChatLog>` consumes a flat
- * `AgentMessage[]` shape; AI SDK's `useChat` produces `UIMessage[]`
- * with structured `parts`. `toAgentMessages()` is the bridge.
- */
-/**
- * Local mirror of `AgentMessage` / `AgentToolCall` from
- * `@eigenpal/docx-js-editor`. Inlined here so this subpath has zero
- * runtime/type coupling to the editor package — the shapes are
- * structurally identical, so values flow either way without casting.
+ * Vercel AI SDK adapter (React side). Opt-in.
+ *
+ * Use this if you're driving the chat with `useChat` from `@ai-sdk/react`.
+ * The library's `<AgentChatLog>` consumes a flat `AgentMessage[]` shape;
+ * AI SDK's `useChat` produces `UIMessage[]` with structured `parts`.
+ * `toAgentMessages()` is the bridge.
+ *
+ * @example
+ * ```tsx
+ * const chat = useChat({ ... });
+ * const messages = useMemo(
+ *   () => toAgentMessages(chat.messages, chat.status),
+ *   [chat.messages, chat.status]
+ * );
+ * return <AgentChatLog messages={messages} />;
+ * ```
+ *
+ * @packageDocumentation
+ * @public
  */
-interface AgentToolCall {
-    id: string;
-    name: string;
-    input?: unknown;
-    result?: string;
-    error?: string;
-    status: 'running' | 'done' | 'error';
-}
-interface AgentMessage {
-    id: string;
-    role: 'user' | 'assistant';
-    text: string;
-    toolCalls?: AgentToolCall[];
-    status?: 'streaming' | 'done';
-}
+import { A as AgentMessage } from '../agent-types-C8RvQB7n.mjs';
+export { a as AgentToolCall } from '../agent-types-C8RvQB7n.mjs';
+
 /**
- * Minimal structural shape of a Vercel AI SDK `UIMessage` — keeps the
- * `ai` package as a peer dep, not a runtime dep.
+ * Framework-agnostic Vercel AI SDK adapter logic. The React and Vue
+ * subpaths re-export from here so consumers don't have to import a
+ * cross-framework path.
  */
+
+/** Minimal structural shape of a Vercel AI SDK `UIMessage`. */
 interface AiSdkUIMessage {
     id: string;
     role: 'user' | 'assistant' | 'system';
@@ -51,17 +51,7 @@ interface AiSdkUIMessage {
  * @param uiMessages - the `messages` array from `useChat`
  * @param status - the `status` from `useChat`. The last assistant
  *   message is marked `streaming` while the chat is still in flight.
- *
- * @example
- * ```tsx
- * const chat = useChat({ ... });
- * const messages = useMemo(
- *   () => toAgentMessages(chat.messages, chat.status),
- *   [chat.messages, chat.status]
- * );
- * return <AgentChatLog messages={messages} />;
- * ```
  */
 declare function toAgentMessages(uiMessages: ReadonlyArray<AiSdkUIMessage>, status: string): AgentMessage[];
 
-export { type AgentMessage, type AgentToolCall, toAgentMessages };
+export { AgentMessage, type AiSdkUIMessage, toAgentMessages };

package/dist/ai-sdk/react.d.ts

@@ -1,36 +1,36 @@
 /**
- * Vercel AI SDK adapter (React side) — opt-in.
+ * @eigenpal/docx-editor-agents/ai-sdk/react
  *
- * Use this only if you're driving the chat with `useChat` from
- * `@ai-sdk/react`. The library's `<AgentChatLog>` consumes a flat
- * `AgentMessage[]` shape; AI SDK's `useChat` produces `UIMessage[]`
- * with structured `parts`. `toAgentMessages()` is the bridge.
- */
-/**
- * Local mirror of `AgentMessage` / `AgentToolCall` from
- * `@eigenpal/docx-js-editor`. Inlined here so this subpath has zero
- * runtime/type coupling to the editor package — the shapes are
- * structurally identical, so values flow either way without casting.
+ * Vercel AI SDK adapter (React side). Opt-in.
+ *
+ * Use this if you're driving the chat with `useChat` from `@ai-sdk/react`.
+ * The library's `<AgentChatLog>` consumes a flat `AgentMessage[]` shape;
+ * AI SDK's `useChat` produces `UIMessage[]` with structured `parts`.
+ * `toAgentMessages()` is the bridge.
+ *
+ * @example
+ * ```tsx
+ * const chat = useChat({ ... });
+ * const messages = useMemo(
+ *   () => toAgentMessages(chat.messages, chat.status),
+ *   [chat.messages, chat.status]
+ * );
+ * return <AgentChatLog messages={messages} />;
+ * ```
+ *
+ * @packageDocumentation
+ * @public
  */
-interface AgentToolCall {
-    id: string;
-    name: string;
-    input?: unknown;
-    result?: string;
-    error?: string;
-    status: 'running' | 'done' | 'error';
-}
-interface AgentMessage {
-    id: string;
-    role: 'user' | 'assistant';
-    text: string;
-    toolCalls?: AgentToolCall[];
-    status?: 'streaming' | 'done';
-}
+import { A as AgentMessage } from '../agent-types-C8RvQB7n.js';
+export { a as AgentToolCall } from '../agent-types-C8RvQB7n.js';
+
 /**
- * Minimal structural shape of a Vercel AI SDK `UIMessage` — keeps the
- * `ai` package as a peer dep, not a runtime dep.
+ * Framework-agnostic Vercel AI SDK adapter logic. The React and Vue
+ * subpaths re-export from here so consumers don't have to import a
+ * cross-framework path.
  */
+
+/** Minimal structural shape of a Vercel AI SDK `UIMessage`. */
 interface AiSdkUIMessage {
     id: string;
     role: 'user' | 'assistant' | 'system';
@@ -51,17 +51,7 @@ interface AiSdkUIMessage {
  * @param uiMessages - the `messages` array from `useChat`
  * @param status - the `status` from `useChat`. The last assistant
  *   message is marked `streaming` while the chat is still in flight.
- *
- * @example
- * ```tsx
- * const chat = useChat({ ... });
- * const messages = useMemo(
- *   () => toAgentMessages(chat.messages, chat.status),
- *   [chat.messages, chat.status]
- * );
- * return <AgentChatLog messages={messages} />;
- * ```
  */
 declare function toAgentMessages(uiMessages: ReadonlyArray<AiSdkUIMessage>, status: string): AgentMessage[];
 
-export { type AgentMessage, type AgentToolCall, toAgentMessages };
+export { AgentMessage, type AiSdkUIMessage, toAgentMessages };

package/dist/ai-sdk/react.js

@@ -1 +1 @@
-'use strict';function g(s,r){return s.map((e,a)=>{let o="",n=[];for(let t of e.parts??[])if(t.type==="text")o+=t.text??"";else if(t.type.startsWith("tool-")){let u=t.state==="output-available"?"done":t.state==="output-error"?"error":"running";n.push({id:t.toolCallId??`${e.id}-tc-${n.length}`,name:t.type.slice(5),input:t.input,result:typeof t.output=="string"?t.output:void 0,error:t.errorText,status:u});}let i=a===s.length-1,l=e.role==="assistant"&&i&&(r==="streaming"||r==="submitted");return {id:e.id,role:e.role==="user"?"user":"assistant",text:o,toolCalls:n.length>0?n:void 0,status:l?"streaming":"done"}})}exports.toAgentMessages=g;
+'use strict';function u(n,o){return n.map((e,a)=>{let r="",s=[];for(let t of e.parts??[])if(t.type==="text")r+=t.text??"";else if(t.type.startsWith("tool-")){let g=t.state==="output-available"?"done":t.state==="output-error"?"error":"running";s.push({id:t.toolCallId??`${e.id}-tc-${s.length}`,name:t.type.slice(5),input:t.input,result:typeof t.output=="string"?t.output:void 0,error:t.errorText,status:g});}let l=a===n.length-1,i=e.role==="assistant"&&l&&(o==="streaming"||o==="submitted");return {id:e.id,role:e.role==="user"?"user":"assistant",text:r,toolCalls:s.length>0?s:void 0,status:i?"streaming":"done"}})}exports.toAgentMessages=u;

package/dist/ai-sdk/react.mjs

@@ -1 +1 @@
-function g(s,r){return s.map((e,a)=>{let o="",n=[];for(let t of e.parts??[])if(t.type==="text")o+=t.text??"";else if(t.type.startsWith("tool-")){let u=t.state==="output-available"?"done":t.state==="output-error"?"error":"running";n.push({id:t.toolCallId??`${e.id}-tc-${n.length}`,name:t.type.slice(5),input:t.input,result:typeof t.output=="string"?t.output:void 0,error:t.errorText,status:u});}let i=a===s.length-1,l=e.role==="assistant"&&i&&(r==="streaming"||r==="submitted");return {id:e.id,role:e.role==="user"?"user":"assistant",text:o,toolCalls:n.length>0?n:void 0,status:l?"streaming":"done"}})}export{g as toAgentMessages};
+function u(n,o){return n.map((e,a)=>{let r="",s=[];for(let t of e.parts??[])if(t.type==="text")r+=t.text??"";else if(t.type.startsWith("tool-")){let g=t.state==="output-available"?"done":t.state==="output-error"?"error":"running";s.push({id:t.toolCallId??`${e.id}-tc-${s.length}`,name:t.type.slice(5),input:t.input,result:typeof t.output=="string"?t.output:void 0,error:t.errorText,status:g});}let l=a===n.length-1,i=e.role==="assistant"&&l&&(o==="streaming"||o==="submitted");return {id:e.id,role:e.role==="user"?"user":"assistant",text:r,toolCalls:s.length>0?s:void 0,status:i?"streaming":"done"}})}export{u as toAgentMessages};

package/dist/ai-sdk/server.d.mts

@@ -1,13 +1,48 @@
+/**
+ * @eigenpal/docx-editor-agents/ai-sdk/server
+ *
+ * Vercel AI SDK adapter (server side). Opt-in.
+ *
+ * The core toolkit is runtime-agnostic. Use this entry only if you're
+ * wiring `streamText` / `generateText` from `ai` in your route handler.
+ * For LangChain, the Anthropic SDK, or OpenAI direct, import
+ * `getToolSchemas` from `@eigenpal/docx-editor-agents/server` and shape it
+ * however your runtime expects.
+ *
+ * @example
+ * ```ts
+ * import { getAiSdkTools } from '@eigenpal/docx-editor-agents/ai-sdk/server';
+ * import { streamText, stepCountIs, convertToModelMessages } from 'ai';
+ *
+ * const tools = getAiSdkTools();
+ *
+ * export async function POST(req: Request) {
+ *   const { messages } = await req.json();
+ *   const result = streamText({
+ *     model: 'openai/gpt-4o',
+ *     messages: await convertToModelMessages(messages),
+ *     tools,
+ *     stopWhen: stepCountIs(12),
+ *   });
+ *   return result.toUIMessageStreamResponse();
+ * }
+ * ```
+ *
+ * @packageDocumentation
+ * @public
+ */
 import { Tool } from 'ai';
 
 /**
- * Vercel AI SDK adapter (server side) — opt-in.
+ * @eigenpal/docx-editor-agents/ai-sdk/server
+ *
+ * Vercel AI SDK adapter (server side). Opt-in.
  *
  * The core toolkit is runtime-agnostic. Use this entry only if you're
  * wiring `streamText` / `generateText` from `ai` in your route handler.
- * For LangChain / Anthropic SDK / OpenAI direct, import
- * `getToolSchemas` from `@eigenpal/docx-editor-agents/server` and
- * shape it however your runtime expects.
+ * For LangChain, the Anthropic SDK, or OpenAI direct, import
+ * `getToolSchemas` from `@eigenpal/docx-editor-agents/server` and shape it
+ * however your runtime expects.
  *
  * @example
  * ```ts
@@ -27,6 +62,9 @@ import { Tool } from 'ai';
  *   return result.toUIMessageStreamResponse();
  * }
  * ```
+ *
+ * @packageDocumentation
+ * @public
  */
 
 /**

package/dist/ai-sdk/server.d.ts

@@ -1,13 +1,48 @@
+/**
+ * @eigenpal/docx-editor-agents/ai-sdk/server
+ *
+ * Vercel AI SDK adapter (server side). Opt-in.
+ *
+ * The core toolkit is runtime-agnostic. Use this entry only if you're
+ * wiring `streamText` / `generateText` from `ai` in your route handler.
+ * For LangChain, the Anthropic SDK, or OpenAI direct, import
+ * `getToolSchemas` from `@eigenpal/docx-editor-agents/server` and shape it
+ * however your runtime expects.
+ *
+ * @example
+ * ```ts
+ * import { getAiSdkTools } from '@eigenpal/docx-editor-agents/ai-sdk/server';
+ * import { streamText, stepCountIs, convertToModelMessages } from 'ai';
+ *
+ * const tools = getAiSdkTools();
+ *
+ * export async function POST(req: Request) {
+ *   const { messages } = await req.json();
+ *   const result = streamText({
+ *     model: 'openai/gpt-4o',
+ *     messages: await convertToModelMessages(messages),
+ *     tools,
+ *     stopWhen: stepCountIs(12),
+ *   });
+ *   return result.toUIMessageStreamResponse();
+ * }
+ * ```
+ *
+ * @packageDocumentation
+ * @public
+ */
 import { Tool } from 'ai';
 
 /**
- * Vercel AI SDK adapter (server side) — opt-in.
+ * @eigenpal/docx-editor-agents/ai-sdk/server
+ *
+ * Vercel AI SDK adapter (server side). Opt-in.
  *
  * The core toolkit is runtime-agnostic. Use this entry only if you're
  * wiring `streamText` / `generateText` from `ai` in your route handler.
- * For LangChain / Anthropic SDK / OpenAI direct, import
- * `getToolSchemas` from `@eigenpal/docx-editor-agents/server` and
- * shape it however your runtime expects.
+ * For LangChain, the Anthropic SDK, or OpenAI direct, import
+ * `getToolSchemas` from `@eigenpal/docx-editor-agents/server` and shape it
+ * however your runtime expects.
  *
  * @example
  * ```ts
@@ -27,6 +62,9 @@ import { Tool } from 'ai';
  *   return result.toUIMessageStreamResponse();
  * }
  * ```
+ *
+ * @packageDocumentation
+ * @public
  */
 
 /**

package/dist/ai-sdk/vue.d.ts

@@ -0,0 +1,32 @@
+/**
+ * @eigenpal/docx-editor-agents/ai-sdk/vue
+ *
+ * Vercel AI SDK adapter (Vue side). Opt-in.
+ *
+ * Use this if you're driving the chat with `useChat` from `@ai-sdk/vue`.
+ * The Vue `<AgentChatLog>` consumes a flat `AgentMessage[]` shape;
+ * AI SDK's `useChat` produces `UIMessage[]` with structured `parts`.
+ * `toAgentMessages()` is the bridge.
+ *
+ * @example
+ * ```vue
+ * <script setup lang="ts">
+ * import { computed } from 'vue';
+ * import { useChat } from '@ai-sdk/vue';
+ * import { toAgentMessages } from '@eigenpal/docx-editor-agents/ai-sdk/vue';
+ * import { AgentChatLog } from '@eigenpal/docx-editor-agents/vue';
+ *
+ * const chat = useChat({ ... });
+ * const messages = computed(() => toAgentMessages(chat.messages.value, chat.status.value));
+ * </script>
+ *
+ * <template>
+ *   <AgentChatLog :messages="messages" />
+ * </template>
+ * ```
+ *
+ * @packageDocumentation
+ * @public
+ */
+export type { AgentMessage, AgentToolCall } from '../agent-types';
+export { toAgentMessages, type AiSdkUIMessage } from './shared';

package/dist/ai-sdk/vue.js

@@ -0,0 +1 @@
+"use strict";Object.defineProperty(exports,Symbol.toStringTag,{value:"Module"});function p(s,r){return s.map((e,l)=>{let n="";const o=[];for(const t of e.parts??[])if(t.type==="text")n+=t.text??"";else if(t.type.startsWith("tool-")){const u=t.state==="output-available"?"done":t.state==="output-error"?"error":"running";o.push({id:t.toolCallId??`${e.id}-tc-${o.length}`,name:t.type.slice(5),input:t.input,result:typeof t.output=="string"?t.output:void 0,error:t.errorText,status:u})}const a=l===s.length-1,i=e.role==="assistant"&&a&&(r==="streaming"||r==="submitted");return{id:e.id,role:e.role==="user"?"user":"assistant",text:n,toolCalls:o.length>0?o:void 0,status:i?"streaming":"done"}})}exports.toAgentMessages=p;

package/dist/ai-sdk/vue.mjs

@@ -0,0 +1,31 @@
+function p(s, r) {
+  return s.map((e, l) => {
+    let n = "";
+    const o = [];
+    for (const t of e.parts ?? [])
+      if (t.type === "text")
+        n += t.text ?? "";
+      else if (t.type.startsWith("tool-")) {
+        const u = t.state === "output-available" ? "done" : t.state === "output-error" ? "error" : "running";
+        o.push({
+          id: t.toolCallId ?? `${e.id}-tc-${o.length}`,
+          name: t.type.slice(5),
+          input: t.input,
+          result: typeof t.output == "string" ? t.output : void 0,
+          error: t.errorText,
+          status: u
+        });
+      }
+    const a = l === s.length - 1, i = e.role === "assistant" && a && (r === "streaming" || r === "submitted");
+    return {
+      id: e.id,
+      role: e.role === "user" ? "user" : "assistant",
+      text: n,
+      toolCalls: o.length > 0 ? o : void 0,
+      status: i ? "streaming" : "done"
+    };
+  });
+}
+export {
+  p as toAgentMessages
+};

package/dist/bridge.d.mts

@@ -1 +1,18 @@
-export { A as AgentToolDefinition, a as AgentToolResult, n as ContentChangeEvent, v as EditorBridge, E as EditorRefLike, o as SelectionChangeEvent, U as UseAgentChatOptions, c as UseAgentChatReturn, r as agentTools, w as createEditorBridge, s as createReviewerBridge, t as executeToolCall, g as getToolSchemas, u as useAgentChat } from './server-DH5eszkm.mjs';
+/**
+ * @eigenpal/docx-editor-agents/bridge
+ *
+ * Editor bridge that connects agent tools to a live `DocxEditor` instance.
+ * Framework-agnostic. The React adapter lives in
+ * `@eigenpal/docx-editor-agents/react`.
+ *
+ * @example
+ * ```ts
+ * import { createEditorBridge } from '@eigenpal/docx-editor-agents/bridge';
+ * const bridge = createEditorBridge(editorRef, 'Assistant');
+ * bridge.addComment({ paragraphIndex: 3, text: 'Fix this.' });
+ * ```
+ *
+ * @packageDocumentation
+ * @public
+ */
+export { j as AgentToolDefinition, k as AgentToolResult, h as ContentChangeEvent, E as EditorBridge, r as EditorRefLike, i as SelectionChangeEvent, n as agentTools, u as createEditorBridge, o as createReviewerBridge, p as executeToolCall, q as getToolSchemas } from './server-B7RHNVSu.mjs';