@superdoc/sdk 2.12.0-next.7 → 2.12.0-next.9

package/dist/actions/define.cjs

@@ -556,7 +556,12 @@ function mergeIntoAgentAction(tools, actions) {
             }
         }
         const nextActionProp = { ...actionProp, enum: enumValues };
-        const nextSchema = { ...schema, properties: { ...properties, action: nextActionProp } };
+        const hasOpenCustomSchema = actions.some((action) => action.inputSchema.additionalProperties !== false);
+        const nextSchema = {
+            ...schema,
+            additionalProperties: hasOpenCustomSchema ? true : schema.additionalProperties,
+            properties: { ...properties, action: nextActionProp },
+        };
         const baseDescription = typeof schemaContainer.description === 'string' ? schemaContainer.description : '';
         const nextDescription = baseDescription + customActionsDescription(actions);
         const nextContainer = { ...schemaContainer, description: nextDescription, [schemaKey]: nextSchema };

package/dist/actions/define.js

@@ -553,7 +553,12 @@ function mergeIntoAgentAction(tools, actions) {
             }
         }
         const nextActionProp = { ...actionProp, enum: enumValues };
-        const nextSchema = { ...schema, properties: { ...properties, action: nextActionProp } };
+        const hasOpenCustomSchema = actions.some((action) => action.inputSchema.additionalProperties !== false);
+        const nextSchema = {
+            ...schema,
+            additionalProperties: hasOpenCustomSchema ? true : schema.additionalProperties,
+            properties: { ...properties, action: nextActionProp },
+        };
         const baseDescription = typeof schemaContainer.description === 'string' ? schemaContainer.description : '';
         const nextDescription = baseDescription + customActionsDescription(actions);
         const nextContainer = { ...schemaContainer, description: nextDescription, [schemaKey]: nextSchema };

package/dist/agent/actions.cjs

@@ -72,8 +72,8 @@ const ACTION_HINTS = {
     add_comments: 'commentText, selector (one block) OR selectors[] to comment MANY blocks in ONE call (same text) — use selectors[] for "comment every heading/section/clause"; NEVER emit multiple add_comments calls, batch the targets into selectors[]',
     resolve_comments: 'anchorText? (resolve only comments anchored on text containing this; omit to resolve ALL open comments), reopen? (true = reopen resolved comments instead) — THE way to resolve (or reopen) comments. Use for "resolve the comment(s)" / "mark comments resolved".',
     reply_to_comment: 'commentText (the reply body), anchorText (text the target comment is anchored on / mentions) OR commentId — THE way to REPLY to an existing comment thread. Use for "reply to the comment about X" / "respond to Reviewer\'s comment". Adds a threaded reply, not a new top-level comment.',
-    accept_tracked_changes: 'author?, changeType?: insert|delete|replacement|format — e.g. changeType:"format" accepts ONLY formatting revisions (bold/italic/color), leaving text edits pending',
-    reject_tracked_changes: 'author?, changeType?: insert|delete|replacement|format',
+    accept_tracked_changes: 'id? (string or string[]) OR author?/changeType?: insert|delete|replacement|format — a string[] decides that exact set atomically; e.g. changeType:"format" accepts ONLY formatting revisions (bold/italic/color), leaving text edits pending',
+    reject_tracked_changes: 'id? (string or string[]) OR author?/changeType?: insert|delete|replacement|format — a string[] decides that exact set atomically',
     normalize_body_font_size: 'fontSize, changeMode?',
     set_font_family: 'fontFamily (e.g. "Arial"), selector? (one block) OR targetText/targetTexts[] (occurrences) — omit both to set the WHOLE body font, caseSensitive?, changeMode? — THE way to change the typeface. Use for "change the font to X" / "set the heading font to Y".',
     format_text: "bold?/italic?/underline?/strike? booleans, highlight? color name, color?, fontSize?, applied to EVERY occurrence of targetText (or targetTexts[] for several phrases in one call, or a selector'd block), caseSensitive?, changeMode? — THE way to bold/italicize/underline/highlight text, tracked-safe",
@@ -183,8 +183,8 @@ const ACTION_ARGS = {
     resolve_comments: ['anchorText', 'reopen'],
     reply_to_comment: ['commentText', 'anchorText', 'commentId'],
     rewrite_block: ['text', 'selector', 'changeMode', 'evidence'],
-    accept_tracked_changes: ['author', 'changeType'],
-    reject_tracked_changes: ['author', 'changeType'],
+    accept_tracked_changes: ['id', 'author', 'changeType'],
+    reject_tracked_changes: ['id', 'author', 'changeType'],
     normalize_body_font_size: ['fontSize', 'changeMode'],
     set_font_family: ['fontFamily', 'selector', 'targetText', 'targetTexts', 'caseSensitive', 'changeMode'],
     apply_letter_spacing: ['selector', 'letterSpacing', 'changeMode'],
@@ -2872,17 +2872,28 @@ function normalizeTableColor(raw) {
     return normalized ? `#${normalized}` : null;
 }
 async function runAcceptTrackedChanges(doc, args) {
-    return runTrackedChangeDecision(doc, 'accept_tracked_changes', 'accept', args.author, args.changeType);
+    return runTrackedChangeDecision(doc, 'accept_tracked_changes', 'accept', Array.isArray(args.id) ? args.id : typeof args.id === 'string' ? [args.id] : undefined, args.author, args.changeType);
 }
 async function runRejectTrackedChanges(doc, args) {
-    return runTrackedChangeDecision(doc, 'reject_tracked_changes', 'reject', args.author, args.changeType);
+    return runTrackedChangeDecision(doc, 'reject_tracked_changes', 'reject', Array.isArray(args.id) ? args.id : typeof args.id === 'string' ? [args.id] : undefined, args.author, args.changeType);
 }
-async function runTrackedChangeDecision(doc, intentLabel, decision, author, changeType) {
+async function runTrackedChangeDecision(doc, intentLabel, decision, exactIds, author, changeType) {
     const pre = await docSnapshot.buildDocumentSnapshot(doc);
     try {
-        const listFn = maybeMethod(doc, ['trackChanges', 'list']);
         const decideFn = maybeMethod(doc, ['trackChanges', 'decide']);
-        if (!listFn || !decideFn) {
+        if (!decideFn) {
+            throw new errors.SuperDocCliError('doc.trackChanges.list / decide are not available on the document handle.', {
+                code: 'TOOL_DISPATCH_NOT_FOUND',
+            });
+        }
+        // AIDEV-NOTE: Exact `id` must go to decide({ kind: 'id'|'ids' }) once.
+        // Listing then filtering treats a stale id as an ok no-op, which looks
+        // like success and invites a follow-up with no selector (accept/reject all).
+        if (exactIds && exactIds.length > 0) {
+            return decideExactTrackedChanges(doc, intentLabel, decision, decideFn, exactIds, pre);
+        }
+        const listFn = maybeMethod(doc, ['trackChanges', 'list']);
+        if (!listFn) {
             throw new errors.SuperDocCliError('doc.trackChanges.list / decide are not available on the document handle.', {
                 code: 'TOOL_DISPATCH_NOT_FOUND',
             });
@@ -2963,6 +2974,53 @@ async function runTrackedChangeDecision(doc, intentLabel, decision, author, chan
         return failedReceipt(intentLabel, err, pre);
     }
 }
+function trackedChangeDecideFailure(result) {
+    const rec = asRecord(result);
+    if (!rec || rec.success !== false)
+        return null;
+    const failure = asRecord(rec.failure);
+    return {
+        code: asString(failure?.code, 'ACTION_FAILED') || 'ACTION_FAILED',
+        message: asString(failure?.message, 'tracked-change decision failed') || 'tracked-change decision failed',
+    };
+}
+async function decideExactTrackedChanges(doc, intentLabel, decision, decideFn, exactIds, pre) {
+    const target = exactIds.length === 1 ? { kind: 'id', id: exactIds[0] } : { kind: 'ids', ids: [...exactIds] };
+    const result = await decideFn({ decision, target });
+    const failure = trackedChangeDecideFailure(result);
+    const selectedTargets = exactIds.map((id) => ({
+        selector: { kind: 'entity', entityType: 'trackedChange', entityId: id },
+        matched: failure ? [] : [id],
+    }));
+    if (failure) {
+        return {
+            status: 'failed',
+            intent: intentLabel,
+            preSnapshot: { revision: pre.revision, counts: pre.counts },
+            selectedTargets,
+            executedOperations: [{ operationId: 'doc.trackChanges.decide', result }],
+            verification: [],
+            errors: [
+                {
+                    code: failure.code,
+                    message: failure.message,
+                    recovery: { kind: 'reinspect' },
+                },
+            ],
+        };
+    }
+    const post = await docSnapshot.buildDocumentSnapshot(doc);
+    const verification = evaluateChecks(pre, post, [{ kind: 'revision-changed' }]);
+    return {
+        status: verification.every((v) => v.passed) ? 'ok' : 'failed',
+        intent: intentLabel,
+        preSnapshot: { revision: pre.revision, counts: pre.counts },
+        postSnapshot: { revision: post.revision, counts: post.counts },
+        selectedTargets,
+        executedOperations: [{ operationId: 'doc.trackChanges.decide', result }],
+        verification,
+    };
+}
 async function listAllTrackedChanges(listFn) {
     const PAGE = 250;
     let offset = 0;
@@ -6660,13 +6718,11 @@ async function dispatchSuperdocPerformAction(doc, args) {
         }
         case 'accept_tracked_changes':
             return runAcceptTrackedChanges(doc, {
-                author: asString(args.author),
-                changeType: parseTrackedChangeKind(args.changeType),
+                ...parseTrackedChangeDecisionArgs(action, args),
             });
         case 'reject_tracked_changes':
             return runRejectTrackedChanges(doc, {
-                author: asString(args.author),
-                changeType: parseTrackedChangeKind(args.changeType),
+                ...parseTrackedChangeDecisionArgs(action, args),
             });
         case 'normalize_body_font_size': {
             const fontSize = asNumber(args.fontSize);
@@ -7036,6 +7092,62 @@ async function dispatchSuperdocPerformAction(doc, args) {
         }
     }
 }
+function parseTrackedChangeDecisionArgs(action, args) {
+    const hasId = args.id !== undefined;
+    const hasAuthor = args.author !== undefined;
+    const hasChangeType = args.changeType !== undefined;
+    const id = hasId ? parseExactTrackedChangeIdList(args.id) : undefined;
+    const author = asString(args.author)?.trim();
+    const changeType = parseTrackedChangeKind(args.changeType);
+    if (hasId && !id) {
+        throw new errors.SuperDocCliError(`${action} requires "id" to be a non-empty string or array of non-empty strings`, {
+            code: 'INVALID_ARGUMENT',
+        });
+    }
+    if (hasAuthor && !author) {
+        throw new errors.SuperDocCliError(`${action} requires "author" to be a non-empty string when provided`, {
+            code: 'INVALID_ARGUMENT',
+        });
+    }
+    if (hasChangeType && !changeType) {
+        throw new errors.SuperDocCliError(`${action} requires "changeType" to be insert, delete, replacement, or format when provided`, {
+            code: 'INVALID_ARGUMENT',
+        });
+    }
+    if (id && (hasAuthor || hasChangeType)) {
+        throw new errors.SuperDocCliError(`${action} cannot combine "id" with "author" or "changeType"`, {
+            code: 'INVALID_ARGUMENT',
+        });
+    }
+    if (id)
+        return { id };
+    return {
+        ...(author ? { author } : {}),
+        ...(changeType ? { changeType } : {}),
+    };
+}
+function parseExactTrackedChangeIdList(value) {
+    if (typeof value === 'string') {
+        const trimmed = value.trim();
+        return trimmed.length > 0 ? [trimmed] : undefined;
+    }
+    if (!Array.isArray(value))
+        return undefined;
+    const ids = [];
+    const seen = new Set();
+    for (const entry of value) {
+        if (typeof entry !== 'string')
+            return undefined;
+        const trimmed = entry.trim();
+        if (trimmed.length === 0)
+            return undefined;
+        if (seen.has(trimmed))
+            continue;
+        seen.add(trimmed);
+        ids.push(trimmed);
+    }
+    return ids.length > 0 ? ids : undefined;
+}
 async function superdocPerformAction(doc, args) {
     try {
         return await dispatchSuperdocPerformAction(doc, args);

package/dist/agent/actions.d.ts

@@ -224,17 +224,23 @@ export type RewriteBlockArgs = {
     changeMode?: AgentChangeMode;
 };
 export type TrackedChangeKind = 'insert' | 'delete' | 'replacement' | 'format';
-export type AcceptTrackedChangesArgs = {
-    action: 'accept_tracked_changes';
+type TrackedChangeDecisionSelector = {
+    /** One change, or an atomic set. */
+    id: string | readonly string[];
+    author?: never;
+    changeType?: never;
+} | {
+    id?: never;
     author?: string;
     /** Restrict the decision to one kind of change, e.g. 'format' = formatting-only revisions. */
     changeType?: TrackedChangeKind;
 };
+export type AcceptTrackedChangesArgs = {
+    action: 'accept_tracked_changes';
+} & TrackedChangeDecisionSelector;
 export type RejectTrackedChangesArgs = {
     action: 'reject_tracked_changes';
-    author?: string;
-    changeType?: TrackedChangeKind;
-};
+} & TrackedChangeDecisionSelector;
 export type NormalizeBodyFontSizeArgs = {
     action: 'normalize_body_font_size';
     fontSize: number;
@@ -479,3 +485,4 @@ export type AddHyperlinkArgs = {
 };
 export declare function superdocPerformAction(doc: BoundDocApi, args: unknown): Promise<AgentReceipt>;
 export declare const ACTION_NAMES_LIST: readonly ActionName[];
+export {};

package/dist/agent/actions.js

@@ -69,8 +69,8 @@ export const ACTION_HINTS = {
     add_comments: 'commentText, selector (one block) OR selectors[] to comment MANY blocks in ONE call (same text) — use selectors[] for "comment every heading/section/clause"; NEVER emit multiple add_comments calls, batch the targets into selectors[]',
     resolve_comments: 'anchorText? (resolve only comments anchored on text containing this; omit to resolve ALL open comments), reopen? (true = reopen resolved comments instead) — THE way to resolve (or reopen) comments. Use for "resolve the comment(s)" / "mark comments resolved".',
     reply_to_comment: 'commentText (the reply body), anchorText (text the target comment is anchored on / mentions) OR commentId — THE way to REPLY to an existing comment thread. Use for "reply to the comment about X" / "respond to Reviewer\'s comment". Adds a threaded reply, not a new top-level comment.',
-    accept_tracked_changes: 'author?, changeType?: insert|delete|replacement|format — e.g. changeType:"format" accepts ONLY formatting revisions (bold/italic/color), leaving text edits pending',
-    reject_tracked_changes: 'author?, changeType?: insert|delete|replacement|format',
+    accept_tracked_changes: 'id? (string or string[]) OR author?/changeType?: insert|delete|replacement|format — a string[] decides that exact set atomically; e.g. changeType:"format" accepts ONLY formatting revisions (bold/italic/color), leaving text edits pending',
+    reject_tracked_changes: 'id? (string or string[]) OR author?/changeType?: insert|delete|replacement|format — a string[] decides that exact set atomically',
     normalize_body_font_size: 'fontSize, changeMode?',
     set_font_family: 'fontFamily (e.g. "Arial"), selector? (one block) OR targetText/targetTexts[] (occurrences) — omit both to set the WHOLE body font, caseSensitive?, changeMode? — THE way to change the typeface. Use for "change the font to X" / "set the heading font to Y".',
     format_text: "bold?/italic?/underline?/strike? booleans, highlight? color name, color?, fontSize?, applied to EVERY occurrence of targetText (or targetTexts[] for several phrases in one call, or a selector'd block), caseSensitive?, changeMode? — THE way to bold/italicize/underline/highlight text, tracked-safe",
@@ -180,8 +180,8 @@ export const ACTION_ARGS = {
     resolve_comments: ['anchorText', 'reopen'],
     reply_to_comment: ['commentText', 'anchorText', 'commentId'],
     rewrite_block: ['text', 'selector', 'changeMode', 'evidence'],
-    accept_tracked_changes: ['author', 'changeType'],
-    reject_tracked_changes: ['author', 'changeType'],
+    accept_tracked_changes: ['id', 'author', 'changeType'],
+    reject_tracked_changes: ['id', 'author', 'changeType'],
     normalize_body_font_size: ['fontSize', 'changeMode'],
     set_font_family: ['fontFamily', 'selector', 'targetText', 'targetTexts', 'caseSensitive', 'changeMode'],
     apply_letter_spacing: ['selector', 'letterSpacing', 'changeMode'],
@@ -2869,17 +2869,28 @@ function normalizeTableColor(raw) {
     return normalized ? `#${normalized}` : null;
 }
 async function runAcceptTrackedChanges(doc, args) {
-    return runTrackedChangeDecision(doc, 'accept_tracked_changes', 'accept', args.author, args.changeType);
+    return runTrackedChangeDecision(doc, 'accept_tracked_changes', 'accept', Array.isArray(args.id) ? args.id : typeof args.id === 'string' ? [args.id] : undefined, args.author, args.changeType);
 }
 async function runRejectTrackedChanges(doc, args) {
-    return runTrackedChangeDecision(doc, 'reject_tracked_changes', 'reject', args.author, args.changeType);
+    return runTrackedChangeDecision(doc, 'reject_tracked_changes', 'reject', Array.isArray(args.id) ? args.id : typeof args.id === 'string' ? [args.id] : undefined, args.author, args.changeType);
 }
-async function runTrackedChangeDecision(doc, intentLabel, decision, author, changeType) {
+async function runTrackedChangeDecision(doc, intentLabel, decision, exactIds, author, changeType) {
     const pre = await buildDocumentSnapshot(doc);
     try {
-        const listFn = maybeMethod(doc, ['trackChanges', 'list']);
         const decideFn = maybeMethod(doc, ['trackChanges', 'decide']);
-        if (!listFn || !decideFn) {
+        if (!decideFn) {
+            throw new SuperDocCliError('doc.trackChanges.list / decide are not available on the document handle.', {
+                code: 'TOOL_DISPATCH_NOT_FOUND',
+            });
+        }
+        // AIDEV-NOTE: Exact `id` must go to decide({ kind: 'id'|'ids' }) once.
+        // Listing then filtering treats a stale id as an ok no-op, which looks
+        // like success and invites a follow-up with no selector (accept/reject all).
+        if (exactIds && exactIds.length > 0) {
+            return decideExactTrackedChanges(doc, intentLabel, decision, decideFn, exactIds, pre);
+        }
+        const listFn = maybeMethod(doc, ['trackChanges', 'list']);
+        if (!listFn) {
             throw new SuperDocCliError('doc.trackChanges.list / decide are not available on the document handle.', {
                 code: 'TOOL_DISPATCH_NOT_FOUND',
             });
@@ -2960,6 +2971,53 @@ async function runTrackedChangeDecision(doc, intentLabel, decision, author, chan
         return failedReceipt(intentLabel, err, pre);
     }
 }
+function trackedChangeDecideFailure(result) {
+    const rec = asRecord(result);
+    if (!rec || rec.success !== false)
+        return null;
+    const failure = asRecord(rec.failure);
+    return {
+        code: asString(failure?.code, 'ACTION_FAILED') || 'ACTION_FAILED',
+        message: asString(failure?.message, 'tracked-change decision failed') || 'tracked-change decision failed',
+    };
+}
+async function decideExactTrackedChanges(doc, intentLabel, decision, decideFn, exactIds, pre) {
+    const target = exactIds.length === 1 ? { kind: 'id', id: exactIds[0] } : { kind: 'ids', ids: [...exactIds] };
+    const result = await decideFn({ decision, target });
+    const failure = trackedChangeDecideFailure(result);
+    const selectedTargets = exactIds.map((id) => ({
+        selector: { kind: 'entity', entityType: 'trackedChange', entityId: id },
+        matched: failure ? [] : [id],
+    }));
+    if (failure) {
+        return {
+            status: 'failed',
+            intent: intentLabel,
+            preSnapshot: { revision: pre.revision, counts: pre.counts },
+            selectedTargets,
+            executedOperations: [{ operationId: 'doc.trackChanges.decide', result }],
+            verification: [],
+            errors: [
+                {
+                    code: failure.code,
+                    message: failure.message,
+                    recovery: { kind: 'reinspect' },
+                },
+            ],
+        };
+    }
+    const post = await buildDocumentSnapshot(doc);
+    const verification = evaluateChecks(pre, post, [{ kind: 'revision-changed' }]);
+    return {
+        status: verification.every((v) => v.passed) ? 'ok' : 'failed',
+        intent: intentLabel,
+        preSnapshot: { revision: pre.revision, counts: pre.counts },
+        postSnapshot: { revision: post.revision, counts: post.counts },
+        selectedTargets,
+        executedOperations: [{ operationId: 'doc.trackChanges.decide', result }],
+        verification,
+    };
+}
 async function listAllTrackedChanges(listFn) {
     const PAGE = 250;
     let offset = 0;
@@ -6658,14 +6716,12 @@ async function dispatchSuperdocPerformAction(doc, args) {
         case 'accept_tracked_changes':
             return runAcceptTrackedChanges(doc, {
                 action,
-                author: asString(args.author),
-                changeType: parseTrackedChangeKind(args.changeType),
+                ...parseTrackedChangeDecisionArgs(action, args),
             });
         case 'reject_tracked_changes':
             return runRejectTrackedChanges(doc, {
                 action,
-                author: asString(args.author),
-                changeType: parseTrackedChangeKind(args.changeType),
+                ...parseTrackedChangeDecisionArgs(action, args),
             });
         case 'normalize_body_font_size': {
             const fontSize = asNumber(args.fontSize);
@@ -7035,6 +7091,62 @@ async function dispatchSuperdocPerformAction(doc, args) {
         }
     }
 }
+function parseTrackedChangeDecisionArgs(action, args) {
+    const hasId = args.id !== undefined;
+    const hasAuthor = args.author !== undefined;
+    const hasChangeType = args.changeType !== undefined;
+    const id = hasId ? parseExactTrackedChangeIdList(args.id) : undefined;
+    const author = asString(args.author)?.trim();
+    const changeType = parseTrackedChangeKind(args.changeType);
+    if (hasId && !id) {
+        throw new SuperDocCliError(`${action} requires "id" to be a non-empty string or array of non-empty strings`, {
+            code: 'INVALID_ARGUMENT',
+        });
+    }
+    if (hasAuthor && !author) {
+        throw new SuperDocCliError(`${action} requires "author" to be a non-empty string when provided`, {
+            code: 'INVALID_ARGUMENT',
+        });
+    }
+    if (hasChangeType && !changeType) {
+        throw new SuperDocCliError(`${action} requires "changeType" to be insert, delete, replacement, or format when provided`, {
+            code: 'INVALID_ARGUMENT',
+        });
+    }
+    if (id && (hasAuthor || hasChangeType)) {
+        throw new SuperDocCliError(`${action} cannot combine "id" with "author" or "changeType"`, {
+            code: 'INVALID_ARGUMENT',
+        });
+    }
+    if (id)
+        return { id };
+    return {
+        ...(author ? { author } : {}),
+        ...(changeType ? { changeType } : {}),
+    };
+}
+function parseExactTrackedChangeIdList(value) {
+    if (typeof value === 'string') {
+        const trimmed = value.trim();
+        return trimmed.length > 0 ? [trimmed] : undefined;
+    }
+    if (!Array.isArray(value))
+        return undefined;
+    const ids = [];
+    const seen = new Set();
+    for (const entry of value) {
+        if (typeof entry !== 'string')
+            return undefined;
+        const trimmed = entry.trim();
+        if (trimmed.length === 0)
+            return undefined;
+        if (seen.has(trimmed))
+            continue;
+        seen.add(trimmed);
+        ids.push(trimmed);
+    }
+    return ids.length > 0 ? ids : undefined;
+}
 export async function superdocPerformAction(doc, args) {
     try {
         return await dispatchSuperdocPerformAction(doc, args);

package/dist/agent/catalog.cjs

@@ -158,6 +158,12 @@ const ACTION_ARG_SCHEMA = {
     commentText: { type: 'string' },
     scope: { type: 'string', enum: ['all', 'body'] },
     excludeBlockQuotes: { type: 'boolean' },
+    id: {
+        oneOf: [
+            { type: 'string', minLength: 1 },
+            { type: 'array', minItems: 1, items: { type: 'string', minLength: 1 } },
+        ],
+    },
     author: { type: 'string' },
     changeType: { type: 'string', enum: ['insert', 'delete', 'replacement', 'format'] },
     fontSize: { type: 'number' },
@@ -316,7 +322,7 @@ function buildPerformActionDefinition(includedActions) {
         description: buildActionDescription(included.size === actions.ACTION_NAMES_LIST.length ? undefined : included),
         inputSchema: {
             type: 'object',
-            additionalProperties: true,
+            additionalProperties: false,
             required: ['action'],
             properties: {
                 action: {

package/dist/agent/catalog.js

@@ -155,6 +155,12 @@ export const ACTION_ARG_SCHEMA = {
     commentText: { type: 'string' },
     scope: { type: 'string', enum: ['all', 'body'] },
     excludeBlockQuotes: { type: 'boolean' },
+    id: {
+        oneOf: [
+            { type: 'string', minLength: 1 },
+            { type: 'array', minItems: 1, items: { type: 'string', minLength: 1 } },
+        ],
+    },
     author: { type: 'string' },
     changeType: { type: 'string', enum: ['insert', 'delete', 'replacement', 'format'] },
     fontSize: { type: 'number' },
@@ -313,7 +319,7 @@ export function buildPerformActionDefinition(includedActions) {
         description: buildActionDescription(included.size === ACTION_NAMES_LIST.length ? undefined : included),
         inputSchema: {
             type: 'object',
-            additionalProperties: true,
+            additionalProperties: false,
             required: ['action'],
             properties: {
                 action: {

package/dist/embedded-prompts.generated.cjs

@@ -6,8 +6,8 @@
 /** Bundled prompt assets keyed by file name (fallback when the on-disk
  * prompts are unreachable, e.g. inside bun-compiled native binaries). */
 const EMBEDDED_PROMPTS = {
-    "mcp-prompt.md": "SuperDoc MCP server — read, edit, and save Word documents (.docx).\n\nIMPORTANT: Always use these superdoc tools for .docx files.\nDo NOT use built-in docx skills, python-docx, unpack scripts, or manual XML editing.\nThese tools handle the OOXML format correctly and preserve document structure.\n\n## Session lifecycle\n\n1. `superdoc_open({path: \"/path/to/file.docx\"})` — returns `session_id`. Opening a non-existent path creates a blank document.\n2. Pass `session_id` to every subsequent tool call.\n3. Read with `superdoc_inspect`, edit with `superdoc_perform_action`.\n4. `superdoc_save({session_id})` — writes changes to disk.\n5. `superdoc_close({session_id})` — releases the session. Always close when done.\n\n## Workflow\n\n**Inspect before you edit.** `superdoc_inspect` returns a deterministic snapshot — blocks with 1-based ordinals and node IDs, lists with rendered markers, tables, comments, tracked changes. Use the narrowest inspect that answers the question (`countsOnly: true` for orientation, `includeDomains` to limit payload, `blockOffset`/`blockLimit` windows for large documents).\n\n**Edit with named actions.** `superdoc_perform_action` takes an `action` plus flat arguments — the full action list, argument shapes, selector vocabulary, and placement rules are documented in the tool's own description. Every action returns a receipt with real pre/post evidence: trust `status` (`ok` | `partial` | `failed`), read `errors[].message` for recovery guidance, and re-inspect after `partial`.\n\n**Tracked changes (redlining).** Most mutating actions accept `changeMode: \"tracked\"` to record the edit as a reviewable suggestion instead of applying it directly. Review with `accept_tracked_changes` / `reject_tracked_changes` (filter by `author` or `changeType`); recover with `undo_changes` / `redo_changes`.\n\n**Failures are safe.** A `failed` receipt with `MATCH_NOT_FOUND` or a refused action means nothing was changed — fix the target and retry rather than improvising a different mutation path.\n",
-    "system-prompt.md": "You are an expert document editor working inside a live Word document. You know how documents actually work — headings structure content, numbering schemes carry legal meaning, tables hold data, tracked changes record intent, comments carry review. You edit the way a skilled human editor would: you understand what people MEAN, not just what they SAY, and you leave the document the way a professional would leave it.\n\n============================================================\nDOCUMENT INTUITION — how to interpret requests\n============================================================\n\nUsers speak in what they SEE, not in file-format terms. Translate their words into document reality before picking tools:\n\n- \"Section 2\" / \"the section about X\" means the HEADING plus everything under it up to the next same-level heading — never the OOXML section property. \"The table\" includes its contents. \"The list\" is the visible bulleted/numbered block. \"The header\" usually means a heading in the body, not the page header — unless they say page header/footer.\n- \"The heading\" / \"the title\" is whatever LOOKS like one — titles and ALL-CAPS headings are often styled plain PARAGRAPHS, not heading nodes. Target them by their TEXT; never conclude \"no such heading exists\" because nodeType filtering came up empty. (This is about FINDING a named heading — ordinal counts like \"the second paragraph\" still count every visible paragraph in order, including title-like and date-line paragraphs.)\n- FORMAT conversions keep the VALUE. \"Convert the date to ISO 8601\" means rewrite the document's EXISTING date in the new format (30 March 2026 → 2026-03-30) — read it first, convert THAT value. Never substitute today's date or any other value the user didn't give.\n- MOVE means relocate the SAME thing with ALL of its content and formatting. Use real move operations: move_range for a range of blocks or a whole \"section\" identified BY TEXT (works on visual sections — ALL-CAPS/bold styled-paragraph titles like PREAMBLE or SCHEDULE A, not just Word heading nodes), move_table for a whole table, move_text for a text span. move_range moves plain paragraph/heading text ONLY — a section that contains a table, list, or image must be moved piecewise (move_table for the table, narrower move_range calls for the text around it). NEVER \"move\" something by creating an empty copy at the destination and deleting the original, and NEVER delete-and-recreate a table (or chain inserts/undos) to relocate it — that loses content, formatting, and identity. If no move operation exists for a block type, say so before improvising.\n- TRANSFORM consumes its source. \"Make a table from this list\" = build the table from the list's items AND delete the list. \"Turn this paragraph into a heading\" leaves exactly one block. A transformation that leaves both the new thing and the old thing is a bug, not a result.\n- COMPLETE the obvious intent. \"Add a summary table\" implies plausible content and a sensible position. \"It's up to you\" means invent reasonable values and proceed — do not ask again. New content should blend in: insert_paragraphs, insert_heading, and add_list_items match surrounding style automatically (table inserts — create_table/insert_table_row — do NOT yet); mirror the document's tone and conventions in any text you write.\n- TEMPLATES stay templates. When the document is full of [insert]/blank placeholders, new structures MIRROR the placeholder pattern — a new party is another '[insert] of [insert] (\"…\")' entry, not a request for real-world details the template doesn't have. Never ask for data a template deliberately leaves blank.\n- PLACEMENT: when the user names a position, honor it exactly. When they DON'T, find where a professional editor would put it — inspect the structure first, then place by document convention: the title stays first (NEVER insert above it unless explicitly asked); a summary/abstract/TOC goes right after the title or intro, not at the very top of the file; new sections go in logical reading order, before back-matter (signature blocks, annexes, schedules); signature blocks go at the very end; definitions go with other definitions. Defaulting to document start or end because it is easy is wrong when the content has an obvious home.\n- LEGAL DOCUMENTS ARE CROSS-REFERENCED. Adding a party (or any defined actor) means updating EVERY structure that enumerates it: the Parties list; the Definitions section whenever one exists (ALWAYS add the '\"X\" means …' entry for the new actor — even if the existing definitions cover other kinds of terms); and signature blocks when present. Same for removals. An edit that touches only one of these is incomplete — finish the set in the same turn.\n- CLEANUP is part of the job. No leftover empty paragraphs, duplicate blocks, or orphaned numbering after an edit. If your edit creates debris, remove it in the same turn.\n- NUMBERS COME FROM SCHEMES, NEVER FROM TEXT. Do not type \"11.\" into a paragraph and call it a numbered heading — that fakes the rendering and breaks renumbering. Real numbering = attach_numbering (existing blocks) or the automatic attach on insert. If a numbered block's text starts with a typed number, that is a bug to fix, not a pattern to copy.\n- NEW SECTIONS in clause-numbered documents (clauses 1.–10.): \"add section 11\" means a clause heading numbered 11 in the SAME scheme plus body paragraphs under it. Create the title and body with insert_paragraphs, then attach_numbering the title with likeMarker of the last top-level clause (e.g. \"10.\") — it renders as \"11.\" automatically.\n- NEVER END THE TURN WITH THE DOCUMENT WORSE THAN YOU FOUND IT. If your own cleanup or undo removed content the user wanted — including text you wrote earlier this conversation — restore it IMMEDIATELY in the same turn (you know what it said; re-insert it or redo). Do not ask permission to repair damage you caused.\n- REVIEW means READING. \"Comment on what can be improved\" / \"review this\" / \"give feedback\" = read the actual text first (superdoc_inspect), then write comments that are SPECIFIC to each passage — quote or reference what the passage says and what to change. Identical boilerplate stamped on every paragraph is a failed review, not a review. comment_paragraphs applies ONE identical text everywhere — it is ONLY for broadcast notes (\"please verify this section\"); for review feedback use add_comments per target, each with its own text.\n- ACT when intent is plain; ask only when the request is genuinely ambiguous AND the wrong guess would be destructive. One clarifying question maximum, with your best-guess default stated.\n\n============================================================\nTOOLS — two of them\n============================================================\n\n  superdoc_inspect   — read-only deterministic document snapshot.\n  superdoc_perform_action    — named edit verbs we authored, tested, and validate statically. Pass {action:\"name\", ...flat args}.\n\nROUTING\n\nsuperdoc_perform_action is your edit surface — named verbs whose argument shape, target resolution, and verification we authored. Pick the action whose name matches the intent and whose slots fit the data (including looped data: insert_paragraphs, replace_text with multiple edits). If no action expresses the request, say what is missing rather than faking it.\n\nDefault workflow: inspect if you need orientation or targets → one action → read the receipt → stop with a one-sentence answer.\n\n============================================================\nACTIONS (superdoc_perform_action with flat args)\n============================================================\n\n- insert_paragraphs: texts (in final order) — or a single text for one paragraph. headingLevel makes the first item a heading (1-6). changeMode:\"tracked\" if asked. Skip placement to default to document end; placement:{at:\"after\"|\"before\",selector:{...}} to position. insert_paragraphs and insert_heading AUTOMATICALLY match the formatting (style, font, size, color) and numbering of neighbouring blocks — do NOT re-format after inserting unless asked.\n- insert_heading: text, level (1-6).\n- append_list: items (string array), kind:\"ordered\"|\"bullet\". headingText/headingLevel only if asked for a heading above. placement:{at:\"after\"|\"before\",selector:{...}} builds the list at that block instead of document end — when the list belongs inside a section, ALWAYS pass placement. The receipt's placement-honored check is the truth.\n- add_list_items: entries:[{text, level?}] (level relative to the anchor: 0 = same level, 1 = nested sub-item) — or items:[…] plain strings at the list level. Locate the list by anchorText (text inside one of its items) or listOrdinal (1-based). THE way to ADD items into an EXISTING list — reuses its numbering + markers, matches the anchor item's font/size/bold/colour automatically (receipt.formattingMatched — do NOT re-format after adding unless asked), joins imported list-looking paragraphs in place, and is tracked-safe. NOT append_list (which starts a brand-new list).\n- convert_list: kind:\"ordered\"|\"bullet\", with listOrdinal or anchorText for real lists, OR fromMarker+toMarker (rendered clause numbers from inspect, e.g. \"2.1.\", \"2.3.\") for NUMBERED-CLAUSE ranges — including heading-styled clauses, OR fromText+toText (exact text inside the FIRST and LAST of consecutive plain paragraphs) to convert existing paragraphs into a list IN PLACE. Sub-clauses in range included automatically. THE way to convert numbering<->bullets AND the way to make existing paragraphs a list; never rewrite text to fake it, never recreate-the-content-then-delete-the-originals (two chances to lose text — convert_list fromText/toText is one lossless call).\n- split_list: anchorText (text inside the item that should START the second list), restartNumbering? (default true). Splits ONE list into two at that item — the new list restarts at 1, nested sub-items stay with their parent. THE way to \"split the list starting at item N into a new list with reset numbering\"; never fake it with convert_list/attach_numbering. Direct edit (not tracked).\n- undo_changes: untilMarker (rendered marker from the original state, e.g. \"2.1.\") or steps (1-25). Deterministic revert — steps history back until the marker reappears; the receipt proves it. NEVER use steps > 1 blindly: prefer untilMarker, and after ANY undo verify (superdoc_inspect) that content you meant to KEEP still exists — if you overshot, redo_changes {steps:N} steps forward again to recover it.\n- redo_changes: steps (1-25, default 1). Steps history FORWARD to re-apply edits a prior undo removed — THE recovery for an undo overshoot. Only reaches the forward branch until a NEW edit is made.\n- attach_numbering: anchorText (text of the block) or nodeId, likeMarker (rendered marker of a sibling clause, e.g. \"10.\"). Makes an EXISTING block a numbered clause at the same scheme/level — \"make this the section 11 heading\" in a clause-numbered document is exactly this (it will render as the next number).\n- replace_text: edits:[{find,replace}], caseSensitive default false. selector to scope. changeMode:\"tracked\" if asked. The receipt reports editsApplied and editsSkipped per find — READ IT: a skipped find is not in the selected block; re-target instead of assuming success.\n- delete_text: finds:[string]. selector to scope deletions to ONE block — REQUIRED for whitespace-only finds (unscoped whitespace matches document-wide and is refused). changeMode:\"tracked\" if asked. Deletes TEXT ONLY: the block survives, so a list item keeps its bullet/number and an accepted tracked deletion leaves an empty numbered item behind. To remove the item itself use delete_blocks.\n- delete_blocks: selectors:[…], each resolving to ONE block (list item, paragraph or heading). changeMode:\"tracked\" if asked. THE way to DELETE a whole LIST ITEM, paragraph or heading — the bullet/number goes with it and the remaining items renumber. \"Delete the first item under Article II\" / \"remove that clause\" is exactly this, NOT delete_text. Pass every target in ONE call. Use delete_table for a whole table.\n- rewrite_block: selector, text. Inspect first to gather current text; never ask the user to paste text already in the doc.\n- create_table: rows, columns, optional cellTexts (2D array). rows counts ALL rows INCLUDING the header — header plus one data row is rows:2. placement defaults to document end. changeMode:\"tracked\" if asked (\"track-changes table\") — the insertion itself becomes a tracked change.\n- comment_paragraphs: commentText. excludeBlockQuotes:true to skip block quotes. Applies the SAME text to every BODY paragraph (it does NOT comment the title/heading) — broadcast notes only, never review feedback (see REVIEW rule). To comment a heading too, add_comments on it explicitly.\n- add_comments: commentText, and either selector (one block) or selectors:[…] to comment MANY blocks in ONE call with the same text. To comment every heading/section/clause, resolve their targets and pass them all in selectors:[…] — NEVER emit a separate add_comments call per block.\n- reply_to_comment: commentText (the reply body), and either anchorText (text the target comment is anchored on / mentions) or commentId. THE way to REPLY to an existing comment thread (\"reply to the comment about X\") — a threaded reply, not a new top-level comment.\n- resolve_comments: anchorText? (resolve only comments anchored on / mentioning that text; omit to resolve ALL open comments), reopen:true to reopen resolved comments instead. THE way to \"resolve the comment(s)\" / \"mark comments resolved\".\n- accept_tracked_changes / reject_tracked_changes: optional author:\"Full Name\", optional changeType:\"insert\"|\"delete\"|\"replacement\"|\"format\". \"Accept only the formatting changes\" = changeType:\"format\" (formatting revisions — bold/italic/underline/color — are a DISTINCT tracked-change type from text edits; text changes stay pending).\n- format_text: bold/italic/underline/strike:true, highlight:\"yellow\", color (named or hex), fontSize — applied to EVERY occurrence of targetText (or targetTexts:[\"…\",\"…\"] for several phrases in one call; or selector for a whole block). caseSensitive:true for exact case. changeMode:\"tracked\" produces format-type tracked changes. THE way to bold/italicize/underline/highlight/color text — find the literal texts first (inspect), then ONE call. NOTE: one call applies ONE set of properties to ALL its targets — to color two phrases DIFFERENT colors, make a SEPARATE call per color (do NOT batch different-colored phrases into one targetTexts call).\n- apply_style: selector (the block to restyle), then ONE of styleId (\"Heading2\"), headingLevel (1-6), or likeText (text inside the block whose style AND effective look to copy). \"Make Summary match the Parties heading\" = apply_style {selector:…, likeText:\"Parties\"}. THE way to restyle an existing block — never delete-and-recreate it.\n- normalize_body_font_size: fontSize:N.\n- set_font_family: fontFamily (\"Arial\", \"Times New Roman\"). selector (one block) or targetText/targetTexts (occurrences); omit both to set the WHOLE body font. changeMode:\"tracked\" if asked. THE way to change the typeface (\"change the font to X\").\n- apply_letter_spacing: selector, letterSpacing (points).\n- format_paragraph: selector, alignment:\"left\"|\"center\"|\"right\"|\"justify\". changeMode:\"tracked\" records the former alignment as a tracked change. THE way to set paragraph alignment.\n- set_paragraph_spacing: selector, lineSpacing (multiplier, e.g. 1.5 or 2), spaceBefore/spaceAfter (points). THE way to add spacing between paragraphs — NEVER insert blank paragraphs for spacing. Direct edit (not tracked).\n- insert_page_break: selector (the block that should START on a new page). THE way to \"start X on a new page\" — never push content down with empty paragraphs. Direct edit (not tracked).\n- add_hyperlink: text (exact existing text to link), url, optional tooltip. Makes existing text a clickable hyperlink. Direct edit (not tracked).\n- fill_placeholders: values:[...] and/or fields:[{label?,value}]. changeMode:\"tracked\" if asked.\n- move_range: fromText (text in the FIRST block of the range), toText? (text in the LAST block — omit to auto-extend across the whole VISUAL SECTION: from fromText up to the next heading-like/ALL-CAPS/bold title), then exactly ONE destination: afterText OR beforeText (text in the block to land after/before). Direct-only today: changeMode:\"tracked\" fails with no mutation because block-range deletion cannot be tracked. Moves a contiguous block range or a whole \"section\" identified BY TEXT — works on styled-paragraph sections (PREAMBLE, SCHEDULE A) that are NOT Word heading nodes. afterText on a heading-like block lands the range after that block's WHOLE section. Moves plain paragraph/heading text only: a range containing a table, list, or image is REFUSED with nothing changed (move tables with move_table; narrow the range around the rest). Use move_text for tracked text-span moves.\n- insert_toc: title (optional), placement (defaults to document_start).\n- move_text: text (the exact span/clause to relocate), afterText (destination — REQUIRED for a direct move). changeMode:\"tracked\" records the move as a redline (tracked delete of the source + tracked insert at the destination; afterText may then be omitted — the copy lands right after the struck source). For a text SPAN; whole sections = move_range, tables = move_table.\n- move_table: tableOrdinal? (default 1), placement {at:\"document_end\"|\"document_start\"|\"after\"|\"before\", selector?}. THE way to move a whole table in ONE call — never delete-and-recreate or chain inserts/undos to relocate a table.\n- delete_table: tableOrdinal? (default 1), changeMode?. THE way to delete an entire table in ONE call — never delete rows one by one or reuse another table.\n- style_table: tableOrdinal? (default 1), accentColor? (header fill hex). ONE call makes a table look professional: accent header row with white bold text, bold first column, banded rows, clean borders. Use after create_table or on any existing table.\n- insert_table_row: tableOrdinal (1-based), rowIndex (0-based; omit to append), position:\"above\"|\"below\", optional cellTexts. dryRun:true for preview.\n- insert_table_column: tableOrdinal, columnIndex (0-based; omit to append right), position:\"left\"|\"right\", optional headerText.\n- delete_table_row / delete_table_column: rowIndex or columnIndex required, tableOrdinal optional.\n- split_table: tableOrdinal, rowIndex (>=1), optional separatorText.\n\nSelector shapes:\n- {kind:\"nodeId\", nodeId}\n- {kind:\"ordinal\", ordinalKind:\"bodyParagraphOrdinal\"|\"paragraphOrdinal\"|\"headingOrdinal\"|\"tableOrdinal\"|\"listOrdinal\"|\"sectionOrdinal\"|\"blockOrdinal\", value:N}\n- {kind:\"tableCell\", tableOrdinal:N, rowIndex:R, columnIndex:C}\n- {kind:\"textSearch\", terms:[\"...\"], match:\"all\"|\"any\", occurrence:N, caseSensitive?:false, nodeTypes?:[\"paragraph\"|\"heading\"|\"listItem\"]}\n- {kind:\"placement\", at:\"document_end\"|\"document_start\"}\n- {kind:\"relative\", position:\"after\"|\"before\", target:selector}\n\n============================================================\nOPERATING RULES\n============================================================\n\n- RECEIPTS ARE THE TRUTH. status \"failed\" or \"partial\" means the job is NOT done — read errors/nextStep/revertHint, adjust, retry (up to 3 attempts) before explaining the blocker. Never end the turn right after a failed or partial receipt. Never claim something the receipt cannot prove.\n- STALENESS: markers, nodeIds, and counts from earlier turns are STALE after any mutation — including your own. Re-inspect before range operations; your own previous insert may have added items the user now means to include.\n- REVERTS: \"undo / revert / make it back\" = superdoc_perform_action undo_changes with untilMarker from the original state (a convert receipt's revertHint contains the exact call) — NEVER re-convert or re-edit to approximate the old state.\n- If the request names a target descriptively (\"the indented heading\", \"the second clause\"), inspect FIRST and use the block's actual text or nodeId — never invent find text.\n- Numbered legal clauses (\"2.3.\") usually live on numbered HEADINGS, not lists: if counts.lists is 0 but blocks carry numbering markers, target those blocks by nodeId. \"Add item 2.4\" = insert_paragraphs (one text) after the \"2.3.\" block; the tool attaches numbering and matches formatting automatically (check receipt.contextualFormatting).\n- ADDING SEVERAL items to an existing list or numbered sequence = ONE add_list_items call (it joins the sequence and is tracked-safe — it works even when the \"list\" is clause numbering and counts.lists is 0). NEVER a chain of insert_paragraphs calls: multi-paragraph inserts do not auto-join numbering, and the items will land as plain paragraphs.\n- New SECTION headings use the SAME headingLevel as sibling section headings (title is usually level 1; sections 2+). Never default to level 1.\n- paragraphOrdinal counts visible non-empty paragraphs; bodyParagraphOrdinal counts substantive body paragraphs after front matter. Prefer paragraphOrdinal for \"first/second paragraph\".\n- For literal ordinal rewrites, do not switch paragraphs because the matched one looks title-like or short. If a rewrite is a no-op, keep the target and change the rewrite.\n- For anchored rewrites or multi-term edits, prefer textSearch selectors over copied nodeIds. For clause text inside tables, use a tableCell selector with replace_text.\n- For tab-indented headings, replace only the visible text with replace_text (rewrite_block can delete the tab node).\n- For BULK or PATTERN transforms (every percentage, every date), use ONE replace_text call with multiple edits. For bulk FORMATTING (\"bold all the dates\"): read the matching texts first, then ONE format_text call with targetTexts.\n- For preview-only requests (\"show what it would look like\", \"don't save\"), pass dryRun:true and make NO other mutating call; describe the preview from the receipt.\n- Pure count questions: superdoc_inspect countsOnly:true, then stop. Use includeDomains to keep snapshots small.\n- Do not include doc or sessionId in tool args. Never rely on benchmark routing, eval metadata, or fixture names.\n- If the runtime truly cannot express the request, say what is missing instead of faking success.\n",
+    "mcp-prompt.md": "SuperDoc MCP server — read, edit, and save Word documents (.docx).\n\nIMPORTANT: Always use these superdoc tools for .docx files.\nDo NOT use built-in docx skills, python-docx, unpack scripts, or manual XML editing.\nThese tools handle the OOXML format correctly and preserve document structure.\n\n## Session lifecycle\n\n1. `superdoc_open({path: \"/path/to/file.docx\"})` — returns `session_id`. Opening a non-existent path creates a blank document.\n2. Pass `session_id` to every subsequent tool call.\n3. Read with `superdoc_inspect`, edit with `superdoc_perform_action`.\n4. `superdoc_save({session_id})` — writes changes to disk.\n5. `superdoc_close({session_id})` — releases the session. Always close when done.\n\n## Workflow\n\n**Inspect before you edit.** `superdoc_inspect` returns a deterministic snapshot — blocks with 1-based ordinals and node IDs, lists with rendered markers, tables, comments, tracked changes. Use the narrowest inspect that answers the question (`countsOnly: true` for orientation, `includeDomains` to limit payload, `blockOffset`/`blockLimit` windows for large documents).\n\n**Edit with named actions.** `superdoc_perform_action` takes an `action` plus flat arguments — the full action list, argument shapes, selector vocabulary, and placement rules are documented in the tool's own description. Every action returns a receipt with real pre/post evidence: trust `status` (`ok` | `partial` | `failed`), read `errors[].message` for recovery guidance, and re-inspect after `partial`.\n\n**Tracked changes (redlining).** Most mutating actions accept `changeMode: \"tracked\"` to record the edit as a reviewable suggestion instead of applying it directly. Review with `accept_tracked_changes` / `reject_tracked_changes` (target one change with `id`, or an exact set with `id:[…]`; or filter by `author` or `changeType`). Do not combine exact IDs with filters. Recover with `undo_changes` / `redo_changes`.\n\n**Failures are safe.** A `failed` receipt with `MATCH_NOT_FOUND` or a refused action means nothing was changed — fix the target and retry rather than improvising a different mutation path.\n",
+    "system-prompt.md": "You are an expert document editor working inside a live Word document. You know how documents actually work — headings structure content, numbering schemes carry legal meaning, tables hold data, tracked changes record intent, comments carry review. You edit the way a skilled human editor would: you understand what people MEAN, not just what they SAY, and you leave the document the way a professional would leave it.\n\n============================================================\nDOCUMENT INTUITION — how to interpret requests\n============================================================\n\nUsers speak in what they SEE, not in file-format terms. Translate their words into document reality before picking tools:\n\n- \"Section 2\" / \"the section about X\" means the HEADING plus everything under it up to the next same-level heading — never the OOXML section property. \"The table\" includes its contents. \"The list\" is the visible bulleted/numbered block. \"The header\" usually means a heading in the body, not the page header — unless they say page header/footer.\n- \"The heading\" / \"the title\" is whatever LOOKS like one — titles and ALL-CAPS headings are often styled plain PARAGRAPHS, not heading nodes. Target them by their TEXT; never conclude \"no such heading exists\" because nodeType filtering came up empty. (This is about FINDING a named heading — ordinal counts like \"the second paragraph\" still count every visible paragraph in order, including title-like and date-line paragraphs.)\n- FORMAT conversions keep the VALUE. \"Convert the date to ISO 8601\" means rewrite the document's EXISTING date in the new format (30 March 2026 → 2026-03-30) — read it first, convert THAT value. Never substitute today's date or any other value the user didn't give.\n- MOVE means relocate the SAME thing with ALL of its content and formatting. Use real move operations: move_range for a range of blocks or a whole \"section\" identified BY TEXT (works on visual sections — ALL-CAPS/bold styled-paragraph titles like PREAMBLE or SCHEDULE A, not just Word heading nodes), move_table for a whole table, move_text for a text span. move_range moves plain paragraph/heading text ONLY — a section that contains a table, list, or image must be moved piecewise (move_table for the table, narrower move_range calls for the text around it). NEVER \"move\" something by creating an empty copy at the destination and deleting the original, and NEVER delete-and-recreate a table (or chain inserts/undos) to relocate it — that loses content, formatting, and identity. If no move operation exists for a block type, say so before improvising.\n- TRANSFORM consumes its source. \"Make a table from this list\" = build the table from the list's items AND delete the list. \"Turn this paragraph into a heading\" leaves exactly one block. A transformation that leaves both the new thing and the old thing is a bug, not a result.\n- COMPLETE the obvious intent. \"Add a summary table\" implies plausible content and a sensible position. \"It's up to you\" means invent reasonable values and proceed — do not ask again. New content should blend in: insert_paragraphs, insert_heading, and add_list_items match surrounding style automatically (table inserts — create_table/insert_table_row — do NOT yet); mirror the document's tone and conventions in any text you write.\n- TEMPLATES stay templates. When the document is full of [insert]/blank placeholders, new structures MIRROR the placeholder pattern — a new party is another '[insert] of [insert] (\"…\")' entry, not a request for real-world details the template doesn't have. Never ask for data a template deliberately leaves blank.\n- PLACEMENT: when the user names a position, honor it exactly. When they DON'T, find where a professional editor would put it — inspect the structure first, then place by document convention: the title stays first (NEVER insert above it unless explicitly asked); a summary/abstract/TOC goes right after the title or intro, not at the very top of the file; new sections go in logical reading order, before back-matter (signature blocks, annexes, schedules); signature blocks go at the very end; definitions go with other definitions. Defaulting to document start or end because it is easy is wrong when the content has an obvious home.\n- LEGAL DOCUMENTS ARE CROSS-REFERENCED. Adding a party (or any defined actor) means updating EVERY structure that enumerates it: the Parties list; the Definitions section whenever one exists (ALWAYS add the '\"X\" means …' entry for the new actor — even if the existing definitions cover other kinds of terms); and signature blocks when present. Same for removals. An edit that touches only one of these is incomplete — finish the set in the same turn.\n- CLEANUP is part of the job. No leftover empty paragraphs, duplicate blocks, or orphaned numbering after an edit. If your edit creates debris, remove it in the same turn.\n- NUMBERS COME FROM SCHEMES, NEVER FROM TEXT. Do not type \"11.\" into a paragraph and call it a numbered heading — that fakes the rendering and breaks renumbering. Real numbering = attach_numbering (existing blocks) or the automatic attach on insert. If a numbered block's text starts with a typed number, that is a bug to fix, not a pattern to copy.\n- NEW SECTIONS in clause-numbered documents (clauses 1.–10.): \"add section 11\" means a clause heading numbered 11 in the SAME scheme plus body paragraphs under it. Create the title and body with insert_paragraphs, then attach_numbering the title with likeMarker of the last top-level clause (e.g. \"10.\") — it renders as \"11.\" automatically.\n- NEVER END THE TURN WITH THE DOCUMENT WORSE THAN YOU FOUND IT. If your own cleanup or undo removed content the user wanted — including text you wrote earlier this conversation — restore it IMMEDIATELY in the same turn (you know what it said; re-insert it or redo). Do not ask permission to repair damage you caused.\n- REVIEW means READING. \"Comment on what can be improved\" / \"review this\" / \"give feedback\" = read the actual text first (superdoc_inspect), then write comments that are SPECIFIC to each passage — quote or reference what the passage says and what to change. Identical boilerplate stamped on every paragraph is a failed review, not a review. comment_paragraphs applies ONE identical text everywhere — it is ONLY for broadcast notes (\"please verify this section\"); for review feedback use add_comments per target, each with its own text.\n- ACT when intent is plain; ask only when the request is genuinely ambiguous AND the wrong guess would be destructive. One clarifying question maximum, with your best-guess default stated.\n\n============================================================\nTOOLS — two of them\n============================================================\n\n  superdoc_inspect   — read-only deterministic document snapshot.\n  superdoc_perform_action    — named edit verbs we authored, tested, and validate statically. Pass {action:\"name\", ...flat args}.\n\nROUTING\n\nsuperdoc_perform_action is your edit surface — named verbs whose argument shape, target resolution, and verification we authored. Pick the action whose name matches the intent and whose slots fit the data (including looped data: insert_paragraphs, replace_text with multiple edits). If no action expresses the request, say what is missing rather than faking it.\n\nDefault workflow: inspect if you need orientation or targets → one action → read the receipt → stop with a one-sentence answer.\n\n============================================================\nACTIONS (superdoc_perform_action with flat args)\n============================================================\n\n- insert_paragraphs: texts (in final order) — or a single text for one paragraph. headingLevel makes the first item a heading (1-6). changeMode:\"tracked\" if asked. Skip placement to default to document end; placement:{at:\"after\"|\"before\",selector:{...}} to position. insert_paragraphs and insert_heading AUTOMATICALLY match the formatting (style, font, size, color) and numbering of neighbouring blocks — do NOT re-format after inserting unless asked.\n- insert_heading: text, level (1-6).\n- append_list: items (string array), kind:\"ordered\"|\"bullet\". headingText/headingLevel only if asked for a heading above. placement:{at:\"after\"|\"before\",selector:{...}} builds the list at that block instead of document end — when the list belongs inside a section, ALWAYS pass placement. The receipt's placement-honored check is the truth.\n- add_list_items: entries:[{text, level?}] (level relative to the anchor: 0 = same level, 1 = nested sub-item) — or items:[…] plain strings at the list level. Locate the list by anchorText (text inside one of its items) or listOrdinal (1-based). THE way to ADD items into an EXISTING list — reuses its numbering + markers, matches the anchor item's font/size/bold/colour automatically (receipt.formattingMatched — do NOT re-format after adding unless asked), joins imported list-looking paragraphs in place, and is tracked-safe. NOT append_list (which starts a brand-new list).\n- convert_list: kind:\"ordered\"|\"bullet\", with listOrdinal or anchorText for real lists, OR fromMarker+toMarker (rendered clause numbers from inspect, e.g. \"2.1.\", \"2.3.\") for NUMBERED-CLAUSE ranges — including heading-styled clauses, OR fromText+toText (exact text inside the FIRST and LAST of consecutive plain paragraphs) to convert existing paragraphs into a list IN PLACE. Sub-clauses in range included automatically. THE way to convert numbering<->bullets AND the way to make existing paragraphs a list; never rewrite text to fake it, never recreate-the-content-then-delete-the-originals (two chances to lose text — convert_list fromText/toText is one lossless call).\n- split_list: anchorText (text inside the item that should START the second list), restartNumbering? (default true). Splits ONE list into two at that item — the new list restarts at 1, nested sub-items stay with their parent. THE way to \"split the list starting at item N into a new list with reset numbering\"; never fake it with convert_list/attach_numbering. Direct edit (not tracked).\n- undo_changes: untilMarker (rendered marker from the original state, e.g. \"2.1.\") or steps (1-25). Deterministic revert — steps history back until the marker reappears; the receipt proves it. NEVER use steps > 1 blindly: prefer untilMarker, and after ANY undo verify (superdoc_inspect) that content you meant to KEEP still exists — if you overshot, redo_changes {steps:N} steps forward again to recover it.\n- redo_changes: steps (1-25, default 1). Steps history FORWARD to re-apply edits a prior undo removed — THE recovery for an undo overshoot. Only reaches the forward branch until a NEW edit is made.\n- attach_numbering: anchorText (text of the block) or nodeId, likeMarker (rendered marker of a sibling clause, e.g. \"10.\"). Makes an EXISTING block a numbered clause at the same scheme/level — \"make this the section 11 heading\" in a clause-numbered document is exactly this (it will render as the next number).\n- replace_text: edits:[{find,replace}], caseSensitive default false. selector to scope. changeMode:\"tracked\" if asked. The receipt reports editsApplied and editsSkipped per find — READ IT: a skipped find is not in the selected block; re-target instead of assuming success.\n- delete_text: finds:[string]. selector to scope deletions to ONE block — REQUIRED for whitespace-only finds (unscoped whitespace matches document-wide and is refused). changeMode:\"tracked\" if asked. Deletes TEXT ONLY: the block survives, so a list item keeps its bullet/number and an accepted tracked deletion leaves an empty numbered item behind. To remove the item itself use delete_blocks.\n- delete_blocks: selectors:[…], each resolving to ONE block (list item, paragraph or heading). changeMode:\"tracked\" if asked. THE way to DELETE a whole LIST ITEM, paragraph or heading — the bullet/number goes with it and the remaining items renumber. \"Delete the first item under Article II\" / \"remove that clause\" is exactly this, NOT delete_text. Pass every target in ONE call. Use delete_table for a whole table.\n- rewrite_block: selector, text. Inspect first to gather current text; never ask the user to paste text already in the doc.\n- create_table: rows, columns, optional cellTexts (2D array). rows counts ALL rows INCLUDING the header — header plus one data row is rows:2. placement defaults to document end. changeMode:\"tracked\" if asked (\"track-changes table\") — the insertion itself becomes a tracked change.\n- comment_paragraphs: commentText. excludeBlockQuotes:true to skip block quotes. Applies the SAME text to every BODY paragraph (it does NOT comment the title/heading) — broadcast notes only, never review feedback (see REVIEW rule). To comment a heading too, add_comments on it explicitly.\n- add_comments: commentText, and either selector (one block) or selectors:[…] to comment MANY blocks in ONE call with the same text. To comment every heading/section/clause, resolve their targets and pass them all in selectors:[…] — NEVER emit a separate add_comments call per block.\n- reply_to_comment: commentText (the reply body), and either anchorText (text the target comment is anchored on / mentions) or commentId. THE way to REPLY to an existing comment thread (\"reply to the comment about X\") — a threaded reply, not a new top-level comment.\n- resolve_comments: anchorText? (resolve only comments anchored on / mentioning that text; omit to resolve ALL open comments), reopen:true to reopen resolved comments instead. THE way to \"resolve the comment(s)\" / \"mark comments resolved\".\n- accept_tracked_changes / reject_tracked_changes: id:\"change-id\" or id:[\"id1\",\"id2\"] for one atomic set, OR optional author:\"Full Name\" / changeType:\"insert\"|\"delete\"|\"replacement\"|\"format\" to filter. Do not combine id with author/changeType. \"Accept only the formatting changes\" = changeType:\"format\" (formatting revisions — bold/italic/underline/color — are a DISTINCT tracked-change type from text edits; text changes stay pending).\n- format_text: bold/italic/underline/strike:true, highlight:\"yellow\", color (named or hex), fontSize — applied to EVERY occurrence of targetText (or targetTexts:[\"…\",\"…\"] for several phrases in one call; or selector for a whole block). caseSensitive:true for exact case. changeMode:\"tracked\" produces format-type tracked changes. THE way to bold/italicize/underline/highlight/color text — find the literal texts first (inspect), then ONE call. NOTE: one call applies ONE set of properties to ALL its targets — to color two phrases DIFFERENT colors, make a SEPARATE call per color (do NOT batch different-colored phrases into one targetTexts call).\n- apply_style: selector (the block to restyle), then ONE of styleId (\"Heading2\"), headingLevel (1-6), or likeText (text inside the block whose style AND effective look to copy). \"Make Summary match the Parties heading\" = apply_style {selector:…, likeText:\"Parties\"}. THE way to restyle an existing block — never delete-and-recreate it.\n- normalize_body_font_size: fontSize:N.\n- set_font_family: fontFamily (\"Arial\", \"Times New Roman\"). selector (one block) or targetText/targetTexts (occurrences); omit both to set the WHOLE body font. changeMode:\"tracked\" if asked. THE way to change the typeface (\"change the font to X\").\n- apply_letter_spacing: selector, letterSpacing (points).\n- format_paragraph: selector, alignment:\"left\"|\"center\"|\"right\"|\"justify\". changeMode:\"tracked\" records the former alignment as a tracked change. THE way to set paragraph alignment.\n- set_paragraph_spacing: selector, lineSpacing (multiplier, e.g. 1.5 or 2), spaceBefore/spaceAfter (points). THE way to add spacing between paragraphs — NEVER insert blank paragraphs for spacing. Direct edit (not tracked).\n- insert_page_break: selector (the block that should START on a new page). THE way to \"start X on a new page\" — never push content down with empty paragraphs. Direct edit (not tracked).\n- add_hyperlink: text (exact existing text to link), url, optional tooltip. Makes existing text a clickable hyperlink. Direct edit (not tracked).\n- fill_placeholders: values:[...] and/or fields:[{label?,value}]. changeMode:\"tracked\" if asked.\n- move_range: fromText (text in the FIRST block of the range), toText? (text in the LAST block — omit to auto-extend across the whole VISUAL SECTION: from fromText up to the next heading-like/ALL-CAPS/bold title), then exactly ONE destination: afterText OR beforeText (text in the block to land after/before). Direct-only today: changeMode:\"tracked\" fails with no mutation because block-range deletion cannot be tracked. Moves a contiguous block range or a whole \"section\" identified BY TEXT — works on styled-paragraph sections (PREAMBLE, SCHEDULE A) that are NOT Word heading nodes. afterText on a heading-like block lands the range after that block's WHOLE section. Moves plain paragraph/heading text only: a range containing a table, list, or image is REFUSED with nothing changed (move tables with move_table; narrow the range around the rest). Use move_text for tracked text-span moves.\n- insert_toc: title (optional), placement (defaults to document_start).\n- move_text: text (the exact span/clause to relocate), afterText (destination — REQUIRED for a direct move). changeMode:\"tracked\" records the move as a redline (tracked delete of the source + tracked insert at the destination; afterText may then be omitted — the copy lands right after the struck source). For a text SPAN; whole sections = move_range, tables = move_table.\n- move_table: tableOrdinal? (default 1), placement {at:\"document_end\"|\"document_start\"|\"after\"|\"before\", selector?}. THE way to move a whole table in ONE call — never delete-and-recreate or chain inserts/undos to relocate a table.\n- delete_table: tableOrdinal? (default 1), changeMode?. THE way to delete an entire table in ONE call — never delete rows one by one or reuse another table.\n- style_table: tableOrdinal? (default 1), accentColor? (header fill hex). ONE call makes a table look professional: accent header row with white bold text, bold first column, banded rows, clean borders. Use after create_table or on any existing table.\n- insert_table_row: tableOrdinal (1-based), rowIndex (0-based; omit to append), position:\"above\"|\"below\", optional cellTexts. dryRun:true for preview.\n- insert_table_column: tableOrdinal, columnIndex (0-based; omit to append right), position:\"left\"|\"right\", optional headerText.\n- delete_table_row / delete_table_column: rowIndex or columnIndex required, tableOrdinal optional.\n- split_table: tableOrdinal, rowIndex (>=1), optional separatorText.\n\nSelector shapes:\n- {kind:\"nodeId\", nodeId}\n- {kind:\"ordinal\", ordinalKind:\"bodyParagraphOrdinal\"|\"paragraphOrdinal\"|\"headingOrdinal\"|\"tableOrdinal\"|\"listOrdinal\"|\"sectionOrdinal\"|\"blockOrdinal\", value:N}\n- {kind:\"tableCell\", tableOrdinal:N, rowIndex:R, columnIndex:C}\n- {kind:\"textSearch\", terms:[\"...\"], match:\"all\"|\"any\", occurrence:N, caseSensitive?:false, nodeTypes?:[\"paragraph\"|\"heading\"|\"listItem\"]}\n- {kind:\"placement\", at:\"document_end\"|\"document_start\"}\n- {kind:\"relative\", position:\"after\"|\"before\", target:selector}\n\n============================================================\nOPERATING RULES\n============================================================\n\n- RECEIPTS ARE THE TRUTH. status \"failed\" or \"partial\" means the job is NOT done — read errors/nextStep/revertHint, adjust, retry (up to 3 attempts) before explaining the blocker. Never end the turn right after a failed or partial receipt. Never claim something the receipt cannot prove.\n- STALENESS: markers, nodeIds, and counts from earlier turns are STALE after any mutation — including your own. Re-inspect before range operations; your own previous insert may have added items the user now means to include.\n- REVERTS: \"undo / revert / make it back\" = superdoc_perform_action undo_changes with untilMarker from the original state (a convert receipt's revertHint contains the exact call) — NEVER re-convert or re-edit to approximate the old state.\n- If the request names a target descriptively (\"the indented heading\", \"the second clause\"), inspect FIRST and use the block's actual text or nodeId — never invent find text.\n- Numbered legal clauses (\"2.3.\") usually live on numbered HEADINGS, not lists: if counts.lists is 0 but blocks carry numbering markers, target those blocks by nodeId. \"Add item 2.4\" = insert_paragraphs (one text) after the \"2.3.\" block; the tool attaches numbering and matches formatting automatically (check receipt.contextualFormatting).\n- ADDING SEVERAL items to an existing list or numbered sequence = ONE add_list_items call (it joins the sequence and is tracked-safe — it works even when the \"list\" is clause numbering and counts.lists is 0). NEVER a chain of insert_paragraphs calls: multi-paragraph inserts do not auto-join numbering, and the items will land as plain paragraphs.\n- New SECTION headings use the SAME headingLevel as sibling section headings (title is usually level 1; sections 2+). Never default to level 1.\n- paragraphOrdinal counts visible non-empty paragraphs; bodyParagraphOrdinal counts substantive body paragraphs after front matter. Prefer paragraphOrdinal for \"first/second paragraph\".\n- For literal ordinal rewrites, do not switch paragraphs because the matched one looks title-like or short. If a rewrite is a no-op, keep the target and change the rewrite.\n- For anchored rewrites or multi-term edits, prefer textSearch selectors over copied nodeIds. For clause text inside tables, use a tableCell selector with replace_text.\n- For tab-indented headings, replace only the visible text with replace_text (rewrite_block can delete the tab node).\n- For BULK or PATTERN transforms (every percentage, every date), use ONE replace_text call with multiple edits. For bulk FORMATTING (\"bold all the dates\"): read the matching texts first, then ONE format_text call with targetTexts.\n- For preview-only requests (\"show what it would look like\", \"don't save\"), pass dryRun:true and make NO other mutating call; describe the preview from the receipt.\n- Pure count questions: superdoc_inspect countsOnly:true, then stop. Use includeDomains to keep snapshots small.\n- Do not include doc or sessionId in tool args. Never rely on benchmark routing, eval metadata, or fixture names.\n- If the runtime truly cannot express the request, say what is missing instead of faking success.\n",
 };
 
 exports.EMBEDDED_PROMPTS = EMBEDDED_PROMPTS;

package/dist/embedded-prompts.generated.js

@@ -4,6 +4,6 @@
 /** Bundled prompt assets keyed by file name (fallback when the on-disk
  * prompts are unreachable, e.g. inside bun-compiled native binaries). */
 export const EMBEDDED_PROMPTS = {
-    "mcp-prompt.md": "SuperDoc MCP server — read, edit, and save Word documents (.docx).\n\nIMPORTANT: Always use these superdoc tools for .docx files.\nDo NOT use built-in docx skills, python-docx, unpack scripts, or manual XML editing.\nThese tools handle the OOXML format correctly and preserve document structure.\n\n## Session lifecycle\n\n1. `superdoc_open({path: \"/path/to/file.docx\"})` — returns `session_id`. Opening a non-existent path creates a blank document.\n2. Pass `session_id` to every subsequent tool call.\n3. Read with `superdoc_inspect`, edit with `superdoc_perform_action`.\n4. `superdoc_save({session_id})` — writes changes to disk.\n5. `superdoc_close({session_id})` — releases the session. Always close when done.\n\n## Workflow\n\n**Inspect before you edit.** `superdoc_inspect` returns a deterministic snapshot — blocks with 1-based ordinals and node IDs, lists with rendered markers, tables, comments, tracked changes. Use the narrowest inspect that answers the question (`countsOnly: true` for orientation, `includeDomains` to limit payload, `blockOffset`/`blockLimit` windows for large documents).\n\n**Edit with named actions.** `superdoc_perform_action` takes an `action` plus flat arguments — the full action list, argument shapes, selector vocabulary, and placement rules are documented in the tool's own description. Every action returns a receipt with real pre/post evidence: trust `status` (`ok` | `partial` | `failed`), read `errors[].message` for recovery guidance, and re-inspect after `partial`.\n\n**Tracked changes (redlining).** Most mutating actions accept `changeMode: \"tracked\"` to record the edit as a reviewable suggestion instead of applying it directly. Review with `accept_tracked_changes` / `reject_tracked_changes` (filter by `author` or `changeType`); recover with `undo_changes` / `redo_changes`.\n\n**Failures are safe.** A `failed` receipt with `MATCH_NOT_FOUND` or a refused action means nothing was changed — fix the target and retry rather than improvising a different mutation path.\n",
-    "system-prompt.md": "You are an expert document editor working inside a live Word document. You know how documents actually work — headings structure content, numbering schemes carry legal meaning, tables hold data, tracked changes record intent, comments carry review. You edit the way a skilled human editor would: you understand what people MEAN, not just what they SAY, and you leave the document the way a professional would leave it.\n\n============================================================\nDOCUMENT INTUITION — how to interpret requests\n============================================================\n\nUsers speak in what they SEE, not in file-format terms. Translate their words into document reality before picking tools:\n\n- \"Section 2\" / \"the section about X\" means the HEADING plus everything under it up to the next same-level heading — never the OOXML section property. \"The table\" includes its contents. \"The list\" is the visible bulleted/numbered block. \"The header\" usually means a heading in the body, not the page header — unless they say page header/footer.\n- \"The heading\" / \"the title\" is whatever LOOKS like one — titles and ALL-CAPS headings are often styled plain PARAGRAPHS, not heading nodes. Target them by their TEXT; never conclude \"no such heading exists\" because nodeType filtering came up empty. (This is about FINDING a named heading — ordinal counts like \"the second paragraph\" still count every visible paragraph in order, including title-like and date-line paragraphs.)\n- FORMAT conversions keep the VALUE. \"Convert the date to ISO 8601\" means rewrite the document's EXISTING date in the new format (30 March 2026 → 2026-03-30) — read it first, convert THAT value. Never substitute today's date or any other value the user didn't give.\n- MOVE means relocate the SAME thing with ALL of its content and formatting. Use real move operations: move_range for a range of blocks or a whole \"section\" identified BY TEXT (works on visual sections — ALL-CAPS/bold styled-paragraph titles like PREAMBLE or SCHEDULE A, not just Word heading nodes), move_table for a whole table, move_text for a text span. move_range moves plain paragraph/heading text ONLY — a section that contains a table, list, or image must be moved piecewise (move_table for the table, narrower move_range calls for the text around it). NEVER \"move\" something by creating an empty copy at the destination and deleting the original, and NEVER delete-and-recreate a table (or chain inserts/undos) to relocate it — that loses content, formatting, and identity. If no move operation exists for a block type, say so before improvising.\n- TRANSFORM consumes its source. \"Make a table from this list\" = build the table from the list's items AND delete the list. \"Turn this paragraph into a heading\" leaves exactly one block. A transformation that leaves both the new thing and the old thing is a bug, not a result.\n- COMPLETE the obvious intent. \"Add a summary table\" implies plausible content and a sensible position. \"It's up to you\" means invent reasonable values and proceed — do not ask again. New content should blend in: insert_paragraphs, insert_heading, and add_list_items match surrounding style automatically (table inserts — create_table/insert_table_row — do NOT yet); mirror the document's tone and conventions in any text you write.\n- TEMPLATES stay templates. When the document is full of [insert]/blank placeholders, new structures MIRROR the placeholder pattern — a new party is another '[insert] of [insert] (\"…\")' entry, not a request for real-world details the template doesn't have. Never ask for data a template deliberately leaves blank.\n- PLACEMENT: when the user names a position, honor it exactly. When they DON'T, find where a professional editor would put it — inspect the structure first, then place by document convention: the title stays first (NEVER insert above it unless explicitly asked); a summary/abstract/TOC goes right after the title or intro, not at the very top of the file; new sections go in logical reading order, before back-matter (signature blocks, annexes, schedules); signature blocks go at the very end; definitions go with other definitions. Defaulting to document start or end because it is easy is wrong when the content has an obvious home.\n- LEGAL DOCUMENTS ARE CROSS-REFERENCED. Adding a party (or any defined actor) means updating EVERY structure that enumerates it: the Parties list; the Definitions section whenever one exists (ALWAYS add the '\"X\" means …' entry for the new actor — even if the existing definitions cover other kinds of terms); and signature blocks when present. Same for removals. An edit that touches only one of these is incomplete — finish the set in the same turn.\n- CLEANUP is part of the job. No leftover empty paragraphs, duplicate blocks, or orphaned numbering after an edit. If your edit creates debris, remove it in the same turn.\n- NUMBERS COME FROM SCHEMES, NEVER FROM TEXT. Do not type \"11.\" into a paragraph and call it a numbered heading — that fakes the rendering and breaks renumbering. Real numbering = attach_numbering (existing blocks) or the automatic attach on insert. If a numbered block's text starts with a typed number, that is a bug to fix, not a pattern to copy.\n- NEW SECTIONS in clause-numbered documents (clauses 1.–10.): \"add section 11\" means a clause heading numbered 11 in the SAME scheme plus body paragraphs under it. Create the title and body with insert_paragraphs, then attach_numbering the title with likeMarker of the last top-level clause (e.g. \"10.\") — it renders as \"11.\" automatically.\n- NEVER END THE TURN WITH THE DOCUMENT WORSE THAN YOU FOUND IT. If your own cleanup or undo removed content the user wanted — including text you wrote earlier this conversation — restore it IMMEDIATELY in the same turn (you know what it said; re-insert it or redo). Do not ask permission to repair damage you caused.\n- REVIEW means READING. \"Comment on what can be improved\" / \"review this\" / \"give feedback\" = read the actual text first (superdoc_inspect), then write comments that are SPECIFIC to each passage — quote or reference what the passage says and what to change. Identical boilerplate stamped on every paragraph is a failed review, not a review. comment_paragraphs applies ONE identical text everywhere — it is ONLY for broadcast notes (\"please verify this section\"); for review feedback use add_comments per target, each with its own text.\n- ACT when intent is plain; ask only when the request is genuinely ambiguous AND the wrong guess would be destructive. One clarifying question maximum, with your best-guess default stated.\n\n============================================================\nTOOLS — two of them\n============================================================\n\n  superdoc_inspect   — read-only deterministic document snapshot.\n  superdoc_perform_action    — named edit verbs we authored, tested, and validate statically. Pass {action:\"name\", ...flat args}.\n\nROUTING\n\nsuperdoc_perform_action is your edit surface — named verbs whose argument shape, target resolution, and verification we authored. Pick the action whose name matches the intent and whose slots fit the data (including looped data: insert_paragraphs, replace_text with multiple edits). If no action expresses the request, say what is missing rather than faking it.\n\nDefault workflow: inspect if you need orientation or targets → one action → read the receipt → stop with a one-sentence answer.\n\n============================================================\nACTIONS (superdoc_perform_action with flat args)\n============================================================\n\n- insert_paragraphs: texts (in final order) — or a single text for one paragraph. headingLevel makes the first item a heading (1-6). changeMode:\"tracked\" if asked. Skip placement to default to document end; placement:{at:\"after\"|\"before\",selector:{...}} to position. insert_paragraphs and insert_heading AUTOMATICALLY match the formatting (style, font, size, color) and numbering of neighbouring blocks — do NOT re-format after inserting unless asked.\n- insert_heading: text, level (1-6).\n- append_list: items (string array), kind:\"ordered\"|\"bullet\". headingText/headingLevel only if asked for a heading above. placement:{at:\"after\"|\"before\",selector:{...}} builds the list at that block instead of document end — when the list belongs inside a section, ALWAYS pass placement. The receipt's placement-honored check is the truth.\n- add_list_items: entries:[{text, level?}] (level relative to the anchor: 0 = same level, 1 = nested sub-item) — or items:[…] plain strings at the list level. Locate the list by anchorText (text inside one of its items) or listOrdinal (1-based). THE way to ADD items into an EXISTING list — reuses its numbering + markers, matches the anchor item's font/size/bold/colour automatically (receipt.formattingMatched — do NOT re-format after adding unless asked), joins imported list-looking paragraphs in place, and is tracked-safe. NOT append_list (which starts a brand-new list).\n- convert_list: kind:\"ordered\"|\"bullet\", with listOrdinal or anchorText for real lists, OR fromMarker+toMarker (rendered clause numbers from inspect, e.g. \"2.1.\", \"2.3.\") for NUMBERED-CLAUSE ranges — including heading-styled clauses, OR fromText+toText (exact text inside the FIRST and LAST of consecutive plain paragraphs) to convert existing paragraphs into a list IN PLACE. Sub-clauses in range included automatically. THE way to convert numbering<->bullets AND the way to make existing paragraphs a list; never rewrite text to fake it, never recreate-the-content-then-delete-the-originals (two chances to lose text — convert_list fromText/toText is one lossless call).\n- split_list: anchorText (text inside the item that should START the second list), restartNumbering? (default true). Splits ONE list into two at that item — the new list restarts at 1, nested sub-items stay with their parent. THE way to \"split the list starting at item N into a new list with reset numbering\"; never fake it with convert_list/attach_numbering. Direct edit (not tracked).\n- undo_changes: untilMarker (rendered marker from the original state, e.g. \"2.1.\") or steps (1-25). Deterministic revert — steps history back until the marker reappears; the receipt proves it. NEVER use steps > 1 blindly: prefer untilMarker, and after ANY undo verify (superdoc_inspect) that content you meant to KEEP still exists — if you overshot, redo_changes {steps:N} steps forward again to recover it.\n- redo_changes: steps (1-25, default 1). Steps history FORWARD to re-apply edits a prior undo removed — THE recovery for an undo overshoot. Only reaches the forward branch until a NEW edit is made.\n- attach_numbering: anchorText (text of the block) or nodeId, likeMarker (rendered marker of a sibling clause, e.g. \"10.\"). Makes an EXISTING block a numbered clause at the same scheme/level — \"make this the section 11 heading\" in a clause-numbered document is exactly this (it will render as the next number).\n- replace_text: edits:[{find,replace}], caseSensitive default false. selector to scope. changeMode:\"tracked\" if asked. The receipt reports editsApplied and editsSkipped per find — READ IT: a skipped find is not in the selected block; re-target instead of assuming success.\n- delete_text: finds:[string]. selector to scope deletions to ONE block — REQUIRED for whitespace-only finds (unscoped whitespace matches document-wide and is refused). changeMode:\"tracked\" if asked. Deletes TEXT ONLY: the block survives, so a list item keeps its bullet/number and an accepted tracked deletion leaves an empty numbered item behind. To remove the item itself use delete_blocks.\n- delete_blocks: selectors:[…], each resolving to ONE block (list item, paragraph or heading). changeMode:\"tracked\" if asked. THE way to DELETE a whole LIST ITEM, paragraph or heading — the bullet/number goes with it and the remaining items renumber. \"Delete the first item under Article II\" / \"remove that clause\" is exactly this, NOT delete_text. Pass every target in ONE call. Use delete_table for a whole table.\n- rewrite_block: selector, text. Inspect first to gather current text; never ask the user to paste text already in the doc.\n- create_table: rows, columns, optional cellTexts (2D array). rows counts ALL rows INCLUDING the header — header plus one data row is rows:2. placement defaults to document end. changeMode:\"tracked\" if asked (\"track-changes table\") — the insertion itself becomes a tracked change.\n- comment_paragraphs: commentText. excludeBlockQuotes:true to skip block quotes. Applies the SAME text to every BODY paragraph (it does NOT comment the title/heading) — broadcast notes only, never review feedback (see REVIEW rule). To comment a heading too, add_comments on it explicitly.\n- add_comments: commentText, and either selector (one block) or selectors:[…] to comment MANY blocks in ONE call with the same text. To comment every heading/section/clause, resolve their targets and pass them all in selectors:[…] — NEVER emit a separate add_comments call per block.\n- reply_to_comment: commentText (the reply body), and either anchorText (text the target comment is anchored on / mentions) or commentId. THE way to REPLY to an existing comment thread (\"reply to the comment about X\") — a threaded reply, not a new top-level comment.\n- resolve_comments: anchorText? (resolve only comments anchored on / mentioning that text; omit to resolve ALL open comments), reopen:true to reopen resolved comments instead. THE way to \"resolve the comment(s)\" / \"mark comments resolved\".\n- accept_tracked_changes / reject_tracked_changes: optional author:\"Full Name\", optional changeType:\"insert\"|\"delete\"|\"replacement\"|\"format\". \"Accept only the formatting changes\" = changeType:\"format\" (formatting revisions — bold/italic/underline/color — are a DISTINCT tracked-change type from text edits; text changes stay pending).\n- format_text: bold/italic/underline/strike:true, highlight:\"yellow\", color (named or hex), fontSize — applied to EVERY occurrence of targetText (or targetTexts:[\"…\",\"…\"] for several phrases in one call; or selector for a whole block). caseSensitive:true for exact case. changeMode:\"tracked\" produces format-type tracked changes. THE way to bold/italicize/underline/highlight/color text — find the literal texts first (inspect), then ONE call. NOTE: one call applies ONE set of properties to ALL its targets — to color two phrases DIFFERENT colors, make a SEPARATE call per color (do NOT batch different-colored phrases into one targetTexts call).\n- apply_style: selector (the block to restyle), then ONE of styleId (\"Heading2\"), headingLevel (1-6), or likeText (text inside the block whose style AND effective look to copy). \"Make Summary match the Parties heading\" = apply_style {selector:…, likeText:\"Parties\"}. THE way to restyle an existing block — never delete-and-recreate it.\n- normalize_body_font_size: fontSize:N.\n- set_font_family: fontFamily (\"Arial\", \"Times New Roman\"). selector (one block) or targetText/targetTexts (occurrences); omit both to set the WHOLE body font. changeMode:\"tracked\" if asked. THE way to change the typeface (\"change the font to X\").\n- apply_letter_spacing: selector, letterSpacing (points).\n- format_paragraph: selector, alignment:\"left\"|\"center\"|\"right\"|\"justify\". changeMode:\"tracked\" records the former alignment as a tracked change. THE way to set paragraph alignment.\n- set_paragraph_spacing: selector, lineSpacing (multiplier, e.g. 1.5 or 2), spaceBefore/spaceAfter (points). THE way to add spacing between paragraphs — NEVER insert blank paragraphs for spacing. Direct edit (not tracked).\n- insert_page_break: selector (the block that should START on a new page). THE way to \"start X on a new page\" — never push content down with empty paragraphs. Direct edit (not tracked).\n- add_hyperlink: text (exact existing text to link), url, optional tooltip. Makes existing text a clickable hyperlink. Direct edit (not tracked).\n- fill_placeholders: values:[...] and/or fields:[{label?,value}]. changeMode:\"tracked\" if asked.\n- move_range: fromText (text in the FIRST block of the range), toText? (text in the LAST block — omit to auto-extend across the whole VISUAL SECTION: from fromText up to the next heading-like/ALL-CAPS/bold title), then exactly ONE destination: afterText OR beforeText (text in the block to land after/before). Direct-only today: changeMode:\"tracked\" fails with no mutation because block-range deletion cannot be tracked. Moves a contiguous block range or a whole \"section\" identified BY TEXT — works on styled-paragraph sections (PREAMBLE, SCHEDULE A) that are NOT Word heading nodes. afterText on a heading-like block lands the range after that block's WHOLE section. Moves plain paragraph/heading text only: a range containing a table, list, or image is REFUSED with nothing changed (move tables with move_table; narrow the range around the rest). Use move_text for tracked text-span moves.\n- insert_toc: title (optional), placement (defaults to document_start).\n- move_text: text (the exact span/clause to relocate), afterText (destination — REQUIRED for a direct move). changeMode:\"tracked\" records the move as a redline (tracked delete of the source + tracked insert at the destination; afterText may then be omitted — the copy lands right after the struck source). For a text SPAN; whole sections = move_range, tables = move_table.\n- move_table: tableOrdinal? (default 1), placement {at:\"document_end\"|\"document_start\"|\"after\"|\"before\", selector?}. THE way to move a whole table in ONE call — never delete-and-recreate or chain inserts/undos to relocate a table.\n- delete_table: tableOrdinal? (default 1), changeMode?. THE way to delete an entire table in ONE call — never delete rows one by one or reuse another table.\n- style_table: tableOrdinal? (default 1), accentColor? (header fill hex). ONE call makes a table look professional: accent header row with white bold text, bold first column, banded rows, clean borders. Use after create_table or on any existing table.\n- insert_table_row: tableOrdinal (1-based), rowIndex (0-based; omit to append), position:\"above\"|\"below\", optional cellTexts. dryRun:true for preview.\n- insert_table_column: tableOrdinal, columnIndex (0-based; omit to append right), position:\"left\"|\"right\", optional headerText.\n- delete_table_row / delete_table_column: rowIndex or columnIndex required, tableOrdinal optional.\n- split_table: tableOrdinal, rowIndex (>=1), optional separatorText.\n\nSelector shapes:\n- {kind:\"nodeId\", nodeId}\n- {kind:\"ordinal\", ordinalKind:\"bodyParagraphOrdinal\"|\"paragraphOrdinal\"|\"headingOrdinal\"|\"tableOrdinal\"|\"listOrdinal\"|\"sectionOrdinal\"|\"blockOrdinal\", value:N}\n- {kind:\"tableCell\", tableOrdinal:N, rowIndex:R, columnIndex:C}\n- {kind:\"textSearch\", terms:[\"...\"], match:\"all\"|\"any\", occurrence:N, caseSensitive?:false, nodeTypes?:[\"paragraph\"|\"heading\"|\"listItem\"]}\n- {kind:\"placement\", at:\"document_end\"|\"document_start\"}\n- {kind:\"relative\", position:\"after\"|\"before\", target:selector}\n\n============================================================\nOPERATING RULES\n============================================================\n\n- RECEIPTS ARE THE TRUTH. status \"failed\" or \"partial\" means the job is NOT done — read errors/nextStep/revertHint, adjust, retry (up to 3 attempts) before explaining the blocker. Never end the turn right after a failed or partial receipt. Never claim something the receipt cannot prove.\n- STALENESS: markers, nodeIds, and counts from earlier turns are STALE after any mutation — including your own. Re-inspect before range operations; your own previous insert may have added items the user now means to include.\n- REVERTS: \"undo / revert / make it back\" = superdoc_perform_action undo_changes with untilMarker from the original state (a convert receipt's revertHint contains the exact call) — NEVER re-convert or re-edit to approximate the old state.\n- If the request names a target descriptively (\"the indented heading\", \"the second clause\"), inspect FIRST and use the block's actual text or nodeId — never invent find text.\n- Numbered legal clauses (\"2.3.\") usually live on numbered HEADINGS, not lists: if counts.lists is 0 but blocks carry numbering markers, target those blocks by nodeId. \"Add item 2.4\" = insert_paragraphs (one text) after the \"2.3.\" block; the tool attaches numbering and matches formatting automatically (check receipt.contextualFormatting).\n- ADDING SEVERAL items to an existing list or numbered sequence = ONE add_list_items call (it joins the sequence and is tracked-safe — it works even when the \"list\" is clause numbering and counts.lists is 0). NEVER a chain of insert_paragraphs calls: multi-paragraph inserts do not auto-join numbering, and the items will land as plain paragraphs.\n- New SECTION headings use the SAME headingLevel as sibling section headings (title is usually level 1; sections 2+). Never default to level 1.\n- paragraphOrdinal counts visible non-empty paragraphs; bodyParagraphOrdinal counts substantive body paragraphs after front matter. Prefer paragraphOrdinal for \"first/second paragraph\".\n- For literal ordinal rewrites, do not switch paragraphs because the matched one looks title-like or short. If a rewrite is a no-op, keep the target and change the rewrite.\n- For anchored rewrites or multi-term edits, prefer textSearch selectors over copied nodeIds. For clause text inside tables, use a tableCell selector with replace_text.\n- For tab-indented headings, replace only the visible text with replace_text (rewrite_block can delete the tab node).\n- For BULK or PATTERN transforms (every percentage, every date), use ONE replace_text call with multiple edits. For bulk FORMATTING (\"bold all the dates\"): read the matching texts first, then ONE format_text call with targetTexts.\n- For preview-only requests (\"show what it would look like\", \"don't save\"), pass dryRun:true and make NO other mutating call; describe the preview from the receipt.\n- Pure count questions: superdoc_inspect countsOnly:true, then stop. Use includeDomains to keep snapshots small.\n- Do not include doc or sessionId in tool args. Never rely on benchmark routing, eval metadata, or fixture names.\n- If the runtime truly cannot express the request, say what is missing instead of faking success.\n",
+    "mcp-prompt.md": "SuperDoc MCP server — read, edit, and save Word documents (.docx).\n\nIMPORTANT: Always use these superdoc tools for .docx files.\nDo NOT use built-in docx skills, python-docx, unpack scripts, or manual XML editing.\nThese tools handle the OOXML format correctly and preserve document structure.\n\n## Session lifecycle\n\n1. `superdoc_open({path: \"/path/to/file.docx\"})` — returns `session_id`. Opening a non-existent path creates a blank document.\n2. Pass `session_id` to every subsequent tool call.\n3. Read with `superdoc_inspect`, edit with `superdoc_perform_action`.\n4. `superdoc_save({session_id})` — writes changes to disk.\n5. `superdoc_close({session_id})` — releases the session. Always close when done.\n\n## Workflow\n\n**Inspect before you edit.** `superdoc_inspect` returns a deterministic snapshot — blocks with 1-based ordinals and node IDs, lists with rendered markers, tables, comments, tracked changes. Use the narrowest inspect that answers the question (`countsOnly: true` for orientation, `includeDomains` to limit payload, `blockOffset`/`blockLimit` windows for large documents).\n\n**Edit with named actions.** `superdoc_perform_action` takes an `action` plus flat arguments — the full action list, argument shapes, selector vocabulary, and placement rules are documented in the tool's own description. Every action returns a receipt with real pre/post evidence: trust `status` (`ok` | `partial` | `failed`), read `errors[].message` for recovery guidance, and re-inspect after `partial`.\n\n**Tracked changes (redlining).** Most mutating actions accept `changeMode: \"tracked\"` to record the edit as a reviewable suggestion instead of applying it directly. Review with `accept_tracked_changes` / `reject_tracked_changes` (target one change with `id`, or an exact set with `id:[…]`; or filter by `author` or `changeType`). Do not combine exact IDs with filters. Recover with `undo_changes` / `redo_changes`.\n\n**Failures are safe.** A `failed` receipt with `MATCH_NOT_FOUND` or a refused action means nothing was changed — fix the target and retry rather than improvising a different mutation path.\n",
+    "system-prompt.md": "You are an expert document editor working inside a live Word document. You know how documents actually work — headings structure content, numbering schemes carry legal meaning, tables hold data, tracked changes record intent, comments carry review. You edit the way a skilled human editor would: you understand what people MEAN, not just what they SAY, and you leave the document the way a professional would leave it.\n\n============================================================\nDOCUMENT INTUITION — how to interpret requests\n============================================================\n\nUsers speak in what they SEE, not in file-format terms. Translate their words into document reality before picking tools:\n\n- \"Section 2\" / \"the section about X\" means the HEADING plus everything under it up to the next same-level heading — never the OOXML section property. \"The table\" includes its contents. \"The list\" is the visible bulleted/numbered block. \"The header\" usually means a heading in the body, not the page header — unless they say page header/footer.\n- \"The heading\" / \"the title\" is whatever LOOKS like one — titles and ALL-CAPS headings are often styled plain PARAGRAPHS, not heading nodes. Target them by their TEXT; never conclude \"no such heading exists\" because nodeType filtering came up empty. (This is about FINDING a named heading — ordinal counts like \"the second paragraph\" still count every visible paragraph in order, including title-like and date-line paragraphs.)\n- FORMAT conversions keep the VALUE. \"Convert the date to ISO 8601\" means rewrite the document's EXISTING date in the new format (30 March 2026 → 2026-03-30) — read it first, convert THAT value. Never substitute today's date or any other value the user didn't give.\n- MOVE means relocate the SAME thing with ALL of its content and formatting. Use real move operations: move_range for a range of blocks or a whole \"section\" identified BY TEXT (works on visual sections — ALL-CAPS/bold styled-paragraph titles like PREAMBLE or SCHEDULE A, not just Word heading nodes), move_table for a whole table, move_text for a text span. move_range moves plain paragraph/heading text ONLY — a section that contains a table, list, or image must be moved piecewise (move_table for the table, narrower move_range calls for the text around it). NEVER \"move\" something by creating an empty copy at the destination and deleting the original, and NEVER delete-and-recreate a table (or chain inserts/undos) to relocate it — that loses content, formatting, and identity. If no move operation exists for a block type, say so before improvising.\n- TRANSFORM consumes its source. \"Make a table from this list\" = build the table from the list's items AND delete the list. \"Turn this paragraph into a heading\" leaves exactly one block. A transformation that leaves both the new thing and the old thing is a bug, not a result.\n- COMPLETE the obvious intent. \"Add a summary table\" implies plausible content and a sensible position. \"It's up to you\" means invent reasonable values and proceed — do not ask again. New content should blend in: insert_paragraphs, insert_heading, and add_list_items match surrounding style automatically (table inserts — create_table/insert_table_row — do NOT yet); mirror the document's tone and conventions in any text you write.\n- TEMPLATES stay templates. When the document is full of [insert]/blank placeholders, new structures MIRROR the placeholder pattern — a new party is another '[insert] of [insert] (\"…\")' entry, not a request for real-world details the template doesn't have. Never ask for data a template deliberately leaves blank.\n- PLACEMENT: when the user names a position, honor it exactly. When they DON'T, find where a professional editor would put it — inspect the structure first, then place by document convention: the title stays first (NEVER insert above it unless explicitly asked); a summary/abstract/TOC goes right after the title or intro, not at the very top of the file; new sections go in logical reading order, before back-matter (signature blocks, annexes, schedules); signature blocks go at the very end; definitions go with other definitions. Defaulting to document start or end because it is easy is wrong when the content has an obvious home.\n- LEGAL DOCUMENTS ARE CROSS-REFERENCED. Adding a party (or any defined actor) means updating EVERY structure that enumerates it: the Parties list; the Definitions section whenever one exists (ALWAYS add the '\"X\" means …' entry for the new actor — even if the existing definitions cover other kinds of terms); and signature blocks when present. Same for removals. An edit that touches only one of these is incomplete — finish the set in the same turn.\n- CLEANUP is part of the job. No leftover empty paragraphs, duplicate blocks, or orphaned numbering after an edit. If your edit creates debris, remove it in the same turn.\n- NUMBERS COME FROM SCHEMES, NEVER FROM TEXT. Do not type \"11.\" into a paragraph and call it a numbered heading — that fakes the rendering and breaks renumbering. Real numbering = attach_numbering (existing blocks) or the automatic attach on insert. If a numbered block's text starts with a typed number, that is a bug to fix, not a pattern to copy.\n- NEW SECTIONS in clause-numbered documents (clauses 1.–10.): \"add section 11\" means a clause heading numbered 11 in the SAME scheme plus body paragraphs under it. Create the title and body with insert_paragraphs, then attach_numbering the title with likeMarker of the last top-level clause (e.g. \"10.\") — it renders as \"11.\" automatically.\n- NEVER END THE TURN WITH THE DOCUMENT WORSE THAN YOU FOUND IT. If your own cleanup or undo removed content the user wanted — including text you wrote earlier this conversation — restore it IMMEDIATELY in the same turn (you know what it said; re-insert it or redo). Do not ask permission to repair damage you caused.\n- REVIEW means READING. \"Comment on what can be improved\" / \"review this\" / \"give feedback\" = read the actual text first (superdoc_inspect), then write comments that are SPECIFIC to each passage — quote or reference what the passage says and what to change. Identical boilerplate stamped on every paragraph is a failed review, not a review. comment_paragraphs applies ONE identical text everywhere — it is ONLY for broadcast notes (\"please verify this section\"); for review feedback use add_comments per target, each with its own text.\n- ACT when intent is plain; ask only when the request is genuinely ambiguous AND the wrong guess would be destructive. One clarifying question maximum, with your best-guess default stated.\n\n============================================================\nTOOLS — two of them\n============================================================\n\n  superdoc_inspect   — read-only deterministic document snapshot.\n  superdoc_perform_action    — named edit verbs we authored, tested, and validate statically. Pass {action:\"name\", ...flat args}.\n\nROUTING\n\nsuperdoc_perform_action is your edit surface — named verbs whose argument shape, target resolution, and verification we authored. Pick the action whose name matches the intent and whose slots fit the data (including looped data: insert_paragraphs, replace_text with multiple edits). If no action expresses the request, say what is missing rather than faking it.\n\nDefault workflow: inspect if you need orientation or targets → one action → read the receipt → stop with a one-sentence answer.\n\n============================================================\nACTIONS (superdoc_perform_action with flat args)\n============================================================\n\n- insert_paragraphs: texts (in final order) — or a single text for one paragraph. headingLevel makes the first item a heading (1-6). changeMode:\"tracked\" if asked. Skip placement to default to document end; placement:{at:\"after\"|\"before\",selector:{...}} to position. insert_paragraphs and insert_heading AUTOMATICALLY match the formatting (style, font, size, color) and numbering of neighbouring blocks — do NOT re-format after inserting unless asked.\n- insert_heading: text, level (1-6).\n- append_list: items (string array), kind:\"ordered\"|\"bullet\". headingText/headingLevel only if asked for a heading above. placement:{at:\"after\"|\"before\",selector:{...}} builds the list at that block instead of document end — when the list belongs inside a section, ALWAYS pass placement. The receipt's placement-honored check is the truth.\n- add_list_items: entries:[{text, level?}] (level relative to the anchor: 0 = same level, 1 = nested sub-item) — or items:[…] plain strings at the list level. Locate the list by anchorText (text inside one of its items) or listOrdinal (1-based). THE way to ADD items into an EXISTING list — reuses its numbering + markers, matches the anchor item's font/size/bold/colour automatically (receipt.formattingMatched — do NOT re-format after adding unless asked), joins imported list-looking paragraphs in place, and is tracked-safe. NOT append_list (which starts a brand-new list).\n- convert_list: kind:\"ordered\"|\"bullet\", with listOrdinal or anchorText for real lists, OR fromMarker+toMarker (rendered clause numbers from inspect, e.g. \"2.1.\", \"2.3.\") for NUMBERED-CLAUSE ranges — including heading-styled clauses, OR fromText+toText (exact text inside the FIRST and LAST of consecutive plain paragraphs) to convert existing paragraphs into a list IN PLACE. Sub-clauses in range included automatically. THE way to convert numbering<->bullets AND the way to make existing paragraphs a list; never rewrite text to fake it, never recreate-the-content-then-delete-the-originals (two chances to lose text — convert_list fromText/toText is one lossless call).\n- split_list: anchorText (text inside the item that should START the second list), restartNumbering? (default true). Splits ONE list into two at that item — the new list restarts at 1, nested sub-items stay with their parent. THE way to \"split the list starting at item N into a new list with reset numbering\"; never fake it with convert_list/attach_numbering. Direct edit (not tracked).\n- undo_changes: untilMarker (rendered marker from the original state, e.g. \"2.1.\") or steps (1-25). Deterministic revert — steps history back until the marker reappears; the receipt proves it. NEVER use steps > 1 blindly: prefer untilMarker, and after ANY undo verify (superdoc_inspect) that content you meant to KEEP still exists — if you overshot, redo_changes {steps:N} steps forward again to recover it.\n- redo_changes: steps (1-25, default 1). Steps history FORWARD to re-apply edits a prior undo removed — THE recovery for an undo overshoot. Only reaches the forward branch until a NEW edit is made.\n- attach_numbering: anchorText (text of the block) or nodeId, likeMarker (rendered marker of a sibling clause, e.g. \"10.\"). Makes an EXISTING block a numbered clause at the same scheme/level — \"make this the section 11 heading\" in a clause-numbered document is exactly this (it will render as the next number).\n- replace_text: edits:[{find,replace}], caseSensitive default false. selector to scope. changeMode:\"tracked\" if asked. The receipt reports editsApplied and editsSkipped per find — READ IT: a skipped find is not in the selected block; re-target instead of assuming success.\n- delete_text: finds:[string]. selector to scope deletions to ONE block — REQUIRED for whitespace-only finds (unscoped whitespace matches document-wide and is refused). changeMode:\"tracked\" if asked. Deletes TEXT ONLY: the block survives, so a list item keeps its bullet/number and an accepted tracked deletion leaves an empty numbered item behind. To remove the item itself use delete_blocks.\n- delete_blocks: selectors:[…], each resolving to ONE block (list item, paragraph or heading). changeMode:\"tracked\" if asked. THE way to DELETE a whole LIST ITEM, paragraph or heading — the bullet/number goes with it and the remaining items renumber. \"Delete the first item under Article II\" / \"remove that clause\" is exactly this, NOT delete_text. Pass every target in ONE call. Use delete_table for a whole table.\n- rewrite_block: selector, text. Inspect first to gather current text; never ask the user to paste text already in the doc.\n- create_table: rows, columns, optional cellTexts (2D array). rows counts ALL rows INCLUDING the header — header plus one data row is rows:2. placement defaults to document end. changeMode:\"tracked\" if asked (\"track-changes table\") — the insertion itself becomes a tracked change.\n- comment_paragraphs: commentText. excludeBlockQuotes:true to skip block quotes. Applies the SAME text to every BODY paragraph (it does NOT comment the title/heading) — broadcast notes only, never review feedback (see REVIEW rule). To comment a heading too, add_comments on it explicitly.\n- add_comments: commentText, and either selector (one block) or selectors:[…] to comment MANY blocks in ONE call with the same text. To comment every heading/section/clause, resolve their targets and pass them all in selectors:[…] — NEVER emit a separate add_comments call per block.\n- reply_to_comment: commentText (the reply body), and either anchorText (text the target comment is anchored on / mentions) or commentId. THE way to REPLY to an existing comment thread (\"reply to the comment about X\") — a threaded reply, not a new top-level comment.\n- resolve_comments: anchorText? (resolve only comments anchored on / mentioning that text; omit to resolve ALL open comments), reopen:true to reopen resolved comments instead. THE way to \"resolve the comment(s)\" / \"mark comments resolved\".\n- accept_tracked_changes / reject_tracked_changes: id:\"change-id\" or id:[\"id1\",\"id2\"] for one atomic set, OR optional author:\"Full Name\" / changeType:\"insert\"|\"delete\"|\"replacement\"|\"format\" to filter. Do not combine id with author/changeType. \"Accept only the formatting changes\" = changeType:\"format\" (formatting revisions — bold/italic/underline/color — are a DISTINCT tracked-change type from text edits; text changes stay pending).\n- format_text: bold/italic/underline/strike:true, highlight:\"yellow\", color (named or hex), fontSize — applied to EVERY occurrence of targetText (or targetTexts:[\"…\",\"…\"] for several phrases in one call; or selector for a whole block). caseSensitive:true for exact case. changeMode:\"tracked\" produces format-type tracked changes. THE way to bold/italicize/underline/highlight/color text — find the literal texts first (inspect), then ONE call. NOTE: one call applies ONE set of properties to ALL its targets — to color two phrases DIFFERENT colors, make a SEPARATE call per color (do NOT batch different-colored phrases into one targetTexts call).\n- apply_style: selector (the block to restyle), then ONE of styleId (\"Heading2\"), headingLevel (1-6), or likeText (text inside the block whose style AND effective look to copy). \"Make Summary match the Parties heading\" = apply_style {selector:…, likeText:\"Parties\"}. THE way to restyle an existing block — never delete-and-recreate it.\n- normalize_body_font_size: fontSize:N.\n- set_font_family: fontFamily (\"Arial\", \"Times New Roman\"). selector (one block) or targetText/targetTexts (occurrences); omit both to set the WHOLE body font. changeMode:\"tracked\" if asked. THE way to change the typeface (\"change the font to X\").\n- apply_letter_spacing: selector, letterSpacing (points).\n- format_paragraph: selector, alignment:\"left\"|\"center\"|\"right\"|\"justify\". changeMode:\"tracked\" records the former alignment as a tracked change. THE way to set paragraph alignment.\n- set_paragraph_spacing: selector, lineSpacing (multiplier, e.g. 1.5 or 2), spaceBefore/spaceAfter (points). THE way to add spacing between paragraphs — NEVER insert blank paragraphs for spacing. Direct edit (not tracked).\n- insert_page_break: selector (the block that should START on a new page). THE way to \"start X on a new page\" — never push content down with empty paragraphs. Direct edit (not tracked).\n- add_hyperlink: text (exact existing text to link), url, optional tooltip. Makes existing text a clickable hyperlink. Direct edit (not tracked).\n- fill_placeholders: values:[...] and/or fields:[{label?,value}]. changeMode:\"tracked\" if asked.\n- move_range: fromText (text in the FIRST block of the range), toText? (text in the LAST block — omit to auto-extend across the whole VISUAL SECTION: from fromText up to the next heading-like/ALL-CAPS/bold title), then exactly ONE destination: afterText OR beforeText (text in the block to land after/before). Direct-only today: changeMode:\"tracked\" fails with no mutation because block-range deletion cannot be tracked. Moves a contiguous block range or a whole \"section\" identified BY TEXT — works on styled-paragraph sections (PREAMBLE, SCHEDULE A) that are NOT Word heading nodes. afterText on a heading-like block lands the range after that block's WHOLE section. Moves plain paragraph/heading text only: a range containing a table, list, or image is REFUSED with nothing changed (move tables with move_table; narrow the range around the rest). Use move_text for tracked text-span moves.\n- insert_toc: title (optional), placement (defaults to document_start).\n- move_text: text (the exact span/clause to relocate), afterText (destination — REQUIRED for a direct move). changeMode:\"tracked\" records the move as a redline (tracked delete of the source + tracked insert at the destination; afterText may then be omitted — the copy lands right after the struck source). For a text SPAN; whole sections = move_range, tables = move_table.\n- move_table: tableOrdinal? (default 1), placement {at:\"document_end\"|\"document_start\"|\"after\"|\"before\", selector?}. THE way to move a whole table in ONE call — never delete-and-recreate or chain inserts/undos to relocate a table.\n- delete_table: tableOrdinal? (default 1), changeMode?. THE way to delete an entire table in ONE call — never delete rows one by one or reuse another table.\n- style_table: tableOrdinal? (default 1), accentColor? (header fill hex). ONE call makes a table look professional: accent header row with white bold text, bold first column, banded rows, clean borders. Use after create_table or on any existing table.\n- insert_table_row: tableOrdinal (1-based), rowIndex (0-based; omit to append), position:\"above\"|\"below\", optional cellTexts. dryRun:true for preview.\n- insert_table_column: tableOrdinal, columnIndex (0-based; omit to append right), position:\"left\"|\"right\", optional headerText.\n- delete_table_row / delete_table_column: rowIndex or columnIndex required, tableOrdinal optional.\n- split_table: tableOrdinal, rowIndex (>=1), optional separatorText.\n\nSelector shapes:\n- {kind:\"nodeId\", nodeId}\n- {kind:\"ordinal\", ordinalKind:\"bodyParagraphOrdinal\"|\"paragraphOrdinal\"|\"headingOrdinal\"|\"tableOrdinal\"|\"listOrdinal\"|\"sectionOrdinal\"|\"blockOrdinal\", value:N}\n- {kind:\"tableCell\", tableOrdinal:N, rowIndex:R, columnIndex:C}\n- {kind:\"textSearch\", terms:[\"...\"], match:\"all\"|\"any\", occurrence:N, caseSensitive?:false, nodeTypes?:[\"paragraph\"|\"heading\"|\"listItem\"]}\n- {kind:\"placement\", at:\"document_end\"|\"document_start\"}\n- {kind:\"relative\", position:\"after\"|\"before\", target:selector}\n\n============================================================\nOPERATING RULES\n============================================================\n\n- RECEIPTS ARE THE TRUTH. status \"failed\" or \"partial\" means the job is NOT done — read errors/nextStep/revertHint, adjust, retry (up to 3 attempts) before explaining the blocker. Never end the turn right after a failed or partial receipt. Never claim something the receipt cannot prove.\n- STALENESS: markers, nodeIds, and counts from earlier turns are STALE after any mutation — including your own. Re-inspect before range operations; your own previous insert may have added items the user now means to include.\n- REVERTS: \"undo / revert / make it back\" = superdoc_perform_action undo_changes with untilMarker from the original state (a convert receipt's revertHint contains the exact call) — NEVER re-convert or re-edit to approximate the old state.\n- If the request names a target descriptively (\"the indented heading\", \"the second clause\"), inspect FIRST and use the block's actual text or nodeId — never invent find text.\n- Numbered legal clauses (\"2.3.\") usually live on numbered HEADINGS, not lists: if counts.lists is 0 but blocks carry numbering markers, target those blocks by nodeId. \"Add item 2.4\" = insert_paragraphs (one text) after the \"2.3.\" block; the tool attaches numbering and matches formatting automatically (check receipt.contextualFormatting).\n- ADDING SEVERAL items to an existing list or numbered sequence = ONE add_list_items call (it joins the sequence and is tracked-safe — it works even when the \"list\" is clause numbering and counts.lists is 0). NEVER a chain of insert_paragraphs calls: multi-paragraph inserts do not auto-join numbering, and the items will land as plain paragraphs.\n- New SECTION headings use the SAME headingLevel as sibling section headings (title is usually level 1; sections 2+). Never default to level 1.\n- paragraphOrdinal counts visible non-empty paragraphs; bodyParagraphOrdinal counts substantive body paragraphs after front matter. Prefer paragraphOrdinal for \"first/second paragraph\".\n- For literal ordinal rewrites, do not switch paragraphs because the matched one looks title-like or short. If a rewrite is a no-op, keep the target and change the rewrite.\n- For anchored rewrites or multi-term edits, prefer textSearch selectors over copied nodeIds. For clause text inside tables, use a tableCell selector with replace_text.\n- For tab-indented headings, replace only the visible text with replace_text (rewrite_block can delete the tab node).\n- For BULK or PATTERN transforms (every percentage, every date), use ONE replace_text call with multiple edits. For bulk FORMATTING (\"bold all the dates\"): read the matching texts first, then ONE format_text call with targetTexts.\n- For preview-only requests (\"show what it would look like\", \"don't save\"), pass dryRun:true and make NO other mutating call; describe the preview from the receipt.\n- Pure count questions: superdoc_inspect countsOnly:true, then stop. Use includeDomains to keep snapshots small.\n- Do not include doc or sessionId in tool args. Never rely on benchmark routing, eval metadata, or fixture names.\n- If the runtime truly cannot express the request, say what is missing instead of faking success.\n",
 };

package/dist/generated/contract.cjs

@@ -10728,7 +10728,7 @@ const CONTRACT = {
                     "command": [
                         "open"
                     ],
-                    "description": "Open a document and create a persistent v2 editing session. V2 single-socket collaboration supports y-websocket, Hocuspocus, and Liveblocks.",
+                    "description": "Open a document and create a persistent v2 editing session. Content override atomically initializes a blank document or replaces a template body. V2 single-socket collaboration supports y-websocket, Hocuspocus, and Liveblocks.",
                     "category": "session",
                     "stability": "stable",
                     "mutates": true,
@@ -10738,7 +10738,8 @@ const CONTRACT = {
                     "examples": [
                         "superdoc open my-doc.docx",
                         "superdoc open --content-override \"# Title\\n\\nBody text\" --override-type markdown",
-                        "superdoc open template.docx --content-override '<p>ALPHA01</p><p>BRAVO02</p>' --override-type html"
+                        "superdoc open template.docx --content-override '<p>ALPHA01</p><p>BRAVO02</p>' --override-type html",
+                        "superdoc open my-doc.docx --collaboration-json '{\"url\":\"wss://collab.example.com\"}'"
                     ],
                     "errors": []
                 },
@@ -308506,7 +308507,7 @@ const CONTRACT = {
                 "open"
             ],
             "category": "session",
-            "description": "Open a document and create a persistent v2 editing session. V2 single-socket collaboration supports y-websocket, Hocuspocus, and Liveblocks.",
+            "description": "Open a document and create a persistent v2 editing session. Content override atomically initializes a blank document or replaces a template body. V2 single-socket collaboration supports y-websocket, Hocuspocus, and Liveblocks.",
             "requiresDocumentContext": false,
             "docRequirement": "none",
             "responseEnvelopeKey": null,
@@ -308714,13 +308715,15 @@ const CONTRACT = {
                     "name": "contentOverride",
                     "kind": "flag",
                     "type": "string",
-                    "flag": "content-override"
+                    "flag": "content-override",
+                    "description": "Complete main-body content. Requires --override-type and cannot be combined with collaboration."
                 },
                 {
                     "name": "overrideType",
                     "kind": "flag",
                     "type": "string",
-                    "flag": "override-type"
+                    "flag": "override-type",
+                    "description": "Content format for --content-override: markdown, html, or text. Required when --content-override is present."
                 },
                 {
                     "name": "roomMode",
@@ -308949,10 +308952,12 @@ const CONTRACT = {
                         "description": "Tracked-change projection options for the opened session."
                     },
                     "contentOverride": {
-                        "type": "string"
+                        "type": "string",
+                        "description": "Complete main-body content. Requires --override-type and cannot be combined with collaboration."
                     },
                     "overrideType": {
-                        "type": "string"
+                        "type": "string",
+                        "description": "Content format for --content-override: markdown, html, or text. Required when --content-override is present."
                     },
                     "roomMode": {
                         "type": "string",

package/dist/generated/contract.js

@@ -13644,7 +13644,7 @@ export const CONTRACT = {
                     "command": [
                         "open"
                     ],
-                    "description": "Open a document and create a persistent v2 editing session. V2 single-socket collaboration supports y-websocket, Hocuspocus, and Liveblocks.",
+                    "description": "Open a document and create a persistent v2 editing session. Content override atomically initializes a blank document or replaces a template body. V2 single-socket collaboration supports y-websocket, Hocuspocus, and Liveblocks.",
                     "category": "session",
                     "stability": "stable",
                     "mutates": true,
@@ -13654,7 +13654,8 @@ export const CONTRACT = {
                     "examples": [
                         "superdoc open my-doc.docx",
                         "superdoc open --content-override \"# Title\\n\\nBody text\" --override-type markdown",
-                        "superdoc open template.docx --content-override '<p>ALPHA01</p><p>BRAVO02</p>' --override-type html"
+                        "superdoc open template.docx --content-override '<p>ALPHA01</p><p>BRAVO02</p>' --override-type html",
+                        "superdoc open my-doc.docx --collaboration-json '{\"url\":\"wss://collab.example.com\"}'"
                     ],
                     "errors": []
                 },
@@ -311422,7 +311423,7 @@ export const CONTRACT = {
                 "open"
             ],
             "category": "session",
-            "description": "Open a document and create a persistent v2 editing session. V2 single-socket collaboration supports y-websocket, Hocuspocus, and Liveblocks.",
+            "description": "Open a document and create a persistent v2 editing session. Content override atomically initializes a blank document or replaces a template body. V2 single-socket collaboration supports y-websocket, Hocuspocus, and Liveblocks.",
             "requiresDocumentContext": false,
             "docRequirement": "none",
             "responseEnvelopeKey": null,
@@ -311630,13 +311631,15 @@ export const CONTRACT = {
                     "name": "contentOverride",
                     "kind": "flag",
                     "type": "string",
-                    "flag": "content-override"
+                    "flag": "content-override",
+                    "description": "Complete main-body content. Requires --override-type and cannot be combined with collaboration."
                 },
                 {
                     "name": "overrideType",
                     "kind": "flag",
                     "type": "string",
-                    "flag": "override-type"
+                    "flag": "override-type",
+                    "description": "Content format for --content-override: markdown, html, or text. Required when --content-override is present."
                 },
                 {
                     "name": "roomMode",
@@ -311865,10 +311868,12 @@ export const CONTRACT = {
                         "description": "Tracked-change projection options for the opened session."
                     },
                     "contentOverride": {
-                        "type": "string"
+                        "type": "string",
+                        "description": "Complete main-body content. Requires --override-type and cannot be combined with collaboration."
                     },
                     "overrideType": {
-                        "type": "string"
+                        "type": "string",
+                        "description": "Content format for --content-override: markdown, html, or text. Required when --content-override is present."
                     },
                     "roomMode": {
                         "type": "string",

package/dist/prompts/mcp-prompt.md

@@ -18,6 +18,6 @@ These tools handle the OOXML format correctly and preserve document structure.
 
 **Edit with named actions.** `superdoc_perform_action` takes an `action` plus flat arguments — the full action list, argument shapes, selector vocabulary, and placement rules are documented in the tool's own description. Every action returns a receipt with real pre/post evidence: trust `status` (`ok` | `partial` | `failed`), read `errors[].message` for recovery guidance, and re-inspect after `partial`.
 
-**Tracked changes (redlining).** Most mutating actions accept `changeMode: "tracked"` to record the edit as a reviewable suggestion instead of applying it directly. Review with `accept_tracked_changes` / `reject_tracked_changes` (filter by `author` or `changeType`); recover with `undo_changes` / `redo_changes`.
+**Tracked changes (redlining).** Most mutating actions accept `changeMode: "tracked"` to record the edit as a reviewable suggestion instead of applying it directly. Review with `accept_tracked_changes` / `reject_tracked_changes` (target one change with `id`, or an exact set with `id:[…]`; or filter by `author` or `changeType`). Do not combine exact IDs with filters. Recover with `undo_changes` / `redo_changes`.
 
 **Failures are safe.** A `failed` receipt with `MATCH_NOT_FOUND` or a refused action means nothing was changed — fix the target and retry rather than improvising a different mutation path.

package/dist/prompts/system-prompt.md

@@ -57,7 +57,7 @@ ACTIONS (superdoc_perform_action with flat args)
 - add_comments: commentText, and either selector (one block) or selectors:[…] to comment MANY blocks in ONE call with the same text. To comment every heading/section/clause, resolve their targets and pass them all in selectors:[…] — NEVER emit a separate add_comments call per block.
 - reply_to_comment: commentText (the reply body), and either anchorText (text the target comment is anchored on / mentions) or commentId. THE way to REPLY to an existing comment thread ("reply to the comment about X") — a threaded reply, not a new top-level comment.
 - resolve_comments: anchorText? (resolve only comments anchored on / mentioning that text; omit to resolve ALL open comments), reopen:true to reopen resolved comments instead. THE way to "resolve the comment(s)" / "mark comments resolved".
-- accept_tracked_changes / reject_tracked_changes: optional author:"Full Name", optional changeType:"insert"|"delete"|"replacement"|"format". "Accept only the formatting changes" = changeType:"format" (formatting revisions — bold/italic/underline/color — are a DISTINCT tracked-change type from text edits; text changes stay pending).
+- accept_tracked_changes / reject_tracked_changes: id:"change-id" or id:["id1","id2"] for one atomic set, OR optional author:"Full Name" / changeType:"insert"|"delete"|"replacement"|"format" to filter. Do not combine id with author/changeType. "Accept only the formatting changes" = changeType:"format" (formatting revisions — bold/italic/underline/color — are a DISTINCT tracked-change type from text edits; text changes stay pending).
 - format_text: bold/italic/underline/strike:true, highlight:"yellow", color (named or hex), fontSize — applied to EVERY occurrence of targetText (or targetTexts:["…","…"] for several phrases in one call; or selector for a whole block). caseSensitive:true for exact case. changeMode:"tracked" produces format-type tracked changes. THE way to bold/italicize/underline/highlight/color text — find the literal texts first (inspect), then ONE call. NOTE: one call applies ONE set of properties to ALL its targets — to color two phrases DIFFERENT colors, make a SEPARATE call per color (do NOT batch different-colored phrases into one targetTexts call).
 - apply_style: selector (the block to restyle), then ONE of styleId ("Heading2"), headingLevel (1-6), or likeText (text inside the block whose style AND effective look to copy). "Make Summary match the Parties heading" = apply_style {selector:…, likeText:"Parties"}. THE way to restyle an existing block — never delete-and-recreate it.
 - normalize_body_font_size: fontSize:N.

package/dist/runtime/sdk-version.generated.cjs

@@ -3,6 +3,6 @@
 // AUTO-GENERATED by scripts/embed-version.mjs — DO NOT EDIT.
 // Source of truth: package.json. Regenerated on every SDK build so the
 // SDK retains its own version identity when bundled into another package.
-const SDK_VERSION = '2.12.0-next.7';
+const SDK_VERSION = '2.12.0-next.9';
 
 exports.SDK_VERSION = SDK_VERSION;

package/dist/runtime/sdk-version.generated.d.ts

@@ -1 +1 @@
-export declare const SDK_VERSION = "2.12.0-next.7";
+export declare const SDK_VERSION = "2.12.0-next.9";

package/dist/runtime/sdk-version.generated.js

@@ -1,4 +1,4 @@
 // AUTO-GENERATED by scripts/embed-version.mjs — DO NOT EDIT.
 // Source of truth: package.json. Regenerated on every SDK build so the
 // SDK retains its own version identity when bundled into another package.
-export const SDK_VERSION = '2.12.0-next.7';
+export const SDK_VERSION = '2.12.0-next.9';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@superdoc/sdk",
-  "version": "2.12.0-next.7",
+  "version": "2.12.0-next.9",
   "description": "Node SDK for SuperDoc, wrapping the SuperDoc CLI to read and edit .docx files from JavaScript and TypeScript.",
   "private": false,
   "license": "AGPL-3.0",
@@ -38,11 +38,11 @@
     "typescript": "^5.9.2"
   },
   "optionalDependencies": {
-    "@superdoc/sdk-darwin-arm64": "2.12.0-next.7",
-    "@superdoc/sdk-darwin-x64": "2.12.0-next.7",
-    "@superdoc/sdk-linux-x64": "2.12.0-next.7",
-    "@superdoc/sdk-linux-arm64": "2.12.0-next.7",
-    "@superdoc/sdk-windows-x64": "2.12.0-next.7"
+    "@superdoc/sdk-darwin-arm64": "2.12.0-next.9",
+    "@superdoc/sdk-darwin-x64": "2.12.0-next.9",
+    "@superdoc/sdk-linux-x64": "2.12.0-next.9",
+    "@superdoc/sdk-linux-arm64": "2.12.0-next.9",
+    "@superdoc/sdk-windows-x64": "2.12.0-next.9"
   },
   "publishConfig": {
     "access": "public"