@superdoc-dev/sdk 1.8.0-next.8 → 1.8.0-next.81

package/tools/intent_dispatch_generated.py

@@ -83,6 +83,8 @@ def dispatch_intent_tool(
             return execute('doc.lists.attach', rest)
         elif action == 'detach':
             return execute('doc.lists.detach', rest)
+        elif action == 'delete':
+            return execute('doc.lists.delete', rest)
         elif action == 'indent':
             return execute('doc.lists.indent', rest)
         elif action == 'outdent':
@@ -136,5 +138,44 @@ def dispatch_intent_tool(
             return execute('doc.mutations.apply', rest)
         else:
             raise SuperDocError(f'Unknown action for superdoc_mutations: {action}', code='TOOL_DISPATCH_NOT_FOUND', details={'toolName': 'superdoc_mutations', 'action': action})
+    elif tool_name == 'superdoc_table':
+        action = args.get('action')
+        rest = {k: v for k, v in args.items() if k != 'action'}
+        if action == 'delete':
+            return execute('doc.tables.delete', rest)
+        elif action == 'set_layout':
+            return execute('doc.tables.setLayout', rest)
+        elif action == 'insert_row':
+            return execute('doc.tables.insertRow', rest)
+        elif action == 'delete_row':
+            return execute('doc.tables.deleteRow', rest)
+        elif action == 'set_row':
+            return execute('doc.tables.setRowHeight', rest)
+        elif action == 'set_row_options':
+            return execute('doc.tables.setRowOptions', rest)
+        elif action == 'insert_column':
+            return execute('doc.tables.insertColumn', rest)
+        elif action == 'delete_column':
+            return execute('doc.tables.deleteColumn', rest)
+        elif action == 'set_column':
+            return execute('doc.tables.setColumnWidth', rest)
+        elif action == 'merge_cells':
+            return execute('doc.tables.mergeCells', rest)
+        elif action == 'unmerge_cells':
+            return execute('doc.tables.unmergeCells', rest)
+        elif action == 'set_cell':
+            return execute('doc.tables.setCellProperties', rest)
+        elif action == 'set_cell_text':
+            return execute('doc.tables.setCellText', rest)
+        elif action == 'set_shading':
+            return execute('doc.tables.setShading', rest)
+        elif action == 'set_style_options':
+            return execute('doc.tables.applyStyle', rest)
+        elif action == 'set_borders':
+            return execute('doc.tables.setBorders', rest)
+        elif action == 'set_options':
+            return execute('doc.tables.setTableOptions', rest)
+        else:
+            raise SuperDocError(f'Unknown action for superdoc_table: {action}', code='TOOL_DISPATCH_NOT_FOUND', details={'toolName': 'superdoc_table', 'action': action})
     else:
         raise SuperDocError(f'Unknown intent tool: {tool_name}', code='TOOL_DISPATCH_NOT_FOUND', details={'toolName': tool_name})

package/tools/prompt-templates/system-prompt-core.md

@@ -8,6 +8,7 @@
 | superdoc_create | Create paragraphs, headings, or tables | Yes |
 | superdoc_format | Apply inline and paragraph formatting, set named styles | Yes |
 | superdoc_list | Create and manipulate bullet/numbered lists | Yes |
+| superdoc_table | Create / modify tables: structure, cell text, styling | Yes |
 | superdoc_comment | Create, update, delete, and list comment threads | Yes |
 | superdoc_track_changes | List, accept, or reject tracked changes | Yes |
 | superdoc_mutations | Execute multi-step atomic edits in a single batch | Yes |
@@ -306,6 +307,57 @@ Selectors resolve at compile time (before execution). This means format.apply st
 
 Never create two steps targeting overlapping text in the same block. Combine them into a single text.rewrite instead.
 
+### Tables: cross-tool workflows
+
+Tool-local rules (which action to pick, locator shapes, color formats) live in the `superdoc_table` description itself. The rules below cover workflows that **cross tools** — that's the part the model gets wrong without explicit guidance.
+
+**1. After `set_cell_text`, format the new cell to match its siblings.**
+`set_cell_text` writes plain text with no formatting. To match the rest of the table:
+
+```
+// Read a sibling cell's text style first (or any body paragraph if the table is fresh):
+superdoc_get_content({action: "blocks", includeText: true})
+
+// Apply matching inline style to the new cell's paragraph:
+superdoc_format({action: "inline", ref: "<new-cell-paragraph-ref>",
+  inline: {fontFamily, fontSize, color, bold: false}})
+```
+
+If sibling cells show a bold-prefix pattern like `"Label: value"`, replicate it on the new cell using `superdoc_search` + `superdoc_format` (or one `superdoc_mutations` batch with `format.apply` steps using `where:{by:"select", ...}`).
+
+**2. "Style the whole table" crosses `superdoc_table` and `superdoc_format`.**
+Borders / shading / cnf flags / spacing live on `superdoc_table`. **Cell-text alignment and font color/weight live on `superdoc_format`** (they're paragraph- and run-level). A complete table-styling pass calls both:
+
+```
+// Table-level (superdoc_table):
+set_borders applyTo:"all" with explicit color
+set_shading on the header cells with the accent color
+set_style_options { headerRow: true }
+
+// Cell-text level (superdoc_format, per cell paragraph):
+set_alignment on header (center) and body (left or right)
+inline { color, bold } on header cells
+
+// Batch many cell-level format calls via superdoc_mutations format.apply.
+```
+
+Discover the document's palette by reading `superdoc_get_content({action: "blocks"})` and reusing colors from existing tables/headings. When none are obvious, default to `1F3864` (corporate blue) or `444444` (dark grey) for accents and `F2F2F2` / `E7E6E6` for banding. Never use `auto` when a concrete color is implied.
+
+**3. After a structural change to a styled table, re-apply the existing styling.**
+Triggers: `insert_row`, `insert_column`, `delete_row`, `delete_column`, `merge_cells`, `unmerge_cells` — but NOT `set_cell_text` or `set_cell` (those don't disturb borders/shading). Read the current borders/shading/cnf flags via `superdoc_get_content({action: "blocks"})` before the change, then re-run the same `set_borders` / `set_shading` / `set_style_options` calls with the SAME values after. Goal is consistency, not redesign. Skip on a freshly created table — a new table starts un-styled.
+
+**4. Convert a list to a table.**
+Three steps:
+1. `superdoc_create({action: "table", rows: N, columns: M, at: ...})`
+2. Populate cells with `superdoc_table({action: "set_cell_text", ...})` — one call per cell.
+3. **Delete the source list** with one `superdoc_list` call:
+
+```
+superdoc_list({action: "delete", target: {kind: "block", nodeType: "listItem", nodeId: "<any-item-id>"}})
+```
+
+Wrong paths (all leave bullets/empty paragraphs behind): `text.delete`, `superdoc_edit` action `delete` on text refs, `lists.detach`, `lists.convertToText`. Only `superdoc_list` action `delete` removes the whole list.
+
 ### Add a comment on specific text
 
 ```
@@ -362,3 +414,5 @@ When formatting newly created content, use the right source:
 - **Only pass `dryRun` when the action's schema explicitly lists it.** Do not assume every action accepts it. Prefer a real call over a preview for destructive actions unless dryRun is documented for that action.
 - **If blocks still report `underline: true` after you explicitly removed it, treat it as a style inheritance artifact.** Do not retry formatting to fix it.
 - **On "Unknown field" errors, drop the unrecognized field and retry.** Use the narrowest working call shape rather than guessing alternative field names.
+- **Table styling crosses two tools.** Borders / shading / cnf flags / spacing are on `superdoc_table`; cell-text alignment and font color/weight are on `superdoc_format` (paragraph- and run-level). A "style the whole table" pass calls both. See the Tables: cross-tool workflows section for the full recipe.
+- **To delete a list, use `superdoc_list` action `delete`.** Pass any list-item nodeId. Never use `text.delete`, `superdoc_edit` action `delete`, `lists.detach`, or `lists.convertToText` for "remove the list" — they leave empty list-item paragraphs behind.

package/tools/system-prompt-mcp.md

@@ -57,6 +57,7 @@ One format.apply step per block. Combine `inline`, `alignment`, and `scope: "blo
 | superdoc_create | Create paragraphs, headings, or tables | Yes |
 | superdoc_format | Apply inline and paragraph formatting, set named styles | Yes |
 | superdoc_list | Create and manipulate bullet/numbered lists | Yes |
+| superdoc_table | Create / modify tables: structure, cell text, styling | Yes |
 | superdoc_comment | Create, update, delete, and list comment threads | Yes |
 | superdoc_track_changes | List, accept, or reject tracked changes | Yes |
 | superdoc_mutations | Execute multi-step atomic edits in a single batch | Yes |
@@ -355,6 +356,57 @@ Selectors resolve at compile time (before execution). This means format.apply st
 
 Never create two steps targeting overlapping text in the same block. Combine them into a single text.rewrite instead.
 
+### Tables: cross-tool workflows
+
+Tool-local rules (which action to pick, locator shapes, color formats) live in the `superdoc_table` description itself. The rules below cover workflows that **cross tools** — that's the part the model gets wrong without explicit guidance.
+
+**1. After `set_cell_text`, format the new cell to match its siblings.**
+`set_cell_text` writes plain text with no formatting. To match the rest of the table:
+
+```
+// Read a sibling cell's text style first (or any body paragraph if the table is fresh):
+superdoc_get_content({action: "blocks", includeText: true})
+
+// Apply matching inline style to the new cell's paragraph:
+superdoc_format({action: "inline", ref: "<new-cell-paragraph-ref>",
+  inline: {fontFamily, fontSize, color, bold: false}})
+```
+
+If sibling cells show a bold-prefix pattern like `"Label: value"`, replicate it on the new cell using `superdoc_search` + `superdoc_format` (or one `superdoc_mutations` batch with `format.apply` steps using `where:{by:"select", ...}`).
+
+**2. "Style the whole table" crosses `superdoc_table` and `superdoc_format`.**
+Borders / shading / cnf flags / spacing live on `superdoc_table`. **Cell-text alignment and font color/weight live on `superdoc_format`** (they're paragraph- and run-level). A complete table-styling pass calls both:
+
+```
+// Table-level (superdoc_table):
+set_borders applyTo:"all" with explicit color
+set_shading on the header cells with the accent color
+set_style_options { headerRow: true }
+
+// Cell-text level (superdoc_format, per cell paragraph):
+set_alignment on header (center) and body (left or right)
+inline { color, bold } on header cells
+
+// Batch many cell-level format calls via superdoc_mutations format.apply.
+```
+
+Discover the document's palette by reading `superdoc_get_content({action: "blocks"})` and reusing colors from existing tables/headings. When none are obvious, default to `1F3864` (corporate blue) or `444444` (dark grey) for accents and `F2F2F2` / `E7E6E6` for banding. Never use `auto` when a concrete color is implied.
+
+**3. After a structural change to a styled table, re-apply the existing styling.**
+Triggers: `insert_row`, `insert_column`, `delete_row`, `delete_column`, `merge_cells`, `unmerge_cells` — but NOT `set_cell_text` or `set_cell` (those don't disturb borders/shading). Read the current borders/shading/cnf flags via `superdoc_get_content({action: "blocks"})` before the change, then re-run the same `set_borders` / `set_shading` / `set_style_options` calls with the SAME values after. Goal is consistency, not redesign. Skip on a freshly created table — a new table starts un-styled.
+
+**4. Convert a list to a table.**
+Three steps:
+1. `superdoc_create({action: "table", rows: N, columns: M, at: ...})`
+2. Populate cells with `superdoc_table({action: "set_cell_text", ...})` — one call per cell.
+3. **Delete the source list** with one `superdoc_list` call:
+
+```
+superdoc_list({action: "delete", target: {kind: "block", nodeType: "listItem", nodeId: "<any-item-id>"}})
+```
+
+Wrong paths (all leave bullets/empty paragraphs behind): `text.delete`, `superdoc_edit` action `delete` on text refs, `lists.detach`, `lists.convertToText`. Only `superdoc_list` action `delete` removes the whole list.
+
 ### Add a comment on specific text
 
 ```
@@ -411,3 +463,5 @@ When formatting newly created content, use the right source:
 - **Only pass `dryRun` when the action's schema explicitly lists it.** Do not assume every action accepts it. Prefer a real call over a preview for destructive actions unless dryRun is documented for that action.
 - **If blocks still report `underline: true` after you explicitly removed it, treat it as a style inheritance artifact.** Do not retry formatting to fix it.
 - **On "Unknown field" errors, drop the unrecognized field and retry.** Use the narrowest working call shape rather than guessing alternative field names.
+- **Table styling crosses two tools.** Borders / shading / cnf flags / spacing are on `superdoc_table`; cell-text alignment and font color/weight are on `superdoc_format` (paragraph- and run-level). A "style the whole table" pass calls both. See the Tables: cross-tool workflows section for the full recipe.
+- **To delete a list, use `superdoc_list` action `delete`.** Pass any list-item nodeId. Never use `text.delete`, `superdoc_edit` action `delete`, `lists.detach`, or `lists.convertToText` for "remove the list" — they leave empty list-item paragraphs behind.

package/tools/system-prompt.md

@@ -12,6 +12,7 @@ You are a document editing assistant. You have a DOCX document open and a set of
 | superdoc_create | Create paragraphs, headings, or tables | Yes |
 | superdoc_format | Apply inline and paragraph formatting, set named styles | Yes |
 | superdoc_list | Create and manipulate bullet/numbered lists | Yes |
+| superdoc_table | Create / modify tables: structure, cell text, styling | Yes |
 | superdoc_comment | Create, update, delete, and list comment threads | Yes |
 | superdoc_track_changes | List, accept, or reject tracked changes | Yes |
 | superdoc_mutations | Execute multi-step atomic edits in a single batch | Yes |
@@ -310,6 +311,57 @@ Selectors resolve at compile time (before execution). This means format.apply st
 
 Never create two steps targeting overlapping text in the same block. Combine them into a single text.rewrite instead.
 
+### Tables: cross-tool workflows
+
+Tool-local rules (which action to pick, locator shapes, color formats) live in the `superdoc_table` description itself. The rules below cover workflows that **cross tools** — that's the part the model gets wrong without explicit guidance.
+
+**1. After `set_cell_text`, format the new cell to match its siblings.**
+`set_cell_text` writes plain text with no formatting. To match the rest of the table:
+
+```
+// Read a sibling cell's text style first (or any body paragraph if the table is fresh):
+superdoc_get_content({action: "blocks", includeText: true})
+
+// Apply matching inline style to the new cell's paragraph:
+superdoc_format({action: "inline", ref: "<new-cell-paragraph-ref>",
+  inline: {fontFamily, fontSize, color, bold: false}})
+```
+
+If sibling cells show a bold-prefix pattern like `"Label: value"`, replicate it on the new cell using `superdoc_search` + `superdoc_format` (or one `superdoc_mutations` batch with `format.apply` steps using `where:{by:"select", ...}`).
+
+**2. "Style the whole table" crosses `superdoc_table` and `superdoc_format`.**
+Borders / shading / cnf flags / spacing live on `superdoc_table`. **Cell-text alignment and font color/weight live on `superdoc_format`** (they're paragraph- and run-level). A complete table-styling pass calls both:
+
+```
+// Table-level (superdoc_table):
+set_borders applyTo:"all" with explicit color
+set_shading on the header cells with the accent color
+set_style_options { headerRow: true }
+
+// Cell-text level (superdoc_format, per cell paragraph):
+set_alignment on header (center) and body (left or right)
+inline { color, bold } on header cells
+
+// Batch many cell-level format calls via superdoc_mutations format.apply.
+```
+
+Discover the document's palette by reading `superdoc_get_content({action: "blocks"})` and reusing colors from existing tables/headings. When none are obvious, default to `1F3864` (corporate blue) or `444444` (dark grey) for accents and `F2F2F2` / `E7E6E6` for banding. Never use `auto` when a concrete color is implied.
+
+**3. After a structural change to a styled table, re-apply the existing styling.**
+Triggers: `insert_row`, `insert_column`, `delete_row`, `delete_column`, `merge_cells`, `unmerge_cells` — but NOT `set_cell_text` or `set_cell` (those don't disturb borders/shading). Read the current borders/shading/cnf flags via `superdoc_get_content({action: "blocks"})` before the change, then re-run the same `set_borders` / `set_shading` / `set_style_options` calls with the SAME values after. Goal is consistency, not redesign. Skip on a freshly created table — a new table starts un-styled.
+
+**4. Convert a list to a table.**
+Three steps:
+1. `superdoc_create({action: "table", rows: N, columns: M, at: ...})`
+2. Populate cells with `superdoc_table({action: "set_cell_text", ...})` — one call per cell.
+3. **Delete the source list** with one `superdoc_list` call:
+
+```
+superdoc_list({action: "delete", target: {kind: "block", nodeType: "listItem", nodeId: "<any-item-id>"}})
+```
+
+Wrong paths (all leave bullets/empty paragraphs behind): `text.delete`, `superdoc_edit` action `delete` on text refs, `lists.detach`, `lists.convertToText`. Only `superdoc_list` action `delete` removes the whole list.
+
 ### Add a comment on specific text
 
 ```
@@ -366,3 +418,5 @@ When formatting newly created content, use the right source:
 - **Only pass `dryRun` when the action's schema explicitly lists it.** Do not assume every action accepts it. Prefer a real call over a preview for destructive actions unless dryRun is documented for that action.
 - **If blocks still report `underline: true` after you explicitly removed it, treat it as a style inheritance artifact.** Do not retry formatting to fix it.
 - **On "Unknown field" errors, drop the unrecognized field and retry.** Use the narrowest working call shape rather than guessing alternative field names.
+- **Table styling crosses two tools.** Borders / shading / cnf flags / spacing are on `superdoc_table`; cell-text alignment and font color/weight are on `superdoc_format` (paragraph- and run-level). A "style the whole table" pass calls both. See the Tables: cross-tool workflows section for the full recipe.
+- **To delete a list, use `superdoc_list` action `delete`.** Pass any list-item nodeId. Never use `text.delete`, `superdoc_edit` action `delete`, `lists.detach`, or `lists.convertToText` for "remove the list" — they leave empty list-item paragraphs behind.

package/tools/tools-policy.json

@@ -1,6 +1,6 @@
 {
   "policyVersion": "v4",
-  "toolCount": 9,
+  "toolCount": 10,
   "tools": [
     {
       "toolName": "superdoc_get_content",
@@ -37,7 +37,11 @@
     {
       "toolName": "superdoc_mutations",
       "mutates": true
+    },
+    {
+      "toolName": "superdoc_table",
+      "mutates": true
     }
   ],
-  "contractHash": "cdb0b02e84f6eb7f4db962c177d082e0f89ec48517abc775736a3d17e4da9ba8"
+  "contractHash": "7f5b6fd6bc20fd3fa19d21530275655158eefbbd59b111ff0107fe76e1dd9a1b"
 }