@superdoc/cli 0.35.0-next.7 → 0.35.0-next.9

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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@superdoc/cli",
-  "version": "0.35.0-next.7",
+  "version": "0.35.0-next.9",
   "description": "Command-line interface for SuperDoc: inspect, convert, and edit .docx files from a terminal or a script.",
   "type": "module",
   "license": "AGPL-3.0",
@@ -29,15 +29,15 @@
     "fast-glob": "^3.3.3",
     "happy-dom": "^20.3.4",
     "ws": "^8.18.0",
-    "superdoc": "2.15.0-next.6",
+    "superdoc": "2.15.0-next.7",
     "y-websocket": "^3.0.0",
     "yjs": "13.6.31"
   },
   "devDependencies": {
     "@hocuspocus/server": "^2.13.6",
-    "@superdoc/sdk": "2.12.0-next.7",
+    "@superdoc/sdk": "2.12.0-next.9",
     "@superdoc/document-api": "0.1.0-alpha.0",
-    "@superdoc/docx-engine": "0.14.0-next.5",
+    "@superdoc/docx-engine": "0.14.0-next.6",
     "@types/bun": "^1.3.8",
     "@types/node": "22.19.2",
     "@types/ws": "^8.5.13",
@@ -51,11 +51,11 @@
     "access": "public"
   },
   "optionalDependencies": {
-    "@superdoc/cli-darwin-arm64": "0.35.0-next.7",
-    "@superdoc/cli-darwin-x64": "0.35.0-next.7",
-    "@superdoc/cli-linux-x64": "0.35.0-next.7",
-    "@superdoc/cli-linux-arm64": "0.35.0-next.7",
-    "@superdoc/cli-windows-x64": "0.35.0-next.7"
+    "@superdoc/cli-darwin-arm64": "0.35.0-next.9",
+    "@superdoc/cli-darwin-x64": "0.35.0-next.9",
+    "@superdoc/cli-linux-x64": "0.35.0-next.9",
+    "@superdoc/cli-linux-arm64": "0.35.0-next.9",
+    "@superdoc/cli-windows-x64": "0.35.0-next.9"
   },
   "scripts": {
     "predev": "node scripts/ensure-superdoc-build.js",

package/skill/SKILL.md

@@ -8,7 +8,7 @@ description: Edit, query, and transform Word documents with the SuperDoc CLI v1
 Use SuperDoc CLI for DOCX work. Use v1 commands (canonical operations and their helper wrappers).
 Do not default to legacy commands unless explicitly needed for v0-style bulk workflows.
 
-Use `superdoc` if installed, or `npx @superdoc-dev/cli@latest` as a fallback.
+Use `superdoc` if installed, or `npx @superdoc/cli@latest` as a fallback.
 
 ## First Step: Discover Exact Params
 
@@ -41,7 +41,7 @@ superdoc close
 
 ### 2) Generate or seed a document body (recommended for synthetic/probe docs)
 
-Use `open --content-override` when you want to create a new body from Markdown, HTML, or plain text in one step.
+Use `open --content-override` to initialize a blank document or replace a template's main body from Markdown, HTML, or plain text in one step. Template styles, theme, section settings, headers, footers, and other non-body package content are retained.
 
 ```bash
 superdoc open --content-override "# Probe Title\n\nALPHA01" --override-type markdown