@eigenpal/docx-editor-agents 1.1.0 → 1.2.0

package/dist/{server-BELKcdSd.d.mts → server-uM9UUIhk.d.mts}

@@ -970,111 +970,6 @@ interface Table {
     rows: TableRow[];
 }
 
-/**
- * Structured Document Tags / content controls (`w:sdt`) — inline and
- * block variants, plus properties (alias, tag, lock, list items,
- * checkbox state) for the supported SDT types.
- */
-
-/**
- * SDT type (content control type)
- */
-type SdtType = 'richText' | 'plainText' | 'date' | 'dropdown' | 'comboBox' | 'checkbox' | 'picture' | 'buildingBlockGallery' | 'group' | 'unknown';
-/**
- * SDT properties (w:sdtPr)
- */
-interface SdtProperties {
-    /** SDT type */
-    sdtType: SdtType;
-    /** Alias (friendly name) */
-    alias?: string;
-    /** Tag (developer identifier) */
-    tag?: string;
-    /** Lock content editing */
-    lock?: 'sdtLocked' | 'contentLocked' | 'sdtContentLocked' | 'unlocked';
-    /** Placeholder text */
-    placeholder?: string;
-    /** Whether showing placeholder */
-    showingPlaceholder?: boolean;
-    /** Date format for date controls */
-    dateFormat?: string;
-    /** Dropdown/combobox list items */
-    listItems?: {
-        displayText: string;
-        value: string;
-    }[];
-    /** Checkbox checked state */
-    checked?: boolean;
-}
-/**
- * Inline SDT (content control within a paragraph)
- */
-interface InlineSdt {
-    type: 'inlineSdt';
-    /** SDT properties */
-    properties: SdtProperties;
-    /**
-     * Inline content held inside the control. OOXML allows runs,
-     * hyperlinks, simple/complex fields, nested SDTs, and math at this
-     * level; the renderer must descend into all of them so docProps-bound
-     * fields and similar template content survive paged rendering.
-     */
-    content: (Run | Hyperlink | SimpleField | ComplexField | InlineSdt | MathEquation)[];
-}
-/**
- * Block-level SDT (content control wrapping paragraphs/tables)
- */
-interface BlockSdt {
-    type: 'blockSdt';
-    /** SDT properties */
-    properties: SdtProperties;
-    /** Block content inside the control */
-    content: (Paragraph | Table)[];
-}
-
-/**
- * Comments (`w:comment` in `comments.xml`) and the inline range markers
- * (`w:commentRangeStart`/`End`) that anchor them inside paragraphs.
- */
-
-/**
- * A comment from `comments.xml` — the top-level entity for review
- * comments and replies. `id` matches the inline `CommentRangeStart` /
- * `CommentRangeEnd` markers that anchor it inside a paragraph; `parentId`
- * threads replies under their parent; `done` reflects Word's "Resolve"
- * state (`w15:done`).
- */
-interface Comment {
-    /** Comment ID (matches commentRangeStart/End) */
-    id: number;
-    /** Author name */
-    author: string;
-    /** Author initials */
-    initials?: string;
-    /** Date */
-    date?: string;
-    /** Comment content (paragraphs) */
-    content: Paragraph[];
-    /** Parent comment ID (for replies) */
-    parentId?: number;
-    /** Whether the comment is resolved/done */
-    done?: boolean;
-}
-/**
- * Comment range start marker in paragraph content
- */
-interface CommentRangeStart {
-    type: 'commentRangeStart';
-    id: number;
-}
-/**
- * Comment range end marker in paragraph content
- */
-interface CommentRangeEnd {
-    type: 'commentRangeEnd';
-    id: number;
-}
-
 /**
  * Page furniture — headers (`w:hdr`), footers (`w:ftr`), footnotes
  * (`w:footnote`), and endnotes (`w:endnote`), plus the section-level
@@ -1104,7 +999,7 @@ interface HeaderFooter {
     /** Header/footer type */
     hdrFtrType: HeaderFooterType;
     /** Content (paragraphs, tables, etc.) */
-    content: (Paragraph | Table)[];
+    content: BlockContent[];
 }
 /**
  * Footnote position
@@ -1152,7 +1047,7 @@ interface Footnote {
      * widened to match HeaderFooter / TableCell shape so the body pipeline
      * (toProseDoc → toFlowBlocks) can render them uniformly.
      */
-    content: (Paragraph | Table)[];
+    content: BlockContent[];
 }
 /**
  * Endnote (w:endnote)
@@ -1167,7 +1062,50 @@ interface Endnote {
      * Content. Per ECMA-376 §17.11.4 endnotes can hold the same blocks as
      * the body — paragraphs and tables. See note on `Footnote.content`.
      */
-    content: (Paragraph | Table)[];
+    content: BlockContent[];
+}
+
+/**
+ * Comments (`w:comment` in `comments.xml`) and the inline range markers
+ * (`w:commentRangeStart`/`End`) that anchor them inside paragraphs.
+ */
+
+/**
+ * A comment from `comments.xml` — the top-level entity for review
+ * comments and replies. `id` matches the inline `CommentRangeStart` /
+ * `CommentRangeEnd` markers that anchor it inside a paragraph; `parentId`
+ * threads replies under their parent; `done` reflects Word's "Resolve"
+ * state (`w15:done`).
+ */
+interface Comment {
+    /** Comment ID (matches commentRangeStart/End) */
+    id: number;
+    /** Author name */
+    author: string;
+    /** Author initials */
+    initials?: string;
+    /** Date */
+    date?: string;
+    /** Comment content (paragraphs) */
+    content: Paragraph[];
+    /** Parent comment ID (for replies) */
+    parentId?: number;
+    /** Whether the comment is resolved/done */
+    done?: boolean;
+}
+/**
+ * Comment range start marker in paragraph content
+ */
+interface CommentRangeStart {
+    type: 'commentRangeStart';
+    id: number;
+}
+/**
+ * Comment range end marker in paragraph content
+ */
+interface CommentRangeEnd {
+    type: 'commentRangeEnd';
+    id: number;
 }
 
 /**
@@ -1342,6 +1280,126 @@ interface DocumentBody {
     comments?: Comment[];
 }
 
+/**
+ * Structured Document Tags / content controls (`w:sdt`) — inline and
+ * block variants, plus properties (alias, tag, lock, list items,
+ * checkbox state) for the supported SDT types.
+ */
+
+/**
+ * SDT type (content control type).
+ *
+ * Values mirror the `w:sdtPr` type-marker element names from ECMA-376
+ * §17.5.2 (`CT_SdtPr`), with two deliberate exceptions:
+ * - `checkbox` is the `w14:checkbox` (Office 2010) extension, not a base
+ *   OOXML type marker.
+ * - `buildingBlockGallery` covers both `w:docPartObj` and `w:docPartList`.
+ *
+ * A `w:sdtPr` with no type marker means `richText` (the spec default). A
+ * type marker the parser does not model maps to `unknown` — it is never
+ * coerced to `richText`, so the projection stays honest. Round-trip
+ * fidelity does not depend on this enum: the raw `w:sdtPr` is replayed
+ * verbatim (see `rawPropertiesXml`).
+ */
+type SdtType = 'richText' | 'plainText' | 'date' | 'dropDownList' | 'comboBox' | 'checkbox' | 'picture' | 'buildingBlockGallery' | 'group' | 'equation' | 'citation' | 'bibliography' | 'unknown';
+/**
+ * XML data binding (`w:dataBinding`) — links a content control to a node in a
+ * Custom XML data store. Modeled read-only; the binding round-trips verbatim
+ * via `rawPropertiesXml` (this projection is for inspection, e.g. "which
+ * controls are bound, and to what XPath"). The editor does not resolve or
+ * sync bound values.
+ */
+interface SdtDataBinding {
+    /** XPath into the bound Custom XML part (`w:xpath`). */
+    xpath?: string;
+    /** Target Custom XML store id (`w:storeItemID`). */
+    storeItemID?: string;
+    /** Namespace prefix mappings used by the XPath (`w:prefixMappings`). */
+    prefixMappings?: string;
+}
+/**
+ * SDT properties (`w:sdtPr`).
+ *
+ * The modeled fields are a **read-only projection** for downstream tooling
+ * (tag/alias addressing, template extraction). They are NOT the
+ * serialization source: the original `w:sdtPr` is captured verbatim in
+ * `rawPropertiesXml` and replayed on save, which preserves element order
+ * (`CT_SdtPr` is an `xsd:sequence`), avoids double-emission, and keeps
+ * unmodeled features (data binding, `w15:*`, `@lastValue`) lossless.
+ */
+interface SdtProperties {
+    /** SDT type (projection; see {@link SdtType}). */
+    sdtType: SdtType;
+    /** Unique numeric id (`w:id`, signed). */
+    id?: number;
+    /** Alias (friendly name, `w:alias`). */
+    alias?: string;
+    /** Tag (developer identifier, `w:tag`). */
+    tag?: string;
+    /** Lock setting (`w:lock`). */
+    lock?: 'sdtLocked' | 'contentLocked' | 'sdtContentLocked' | 'unlocked';
+    /**
+     * Placeholder building-block name (`w:placeholder/w:docPart@w:val`).
+     * This is a reference to a glossary docPart that supplies the placeholder
+     * content — NOT the literal placeholder text.
+     */
+    placeholder?: string;
+    /** Whether the control is currently showing its placeholder (`w:showingPlcHdr`). */
+    showingPlaceholder?: boolean;
+    /** Date format for date controls (`w:date@w:fullDate`). */
+    dateFormat?: string;
+    /** Dropdown/combobox list items. */
+    listItems?: {
+        displayText: string;
+        value: string;
+    }[];
+    /** Checkbox checked state (`w14:checkbox`). */
+    checked?: boolean;
+    /** XML data binding (`w:dataBinding`), if the control is bound. */
+    dataBinding?: SdtDataBinding;
+    /**
+     * The original `<w:sdtPr>` serialized verbatim as an XML string, captured
+     * at parse time. Replayed unchanged on save so the properties block
+     * round-trips losslessly. Stored as a string (not an `XmlElement`) so the
+     * types layer stays free of the parser/`xml-js` dependency. Absent for
+     * SDTs created programmatically — the serializer then synthesizes a
+     * minimal, sequence-valid `w:sdtPr` from the modeled fields.
+     */
+    rawPropertiesXml?: string;
+    /** The original `<w:sdtEndPr>` serialized verbatim, if present. */
+    rawEndPropertiesXml?: string;
+}
+/**
+ * Inline SDT (content control within a paragraph)
+ */
+interface InlineSdt {
+    type: 'inlineSdt';
+    /** SDT properties */
+    properties: SdtProperties;
+    /**
+     * Inline content held inside the control. OOXML allows runs,
+     * hyperlinks, simple/complex fields, nested SDTs, and math at this
+     * level; the renderer must descend into all of them so docProps-bound
+     * fields and similar template content survive paged rendering.
+     */
+    content: (Run | Hyperlink | SimpleField | ComplexField | InlineSdt | MathEquation)[];
+}
+/**
+ * Block-level SDT (content control wrapping block content).
+ *
+ * `content` is `BlockContent[]` (not just paragraphs/tables) so a nested
+ * block SDT survives the round trip. `CT_SdtContentBlock` also permits
+ * run-level content (bookmarks, etc.); that is carried through the same
+ * block-content parsing as elsewhere in the document.
+ */
+interface BlockSdt {
+    type: 'blockSdt';
+    /** SDT properties */
+    properties: SdtProperties;
+    /** Block content inside the control */
+    content: BlockContent[];
+}
+
 /**
  * Paragraph (`w:p`) — the union of inline content that can sit inside a
  * paragraph (runs, hyperlinks, bookmarks, fields, SDT, comment ranges,

package/dist/{server-BELKcdSd.d.ts → server-uM9UUIhk.d.ts}

@@ -970,111 +970,6 @@ interface Table {
     rows: TableRow[];
 }
 
-/**
- * Structured Document Tags / content controls (`w:sdt`) — inline and
- * block variants, plus properties (alias, tag, lock, list items,
- * checkbox state) for the supported SDT types.
- */
-
-/**
- * SDT type (content control type)
- */
-type SdtType = 'richText' | 'plainText' | 'date' | 'dropdown' | 'comboBox' | 'checkbox' | 'picture' | 'buildingBlockGallery' | 'group' | 'unknown';
-/**
- * SDT properties (w:sdtPr)
- */
-interface SdtProperties {
-    /** SDT type */
-    sdtType: SdtType;
-    /** Alias (friendly name) */
-    alias?: string;
-    /** Tag (developer identifier) */
-    tag?: string;
-    /** Lock content editing */
-    lock?: 'sdtLocked' | 'contentLocked' | 'sdtContentLocked' | 'unlocked';
-    /** Placeholder text */
-    placeholder?: string;
-    /** Whether showing placeholder */
-    showingPlaceholder?: boolean;
-    /** Date format for date controls */
-    dateFormat?: string;
-    /** Dropdown/combobox list items */
-    listItems?: {
-        displayText: string;
-        value: string;
-    }[];
-    /** Checkbox checked state */
-    checked?: boolean;
-}
-/**
- * Inline SDT (content control within a paragraph)
- */
-interface InlineSdt {
-    type: 'inlineSdt';
-    /** SDT properties */
-    properties: SdtProperties;
-    /**
-     * Inline content held inside the control. OOXML allows runs,
-     * hyperlinks, simple/complex fields, nested SDTs, and math at this
-     * level; the renderer must descend into all of them so docProps-bound
-     * fields and similar template content survive paged rendering.
-     */
-    content: (Run | Hyperlink | SimpleField | ComplexField | InlineSdt | MathEquation)[];
-}
-/**
- * Block-level SDT (content control wrapping paragraphs/tables)
- */
-interface BlockSdt {
-    type: 'blockSdt';
-    /** SDT properties */
-    properties: SdtProperties;
-    /** Block content inside the control */
-    content: (Paragraph | Table)[];
-}
-
-/**
- * Comments (`w:comment` in `comments.xml`) and the inline range markers
- * (`w:commentRangeStart`/`End`) that anchor them inside paragraphs.
- */
-
-/**
- * A comment from `comments.xml` — the top-level entity for review
- * comments and replies. `id` matches the inline `CommentRangeStart` /
- * `CommentRangeEnd` markers that anchor it inside a paragraph; `parentId`
- * threads replies under their parent; `done` reflects Word's "Resolve"
- * state (`w15:done`).
- */
-interface Comment {
-    /** Comment ID (matches commentRangeStart/End) */
-    id: number;
-    /** Author name */
-    author: string;
-    /** Author initials */
-    initials?: string;
-    /** Date */
-    date?: string;
-    /** Comment content (paragraphs) */
-    content: Paragraph[];
-    /** Parent comment ID (for replies) */
-    parentId?: number;
-    /** Whether the comment is resolved/done */
-    done?: boolean;
-}
-/**
- * Comment range start marker in paragraph content
- */
-interface CommentRangeStart {
-    type: 'commentRangeStart';
-    id: number;
-}
-/**
- * Comment range end marker in paragraph content
- */
-interface CommentRangeEnd {
-    type: 'commentRangeEnd';
-    id: number;
-}
-
 /**
  * Page furniture — headers (`w:hdr`), footers (`w:ftr`), footnotes
  * (`w:footnote`), and endnotes (`w:endnote`), plus the section-level
@@ -1104,7 +999,7 @@ interface HeaderFooter {
     /** Header/footer type */
     hdrFtrType: HeaderFooterType;
     /** Content (paragraphs, tables, etc.) */
-    content: (Paragraph | Table)[];
+    content: BlockContent[];
 }
 /**
  * Footnote position
@@ -1152,7 +1047,7 @@ interface Footnote {
      * widened to match HeaderFooter / TableCell shape so the body pipeline
      * (toProseDoc → toFlowBlocks) can render them uniformly.
      */
-    content: (Paragraph | Table)[];
+    content: BlockContent[];
 }
 /**
  * Endnote (w:endnote)
@@ -1167,7 +1062,50 @@ interface Endnote {
      * Content. Per ECMA-376 §17.11.4 endnotes can hold the same blocks as
      * the body — paragraphs and tables. See note on `Footnote.content`.
      */
-    content: (Paragraph | Table)[];
+    content: BlockContent[];
+}
+
+/**
+ * Comments (`w:comment` in `comments.xml`) and the inline range markers
+ * (`w:commentRangeStart`/`End`) that anchor them inside paragraphs.
+ */
+
+/**
+ * A comment from `comments.xml` — the top-level entity for review
+ * comments and replies. `id` matches the inline `CommentRangeStart` /
+ * `CommentRangeEnd` markers that anchor it inside a paragraph; `parentId`
+ * threads replies under their parent; `done` reflects Word's "Resolve"
+ * state (`w15:done`).
+ */
+interface Comment {
+    /** Comment ID (matches commentRangeStart/End) */
+    id: number;
+    /** Author name */
+    author: string;
+    /** Author initials */
+    initials?: string;
+    /** Date */
+    date?: string;
+    /** Comment content (paragraphs) */
+    content: Paragraph[];
+    /** Parent comment ID (for replies) */
+    parentId?: number;
+    /** Whether the comment is resolved/done */
+    done?: boolean;
+}
+/**
+ * Comment range start marker in paragraph content
+ */
+interface CommentRangeStart {
+    type: 'commentRangeStart';
+    id: number;
+}
+/**
+ * Comment range end marker in paragraph content
+ */
+interface CommentRangeEnd {
+    type: 'commentRangeEnd';
+    id: number;
 }
 
 /**
@@ -1342,6 +1280,126 @@ interface DocumentBody {
     comments?: Comment[];
 }
 
+/**
+ * Structured Document Tags / content controls (`w:sdt`) — inline and
+ * block variants, plus properties (alias, tag, lock, list items,
+ * checkbox state) for the supported SDT types.
+ */
+
+/**
+ * SDT type (content control type).
+ *
+ * Values mirror the `w:sdtPr` type-marker element names from ECMA-376
+ * §17.5.2 (`CT_SdtPr`), with two deliberate exceptions:
+ * - `checkbox` is the `w14:checkbox` (Office 2010) extension, not a base
+ *   OOXML type marker.
+ * - `buildingBlockGallery` covers both `w:docPartObj` and `w:docPartList`.
+ *
+ * A `w:sdtPr` with no type marker means `richText` (the spec default). A
+ * type marker the parser does not model maps to `unknown` — it is never
+ * coerced to `richText`, so the projection stays honest. Round-trip
+ * fidelity does not depend on this enum: the raw `w:sdtPr` is replayed
+ * verbatim (see `rawPropertiesXml`).
+ */
+type SdtType = 'richText' | 'plainText' | 'date' | 'dropDownList' | 'comboBox' | 'checkbox' | 'picture' | 'buildingBlockGallery' | 'group' | 'equation' | 'citation' | 'bibliography' | 'unknown';
+/**
+ * XML data binding (`w:dataBinding`) — links a content control to a node in a
+ * Custom XML data store. Modeled read-only; the binding round-trips verbatim
+ * via `rawPropertiesXml` (this projection is for inspection, e.g. "which
+ * controls are bound, and to what XPath"). The editor does not resolve or
+ * sync bound values.
+ */
+interface SdtDataBinding {
+    /** XPath into the bound Custom XML part (`w:xpath`). */
+    xpath?: string;
+    /** Target Custom XML store id (`w:storeItemID`). */
+    storeItemID?: string;
+    /** Namespace prefix mappings used by the XPath (`w:prefixMappings`). */
+    prefixMappings?: string;
+}
+/**
+ * SDT properties (`w:sdtPr`).
+ *
+ * The modeled fields are a **read-only projection** for downstream tooling
+ * (tag/alias addressing, template extraction). They are NOT the
+ * serialization source: the original `w:sdtPr` is captured verbatim in
+ * `rawPropertiesXml` and replayed on save, which preserves element order
+ * (`CT_SdtPr` is an `xsd:sequence`), avoids double-emission, and keeps
+ * unmodeled features (data binding, `w15:*`, `@lastValue`) lossless.
+ */
+interface SdtProperties {
+    /** SDT type (projection; see {@link SdtType}). */
+    sdtType: SdtType;
+    /** Unique numeric id (`w:id`, signed). */
+    id?: number;
+    /** Alias (friendly name, `w:alias`). */
+    alias?: string;
+    /** Tag (developer identifier, `w:tag`). */
+    tag?: string;
+    /** Lock setting (`w:lock`). */
+    lock?: 'sdtLocked' | 'contentLocked' | 'sdtContentLocked' | 'unlocked';
+    /**
+     * Placeholder building-block name (`w:placeholder/w:docPart@w:val`).
+     * This is a reference to a glossary docPart that supplies the placeholder
+     * content — NOT the literal placeholder text.
+     */
+    placeholder?: string;
+    /** Whether the control is currently showing its placeholder (`w:showingPlcHdr`). */
+    showingPlaceholder?: boolean;
+    /** Date format for date controls (`w:date@w:fullDate`). */
+    dateFormat?: string;
+    /** Dropdown/combobox list items. */
+    listItems?: {
+        displayText: string;
+        value: string;
+    }[];
+    /** Checkbox checked state (`w14:checkbox`). */
+    checked?: boolean;
+    /** XML data binding (`w:dataBinding`), if the control is bound. */
+    dataBinding?: SdtDataBinding;
+    /**
+     * The original `<w:sdtPr>` serialized verbatim as an XML string, captured
+     * at parse time. Replayed unchanged on save so the properties block
+     * round-trips losslessly. Stored as a string (not an `XmlElement`) so the
+     * types layer stays free of the parser/`xml-js` dependency. Absent for
+     * SDTs created programmatically — the serializer then synthesizes a
+     * minimal, sequence-valid `w:sdtPr` from the modeled fields.
+     */
+    rawPropertiesXml?: string;
+    /** The original `<w:sdtEndPr>` serialized verbatim, if present. */
+    rawEndPropertiesXml?: string;
+}
+/**
+ * Inline SDT (content control within a paragraph)
+ */
+interface InlineSdt {
+    type: 'inlineSdt';
+    /** SDT properties */
+    properties: SdtProperties;
+    /**
+     * Inline content held inside the control. OOXML allows runs,
+     * hyperlinks, simple/complex fields, nested SDTs, and math at this
+     * level; the renderer must descend into all of them so docProps-bound
+     * fields and similar template content survive paged rendering.
+     */
+    content: (Run | Hyperlink | SimpleField | ComplexField | InlineSdt | MathEquation)[];
+}
+/**
+ * Block-level SDT (content control wrapping block content).
+ *
+ * `content` is `BlockContent[]` (not just paragraphs/tables) so a nested
+ * block SDT survives the round trip. `CT_SdtContentBlock` also permits
+ * run-level content (bookmarks, etc.); that is carried through the same
+ * block-content parsing as elsewhere in the document.
+ */
+interface BlockSdt {
+    type: 'blockSdt';
+    /** SDT properties */
+    properties: SdtProperties;
+    /** Block content inside the control */
+    content: BlockContent[];
+}
+
 /**
  * Paragraph (`w:p`) — the union of inline content that can sit inside a
  * paragraph (runs, hyperlinks, bookmarks, fields, SDT, comment ranges,

package/dist/server.d.mts

@@ -31,4 +31,4 @@
  * @packageDocumentation
  * @public
  */
-export { s as AgentContextSnapshot, j as AgentToolDefinition, k as AgentToolResult, D as DocxReviewer, E as EditorBridge, S as SelectionInfo, o as createReviewerBridge, n as docxAgentTools, p as executeToolCall, t as getToolDisplayName, q as getToolSchemas } from './server-BELKcdSd.mjs';
+export { s as AgentContextSnapshot, j as AgentToolDefinition, k as AgentToolResult, D as DocxReviewer, E as EditorBridge, S as SelectionInfo, o as createReviewerBridge, n as docxAgentTools, p as executeToolCall, t as getToolDisplayName, q as getToolSchemas } from './server-uM9UUIhk.mjs';

package/dist/server.d.ts

@@ -31,4 +31,4 @@
  * @packageDocumentation
  * @public
  */
-export { s as AgentContextSnapshot, j as AgentToolDefinition, k as AgentToolResult, D as DocxReviewer, E as EditorBridge, S as SelectionInfo, o as createReviewerBridge, n as docxAgentTools, p as executeToolCall, t as getToolDisplayName, q as getToolSchemas } from './server-BELKcdSd.js';
+export { s as AgentContextSnapshot, j as AgentToolDefinition, k as AgentToolResult, D as DocxReviewer, E as EditorBridge, S as SelectionInfo, o as createReviewerBridge, n as docxAgentTools, p as executeToolCall, t as getToolDisplayName, q as getToolSchemas } from './server-uM9UUIhk.js';

package/dist/server.js

@@ -1 +1 @@
-'use strict';var chunkVGEZQUGC_js=require('./chunk-VGEZQUGC.js'),chunkFUL3O7MO_js=require('./chunk-FUL3O7MO.js'),chunkRI5S75JY_js=require('./chunk-RI5S75JY.js');Object.defineProperty(exports,"DocxReviewer",{enumerable:true,get:function(){return chunkVGEZQUGC_js.a}});Object.defineProperty(exports,"createReviewerBridge",{enumerable:true,get:function(){return chunkFUL3O7MO_js.m}});Object.defineProperty(exports,"docxAgentTools",{enumerable:true,get:function(){return chunkRI5S75JY_js.a}});Object.defineProperty(exports,"executeToolCall",{enumerable:true,get:function(){return chunkRI5S75JY_js.b}});Object.defineProperty(exports,"getToolDisplayName",{enumerable:true,get:function(){return chunkRI5S75JY_js.c}});Object.defineProperty(exports,"getToolSchemas",{enumerable:true,get:function(){return chunkRI5S75JY_js.d}});
+'use strict';var chunkNSFRE2VK_js=require('./chunk-NSFRE2VK.js'),chunkMHUG23P6_js=require('./chunk-MHUG23P6.js'),chunkRI5S75JY_js=require('./chunk-RI5S75JY.js');Object.defineProperty(exports,"DocxReviewer",{enumerable:true,get:function(){return chunkNSFRE2VK_js.a}});Object.defineProperty(exports,"createReviewerBridge",{enumerable:true,get:function(){return chunkMHUG23P6_js.m}});Object.defineProperty(exports,"docxAgentTools",{enumerable:true,get:function(){return chunkRI5S75JY_js.a}});Object.defineProperty(exports,"executeToolCall",{enumerable:true,get:function(){return chunkRI5S75JY_js.b}});Object.defineProperty(exports,"getToolDisplayName",{enumerable:true,get:function(){return chunkRI5S75JY_js.c}});Object.defineProperty(exports,"getToolSchemas",{enumerable:true,get:function(){return chunkRI5S75JY_js.d}});

package/dist/server.mjs

@@ -1 +1 @@
-export{a as DocxReviewer}from'./chunk-UIE7JPED.mjs';export{m as createReviewerBridge}from'./chunk-F22XEI77.mjs';export{a as docxAgentTools,b as executeToolCall,c as getToolDisplayName,d as getToolSchemas}from'./chunk-24MVJKCP.mjs';
+export{a as DocxReviewer}from'./chunk-6KT5LOQB.mjs';export{m as createReviewerBridge}from'./chunk-MK47WH2X.mjs';export{a as docxAgentTools,b as executeToolCall,c as getToolDisplayName,d as getToolSchemas}from'./chunk-24MVJKCP.mjs';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eigenpal/docx-editor-agents",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "Agent SDK and chat UI for the DOCX editor — framework-agnostic bridge, MCP server, AI SDK adapters, plus React UI (and Vue UI in 1.x)",
   "sideEffects": [
     "*.css"