dsh-office-kit 0.3.2 → 0.4.0

package/CAPABILITY.md

@@ -93,32 +93,34 @@ never guessed.
 
 ## Renderer dependency
 
-- `docx`, `pptx` and `xlsx` rendering needs an office suite: Microsoft Office
-  (Word/PowerPoint/Excel over COM), WPS Office (`KWps`/`KWpp`/`Ket` over COM) or
-  LibreOffice (headless conversion). `render` names the one it used in its
-  `renderer` field (`microsoft-office`, `kingsoft-wps`, `libreoffice`). With none
-  installed it exits non-zero: `no document renderer found: install LibreOffice,
-  Microsoft Office, or WPS Office`.
-- `xlsx recalc` needs a real calculation engine: Excel or WPS Spreadsheets over
-  COM. It reports `renderer` and the count of cached values it filled in.
+- `docx`, `pptx` and `xlsx` rendering goes through the LibreOffice kit that
+  DeepSeek Harness ships (`@deepseek-ai/libreoffice-kit`: native engine on Windows
+  and macOS, WASM on Linux). No system Office, WPS or LibreOffice installation is
+  probed or used. `render` names it in `renderer` (`libreoffice-kit`) and the
+  engine in `engine` (`native` / `wasm`). When the kit cannot be found the
+  command exits non-zero: `the LibreOffice renderer is not available: the DSH
+  LibreOffice kit was not found`.
+- Locating the kit: walk up from the plugin directory to
+  `node_modules/@deepseek-ai/libreoffice-kit/lib/cli.js`; override with
+  `DSH_LIBREOFFICE_KIT_CLI` (and `DSH_NODE` for the node binary).
+- `xlsx recalc` uses the same kit (`recalculate`), on every platform, and reports
+  `renderer`, `engine` and the count of cached values it filled in.
+- Render reports `missing_fonts`, `glyph_fallback` and a `warnings` list; a
+  missing font is reported instead of silently producing boxes. `--pdf` also
+  exports a PDF through the kit.
 - `pdf render` needs no external renderer; PyMuPDF rasterises it directly.
 - The PPTX pack's `container_tools/preview_render.py` is a geometry-only draft:
   it redraws shapes, text boxes and images from the package with PyMuPDF and
   labels itself `draft-preview` / `geometry-only`. It proves placement, not
   typography (bullet glyphs are not drawn), and `render_slides.py` prefers the
   real renderer whenever one exists.
-- **This machine renders through WPS Office.** `office_status` reports
-  `kingsoft_wps: {writer, presentation, spreadsheet}` from `wps.exe`/`wpp.exe`/
-  `et.exe` under `%LOCALAPPDATA%\Kingsoft\WPS Office\<version>\office6`;
-  `docx`/`pptx`/`xlsx render` return `"renderer": "kingsoft-wps"`, and `xlsx
-  recalc` fills cached values through `Ket.Application`.
 - `assets/skills/shared/scripts/ensure_raster_image.py` turns SVG, a chosen PDF
   page, or a raster file into a PNG (PyMuPDF for vectors, Pillow for rasters), so
   artwork can be embedded and then looked at. It never overwrites its input.
 - `assets/skills/shared/check_runtime.py` imports every package from
   `python/requirements.txt` and runs `<cli> status`; it exits non-zero on a
-  missing package or broken CLI, and 4 with `--require-renderer` when no renderer
-  is installed (a missing renderer is otherwise only a warning).
+  missing package or broken CLI, and 4 with `--require-renderer` when the kit is
+  unavailable (otherwise only a warning).
 
 ## Verification evidence
 
@@ -127,10 +129,10 @@ never guessed.
 | Packages on the runtime venv (3.13.12, `~/.dsh/office/runtime/venv`) | 10/10 import — python-docx 1.2.0, openpyxl 3.1.5, python-pptx 1.0.2, pypdf 6.21.1, reportlab 4.5.1, pdfplumber 0.11.9, PyMuPDF 1.28.2, Pillow 11.3.0, latex2mathml 3.81.1, mathml2omml 0.0.2 |
 | `check_runtime.py` (venv / `--require-renderer` / bare `py -3.14`) | exit 0 + renderer warning / exit 4 / exit 1 listing the 8 missing packages and the pip remedy |
 | DOCX create / read / `replace_text.py` / `append_blocks.py` | ok — counts returned, styles preserved, `replacements: 1`, `appended: 1`, equation intact |
-| DOCX / PPTX render | ok through WPS — `renderer: kingsoft-wps`, DOCX 2 pages, PPTX 3 pages, PNGs opened and checked |
+| DOCX / PPTX render | ok through the kit — `renderer: libreoffice-kit`, `engine: native`, PNGs opened and checked |
 | PPTX create / read / `add_slides.py` | ok — 3 slides, texts and charts read back |
 | XLSX create / read / `set_cells.py` | ok — formula read back uncached, one cell written |
-| XLSX recalc | ok through WPS — `renderer: kingsoft-wps`, 34 cached values filled, `A3 = 7` after `CalculateFull` |
+| XLSX recalc | ok through the kit — `renderer: libreoffice-kit`, `engine: native`, formula cells gained cached values |
 | `ensure_raster_image.py` | ok — 120×60 SVG at `--dpi 300` → 500×250, `--page` on a 2-page PDF, `--width 400` upscale, JSON errors on missing/unwritable input |
 | `excel-live-control/container_tools/live_excel.py` | ok against WPS — attach refusal with remediation when nothing runs; `write_range` A1:B3 (6 cells), `set_formula` C1, `read_range` values `[[10,20,30],[30,40,null],[50,60,null]]`, `save` 9,268 bytes, `--diagnose` lists the workbook/sheet, `close --quit-app` refuses a dirty book, `--discard` leaves zero `et.exe` |
 | PDF create / read / render / `metadata.py` / `page_ops.py` / `redact_region.py` | ok — CJK font applied, metadata written, merge→remove→rotate, region redaction removed 170 chars and 11 drawings, `page-1.png` produced |
@@ -138,7 +140,7 @@ never guessed.
 | Forbidden-vocabulary grep over the delivered docs | empty |
 
 Not claimed (no evidence here): installer or self-heal timings, live GUI
-interaction (`/` menu, chip, sidebar preview, annotation overlay), and macOS/Linux
+interaction (`/` menu, chip, sidebar preview, annotation overlay), and macOS
 renderer support.
 
 ## Explicitly out of scope
@@ -150,5 +152,6 @@ renderer support.
   so); OCR and scanned-PDF text extraction.
 - PPTX animations, speaker notes, slide masters; XLSX pivots, macros, data
   validation, conditional formatting — no spec keys or verbs in the helper.
-- Formula evaluation without Microsoft Excel or WPS Spreadsheets; macOS/Linux
-  installation and renderer behaviour (only Windows was exercised).
+- Formula evaluation without the DSH LibreOffice kit; macOS/Linux installation
+  was exercised in CI (Linux runs the WASM engine), but only Windows was checked
+  by hand.

package/README.md

@@ -37,7 +37,7 @@ dsh plugin add dsh-office-kit
 - 📊 **电子表格**：`/spreadsheets` 创建、读取和编辑 XLSX，支持公式、样式、图表、冻结窗格与重算。
 - 🖍️ **侧边栏标注**：在 PDF、DOC/DOCX、PPTX、XLSX 预览中吸附段落或框选区域，批量提交修改要求。
 - 🔗 **会话引用**：通过 Chip 调用文档技能；注释链接可悬停查看文件名与要求，PDF 标注附选区截图。
-- 🖼️ **渲染校验**：DOCX/PPTX/XLSX 经 Microsoft Office、WPS Office 或 LibreOffice 导出 PDF 再栅格化，PDF 直接用 PyMuPDF；SVG/PDF 素材可用 `ensure_raster_image.py` 转成 PNG 后嵌入。
+- 🖼️ **渲染校验**：DOCX/PPTX/XLSX 经 DeepSeek Harness 自带的 LibreOffice Kit（Windows/macOS 原生引擎，Linux 走 WASM）栅格化，PDF 直接用 PyMuPDF；缺失字体会在报告里点名，不再静默产出豆腐块。SVG/PDF 素材可用 `ensure_raster_image.py` 转成 PNG 后嵌入。
 - 🧮 **活体表格**：`excel-live-control` 技能通过 COM 驱动已经打开的 Excel / WPS 表格（读区、写值、样式、图表、重算、保存）。
 
 ## 🚀 快速开始

package/assets/skills/office-documents/SKILL.md

@@ -45,7 +45,7 @@ Rendering is the only proof that a document looks right.
 The command writes a PDF plus one PNG per page and prints the paths. Open each PNG with `read_image` and check: heading hierarchy, table width and cell wrapping, page breaks, header/footer, clipped or overflowing text, missing glyphs (dashes, CJK, symbols), equation rendering, and caption placement.
 
 - Iterate until the pages look correct, then deliver. "It parses" is not verification.
-- If the runtime reports no renderer (none of Microsoft Word, WPS Writer, or LibreOffice), ask the user to install one, or fall back to `docx read` plus the audit scripts. Say plainly that layout was not visually verified — do not describe a page you did not see.
+- If the runtime reports no renderer (`renderers.can_render.docx: false` — the DSH LibreOffice kit is missing), ask the user to fix the install, or fall back to `docx read` plus the audit scripts. Say plainly that layout was not visually verified — do not describe a page you did not see.
 - After a script edits XML, re-render. A package can stay valid while the page it produces is broken.
 
 ## Choosing a route

package/assets/skills/office-documents/examples/end_to_end_smoke_test.md

@@ -71,7 +71,7 @@ Audits may exit 1 with findings — that is a report, not a failure of the envir
 "$PY" "$R/render_docx.py" "$W/with-toc.docx" --output_dir "$W/render" --dpi 150
 ```
 
-Then open each PNG with `read_image`. Without a renderer the command exits 3 with `no_renderer`; that is the expected result on a machine with neither LibreOffice nor Word, and the rest of the test still stands.
+Then open each PNG with `read_image`. Without the DSH LibreOffice kit the command exits 3 with `no_renderer`; that is a setup problem, not a document problem, and the rest of the test still stands.
 
 ## 6. Deliver
 

package/assets/skills/office-documents/render_docx.py

@@ -5,11 +5,11 @@ Rendering is the only honest check that a document looks right: XML can be valid
 and still overlap, clip or reflow badly.  This script keeps the plumbing in one
 place so tasks can say "render it, look at the images" and mean a single command.
 
-The render verb needs a real Word engine (Microsoft Word, WPS Writer, or
-LibreOffice).  When none is installed the script reports exactly that and exits 3,
-because a placeholder image would be worse than no image.
+The render verb needs the DSH LibreOffice kit.  When the kit cannot be found the
+script reports exactly that and exits 3, because a placeholder image would be
+worse than no image.
 
-Exit codes: 0 rendered, 1 render failed, 3 no renderer installed, 2 bad input.
+Exit codes: 0 rendered, 1 render failed, 3 no renderer available, 2 bad input.
 """
 
 from __future__ import annotations
@@ -62,6 +62,8 @@ def main(argv: list[str] | None = None) -> int:
     command = ["docx", "render", "--input", str(source), "--out-dir", str(out_dir)]
     if args.dpi:
         command += ["--dpi", str(args.dpi)]
+    if args.emit_pdf:
+        command += ["--pdf"]
     code, stdout, stderr = kit.run_office_cli(command)
     payload = kit.cli_json(stdout) or kit.cli_json(stderr) or {}
     pages = payload.get("pages") or []
@@ -72,7 +74,7 @@ def main(argv: list[str] | None = None) -> int:
             lines = [line for line in (stderr or stdout or "").splitlines() if line.strip() not in ("", "{", "}")]
             detail = lines[-1].strip() if lines else "render failed"
         if "renderer" in detail.lower() or "libreoffice" in detail.lower():
-            kit.emit({"ok": False, "reason": "no_renderer", "detail": detail, "remedy": "Install Microsoft Office, WPS Office, or LibreOffice, then re-run this command."})
+            kit.emit({"ok": False, "reason": "no_renderer", "detail": detail, "remedy": "Install this plugin inside the DeepSeek Harness tree so @deepseek-ai/libreoffice-kit is available, or set DSH_LIBREOFFICE_KIT_CLI, then re-run this command."})
             return 3
         kit.emit({"ok": False, "reason": "render_failed", "detail": detail})
         return 1
@@ -86,6 +88,9 @@ def main(argv: list[str] | None = None) -> int:
         "pages": pages,
         "page_count": len(pages),
         "renderer": payload.get("renderer"),
+        "missing_fonts": payload.get("missing_fonts") or [],
+        "glyph_fallback": bool(payload.get("glyph_fallback")),
+        "warnings": payload.get("warnings") or [],
     }
     if args.emit_pdf and payload.get("pdf"):
         result["pdf"] = payload["pdf"]

package/assets/skills/office-documents/scripts/render_and_diff.py

@@ -82,7 +82,7 @@ def main(argv: list[str] | None = None) -> int:
     if code_a != 0 or code_b != 0 or not pages_a or not pages_b:
         detail = detail_a or detail_b or "render failed"
         reason = "no_renderer" if ("renderer" in detail.lower() or "libreoffice" in detail.lower()) else "render_failed"
-        kit.emit({"ok": False, "reason": reason, "detail": detail, "remedy": "Install Microsoft Office, WPS Office, or LibreOffice, then re-run."})
+        kit.emit({"ok": False, "reason": reason, "detail": detail, "remedy": "Install this plugin inside the DeepSeek Harness tree so @deepseek-ai/libreoffice-kit is available, or set DSH_LIBREOFFICE_KIT_CLI, then re-run."})
         return 3 if reason == "no_renderer" else 1
 
     pairs = list(zip(pages_a, pages_b))

package/assets/skills/office-documents/tasks/verify_render.md

@@ -8,7 +8,7 @@
 "<python>" "<cli>" docx render --input "<file.docx>" --out-dir "<render-dir>"
 ```
 
-Writes a PDF and one PNG per page, and prints their paths plus the renderer it used (Word via COM, or LibreOffice). Use the same command through `render_docx.py` when you want the JSON report and page list:
+Writes one PNG per page and prints their paths plus the renderer it used (`libreoffice-kit`); add `--pdf` to also keep a PDF. Use the same command through `render_docx.py` when you want the JSON report and page list:
 
 ```bash
 "<python>" "<skill>/render_docx.py" "<file.docx>" --output_dir "<render-dir>" --dpi 150
@@ -27,12 +27,12 @@ Open every PNG with `read_image` and check, in this order:
 
 ## When no renderer exists
 
-The runtime reports `renderers.libreoffice: null` and no Office installation. `render` then exits non-zero with a JSON error naming the missing renderer, and `render_docx.py` exits 3 with `reason: no_renderer`.
+The runtime reports `renderers.can_render.docx: false` because the DSH LibreOffice kit was not found. `render` then exits non-zero with a JSON error naming the missing renderer, and `render_docx.py` exits 3 with `reason: no_renderer`.
 
 In that state:
 
 - Verify structure with `docx read`, `docx_kit.py parts|text|xml` and the audit scripts.
-- Tell the user plainly that layout was not visually verified, and offer to install Microsoft Office, WPS Office, or LibreOffice instead of describing a page you did not see.
+- Tell the user plainly that layout was not visually verified, and that the fix is installing the plugin inside the harness tree (or setting `DSH_LIBREOFFICE_KIT_CLI`), not installing Word/LibreOffice.
 - Do not claim a file "looks good" from XML evidence alone.
 
 ## After any script edit
@@ -46,5 +46,5 @@ Re-render. Package-valid is not page-valid: a caption inserted before the paragr
 ## Pitfalls
 
 - Different renderers paginate differently. Compare like with like, and do not promise Word-perfect pagination from a LibreOffice render.
-- A render fails silently into a blank page when a font is missing; a blank page is a finding, not a rendering bug.
+- A render fails silently into a blank page when a font is missing; a blank page is a finding, not a rendering bug. `missing_fonts` / `glyph_fallback` in the render JSON tells you substitution happened.
 - Render into a fresh directory; stale PNGs from an earlier run are the classic false pass.

package/assets/skills/office-documents/troubleshooting/libreoffice_headless.md

@@ -6,31 +6,28 @@
 "<python>" "<cli>" status
 ```
 
-Look at `renderers.libreoffice` and `microsoft_office`. Both null means `docx render` will fail — not with a corrupt file, but with `no document renderer found`. That is a setup problem, not a document problem.
+Look at `renderers.kit` and `renderers.can_render`. `can_render.docx: false` means `docx render` will fail — not with a corrupt file, but with `the LibreOffice renderer is not available`. That is a setup problem, not a document problem.
 
-## LibreOffice
+## What renders
 
-Install LibreOffice (Windows: winget `TheDocumentFoundation.LibreOffice`), then check:
+Rendering goes through the LibreOffice kit that DeepSeek Harness ships (`@deepseek-ai/libreoffice-kit`). On macOS and Windows it uses the kit's native engine; on Linux it uses the WASM engine. A separately installed Microsoft Office, WPS Office, or system LibreOffice is **not** used and does not make rendering work on its own.
 
-```bash
-soffice --headless --version
-```
-
-If the binary is not on `PATH`, the runtime cannot find it; either add its `program` directory to `PATH` or install into the default location the runtime probes. On Windows, `soffice.com` is the console wrapper — use that one, not `soffice.exe`, when a script needs to wait for exit.
-
-## Microsoft Office
+The plugin finds the kit by walking up from its own directory through `node_modules/@deepseek-ai/libreoffice-kit/lib/cli.js`. So:
 
-When Word is installed, the CLI can drive it through COM and does not need LibreOffice. Office must be activated and able to launch without a first-run dialog; a pending activation or a modal "sign in" blocks the render forever.
+- Installed inside the harness tree → the kit is found automatically.
+- Installed anywhere else → install the plugin where the harness can see its dependencies, or set `DSH_LIBREOFFICE_KIT_CLI` to the kit's `lib/cli.js`.
+- `DSH_NODE` overrides the node binary if `node` is not on `PATH`.
 
 ## Common failures
 
 | Message | Cause | Fix |
 |---|---|---|
-| `no document renderer found` | Neither installed / not on PATH | Install one, re-check `status` |
-| Render hangs | A dialog is waiting in the headless process | Kill the leftover process, add the `--headless --norestore` flags the CLI uses |
-| Blank pages | Missing font | Install the font or substitute it |
+| `the LibreOffice renderer is not available` | Kit not found from the plugin directory | Put the plugin inside the harness tree, or set `DSH_LIBREOFFICE_KIT_CLI` |
+| `cannot start the LibreOffice kit` / `EEXIST` | Interrupted install, or a stale staging directory | Re-run the plugin postinstall; delete leftover `.kit-render-*` directories |
+| `Unsupported LibreOfficeKit host` | Unsupported platform/arch (the kit ships Windows x64/arm64, macOS x64/arm64, Linux via WASM) | Render on a supported host |
+| `warning: N font(s) used by this file are not installed` | Font substitution — the render succeeded but that text may reflow or show boxes | Install the font or substitute it deliberately, then re-render |
+| Blank pages | Missing font | See the font warning above |
 | Text shifted | Font substitution | Compare with a render from the same renderer the user will use |
-| `soffice already running` | A user profile lock from a crashed run | Remove the stale lock file under the LibreOffice user profile, or wait for the old process to exit |
 
 ## Working without a renderer
 
@@ -38,7 +35,7 @@ Structure, text and metadata are all verifiable headlessly (`docx read`, the aud
 
 1. Do the structural verification.
 2. Tell the user that page layout was not visually checked, and why.
-3. Offer the install, or ask them to open the file and say what looks wrong.
+3. Ask them to fix the kit install, or open the file and say what looks wrong.
 
 Never describe a page you did not render.
 

package/assets/skills/office-pdf/SKILL.md

@@ -42,7 +42,7 @@ Decide the route before you type a command. Every route ends in the same render
 | --- | --- | --- |
 | `{"ok": false, ...}` and non-zero exit | Invalid argument, missing file, or a refused overwrite | Read the `error` field, fix what it names, re-run. Never strip a step to make it pass. |
 | `encrypted` in the error | The file needs a password | Ask the user for a decrypted copy; do not guess passwords or write one into a command. |
-| `no document renderer found: install LibreOffice, Microsoft Office, or WPS Office` | Media conversion for docx/pptx/xlsx is unavailable | PDF rendering still works (PyMuPDF); for a PDF this is harmless. For other formats report that appearance could not be checked. |
+| `the LibreOffice renderer is not available` | Media conversion for docx/pptx/xlsx is unavailable because the DSH LibreOffice kit was not found | PDF rendering still works (PyMuPDF); for a PDF this is harmless. For other formats report that appearance could not be checked. |
 | `leftover_chars_in_rect` greater than 0 | The redaction rectangle missed text | Enlarge `--pad` or reconvert the region; re-render before delivering. |
 | `not_applied` is not empty | A form value did not persist after save | Treat as a failure: check the field name, its allowed states, and whether the widget has an appearance stream. |
 | `chars: 0` on a page that shows text | Scanned page, no text layer | Say so; follow `references/limits.md` for the OCR situation. Do not return an empty extraction as success. |

package/assets/skills/office-presentations/SKILL.md

@@ -62,10 +62,10 @@ Render, look at every page, then deliver — in that order, with nothing skipped
 "<python>" "<skill>/container_tools/render_slides.py" --input "<file.pptx>" --out-dir "<render-dir>"
 ```
 
-`render_slides.py` uses the CLI's `pptx render` — which drives Microsoft
-PowerPoint, WPS Presentation, or LibreOffice, whichever is installed — and falls
-back to a draft preview when none is, so this one command is always the right
-entry point. The JSON names the engine it used in `engine`.
+`render_slides.py` uses the CLI's `pptx render` — which renders through the DSH
+LibreOffice kit — and falls back to a draft preview when the kit is missing, so
+this one command is always the right entry point. The JSON names the engine it
+used in `engine` (`libreoffice-kit` means a faithful render).
 
 Then open each PNG with `read_image` (or build one sheet with
 `"<skill>/template_following_scripts/make_contact_sheet.py"`). Check: titles
@@ -149,9 +149,10 @@ Guidance: [authoring workflow](references/authoring-workflow.md) ·
 
 ## Genuine gaps
 
-- No Microsoft Office, WPS Office, or LibreOffice installed → no true render;
-  use `--engine draft` and say the check was geometric. Installing any of them
-  fixes it.
+- The DSH LibreOffice kit missing (`renderers.can_render.pptx: false`) → no true
+  render; use `--engine draft` and say the check was geometric. Installing the
+  plugin inside the harness tree (or setting `DSH_LIBREOFFICE_KIT_CLI`) fixes it;
+  a standalone Office/LibreOffice install does not.
 - Fonts the user's machine lacks are substituted by any renderer; the pack
   cannot install fonts.
 - Google Slides import fidelity is out of our control; see

package/assets/skills/office-presentations/container_tools/render_slides.py

@@ -1,9 +1,9 @@
 """Render a deck to PNGs, one per slide, using whatever engine is available.
 
-Purpose: the verification loop needs pixels. Ask the plugin CLI first: it drives
-Microsoft Office, WPS Office, or LibreOffice, whichever is installed. When none
-is, fall back to the draft geometry renderer in `preview_render.py` and say so
-loudly in the JSON — a draft preview proves placement, not typography.
+Purpose: the verification loop needs pixels. Ask the plugin CLI first: it renders
+through the DSH LibreOffice kit. When that is unavailable, fall back to the draft
+geometry renderer in `preview_render.py` and say so loudly in the JSON — a draft
+preview proves placement, not typography.
 
 Inputs may be a .pptx or a .pdf. Output is `<out-dir>/slide-NN.png` for every
 page, plus `<out-dir>/render.json`.
@@ -105,7 +105,7 @@ def render(input_path: str | Path, out_dir: str | Path, dpi: int = 110, engine:
             notes.append(f"office render failed: {exc}")
 
     if engine == "office":
-        return {"ok": False, "engine": "office", "notes": notes, "error": {"code": "no_engine", "message": "no Microsoft Office, WPS Office, or LibreOffice renderer is available"}}
+        return {"ok": False, "engine": "office", "notes": notes, "error": {"code": "no_engine", "message": "the DSH LibreOffice renderer is not available (see office_status)"}}
 
     from preview_render import render_preview
 

package/assets/skills/office-presentations/tasks/inspect-and-verify.md

@@ -84,12 +84,11 @@ title.
 
 ## 6. When nothing can render
 
-With no Microsoft Office, WPS Office, or LibreOffice installed
-(`office_status` → `renderers.kingsoft_wps` / `microsoft_office` / `libreoffice`),
-`render_slides.py` falls back to `--engine draft`, a PyMuPDF geometry preview. It
-shows placement, overflow and overlap — not typography or theme chrome. Say so
-when reporting: "verified as a geometry preview" is honest, "looks great" from an
-approximate render is not.
+With the DSH LibreOffice kit missing (`office_status` → `renderers.kit` /
+`renderers.can_render`), `render_slides.py` falls back to `--engine draft`, a
+PyMuPDF geometry preview. It shows placement, overflow and overlap — not
+typography or theme chrome. Say so when reporting: "verified as a geometry
+preview" is honest, "looks great" from an approximate render is not.
 
 If even the preview cannot run, the delivery is unverified: report the failing
 command, the file's slide count from `pptx read`, and the gate results, and tell

package/assets/skills/office-spreadsheets/SKILL.md

@@ -4,7 +4,7 @@ description: Create, inspect, edit, recalculate, and verify Excel workbooks (.xl
 
 # Spreadsheets (.xlsx)
 
-A workbook is cells: each one holds a value, a format, and possibly a formula *string*. openpyxl writes all three and evaluates none of them, so a formula you just wrote has no cached result and `xlsx read` shows `=SUM(B2:B9)` where the user expects `1,950,400`. The calculation happens in an engine — Microsoft Excel or WPS Spreadsheets via `xlsx recalc`, or whatever app the user opens the file in. Everything below follows from that: write values and formulas, then verify structure by reading back, then verify numbers by recalculating, then verify appearance by rendering.
+A workbook is cells: each one holds a value, a format, and possibly a formula *string*. openpyxl writes all three and evaluates none of them, so a formula you just wrote has no cached result and `xlsx read` shows `=SUM(B2:B9)` where the user expects `1,950,400`. The calculation happens in an engine — the DSH LibreOffice via `xlsx recalc` (cross-platform), or whatever app the user opens the file in. Everything below follows from that: write values and formulas, then verify structure by reading back, then verify numbers by recalculating, then verify appearance by rendering.
 
 | User job | What is really happening | Fast path |
 | --- | --- | --- |
@@ -52,8 +52,8 @@ For xlsx the payload is `{ target, fileName, text: "", requirement, region, imag
 Three checks, in this order, after every mutation:
 
 1. **Structure and values.** `"<python>" "<cli>" xlsx read --input "<file>"` proves the cells you wrote are where you wrote them; `container_tools/inspect_workbook.py` proves charts, tables, conditional formats, names, and merges survived.
-2. **Numbers.** If any formula changed or was added, run `"<python>" "<cli>" xlsx recalc --input "<file>" --out "<file>"` and then `container_tools/recalc_gate.py --input "<file>"`. On a host without Microsoft Excel or WPS Spreadsheets the recalc fails and `recalc_gate.py` reports `unverified` — say that plainly instead of presenting an empty cache as a result.
-3. **Appearance.** `"<python>" "<cli>" xlsx render --input "<file>" --out-dir "<render-dir>"`, then `read_image` each PNG. Check titles and labels, `###` columns, clipped numbers, charts cut off by the print area, plots with no categories, legends naming `Series 1`, conditional formatting that never fired, and blank pages. The render goes through Excel, WPS Spreadsheets, or LibreOffice; with none installed it fails explicitly: report the file as structurally verified but visually unchecked, and offer to rebuild from a spec. WPS in particular needs its print area and page setup right before exporting, so a layout complaint may be the export settings rather than the sheet.
+2. **Numbers.** If any formula changed or was added, run `"<python>" "<cli>" xlsx recalc --input "<file>" --out "<file>"` and then `container_tools/recalc_gate.py --input "<file>"`. The kit recalculates on every platform; only when the kit itself is missing does the recalc fail, and `recalc_gate.py` then reports `unverified` — say that plainly instead of presenting an empty cache as a result.
+3. **Appearance.** `"<python>" "<cli>" xlsx render --input "<file>" --out-dir "<render-dir>"`, then `read_image` each PNG. Check titles and labels, `###` columns, clipped numbers, charts cut off by the print area, plots with no categories, legends naming `Series 1`, conditional formatting that never fired, and blank pages. The render goes through the DSH LibreOffice kit; when it is missing the command fails explicitly: report the file as structurally verified but visually unchecked, and offer to rebuild from a spec.
 
 Two or three render/fix passes are normal. If a defect survives three, say what still looks wrong.
 

package/assets/skills/office-spreadsheets/container_tools/recalc_gate.py

@@ -1,15 +1,15 @@
 #!/usr/bin/env python3
 """Gate a workbook on formulas that actually resolve.
 
-Recomputes the file through the helper CLI (`xlsx recalc`, which drives Microsoft
-Excel or WPS Spreadsheets over COM), then classifies every formula cell: a real
+Recomputes the file through the helper CLI (`xlsx recalc`, which drives the DSH
+LibreOffice kit on every platform), then classifies every formula cell: a real
 value, a spreadsheet error, or no cached value at all. Also flags formulas that
 point at sheets the workbook does not contain, and formulas whose text already
 carries a `#REF!` literal.
 
-Without a calculation engine the recomputation cannot happen; `--no-recalc` then
-inspects the cached values a previous producer left in the file instead of failing
-outright. A file whose formulas carry no cached value at all cannot be certified.
+Without the kit the recomputation cannot happen; `--no-recalc` then inspects the
+cached values a previous producer left in the file instead of failing outright. A
+file whose formulas carry no cached value at all cannot be certified.
 
 Exit codes:
   0  verified: every formula resolved to a value

package/assets/skills/office-spreadsheets/tasks/recalc-and-check.md

@@ -10,9 +10,9 @@ every formula cell got a value and none of them is an error.
 "<python>" "<skill>/container_tools/recalc_gate.py" --input "<book-recalculated.xlsx>"
 ```
 
-- `recalc` needs a calculation engine on this host — Microsoft Excel or WPS
-  Spreadsheets, driven over COM. Without one the verb fails with a plain message
-  and changes nothing.
+- `recalc` needs the DSH LibreOffice kit (the same renderer used for images);
+  it runs on Windows, macOS and Linux. Without the kit the verb fails with a
+  plain message and changes nothing.
 - `recalc_gate.py` runs `recalc` for you when given `--cli`: it takes
   `--input`, writes `<stem>-recalculated.xlsx` unless `--out` is given, then
   scans every formula cell.

package/assets/skills/shared/annotation-recipes.md

@@ -126,9 +126,8 @@ Choose the edit that the helper actually supports:
   rebuild as a surgical edit.
 
 Verify with `<cli> pdf render --input "report-edited.pdf" --out-dir "render"` and
-`read_image render/page-1.png`. `pdf render` uses PyMuPDF and works without
-LibreOffice or Office, so a PDF annotation is never blocked by a missing
-renderer.
+`read_image render/page-1.png`. `pdf render` uses PyMuPDF and works without the
+LibreOffice kit, so a PDF annotation is never blocked by a missing renderer.
 
 ## pptx — select the shapes that overlap the region
 
@@ -234,10 +233,10 @@ Forbidden, because both produce plausible-looking edits in the wrong place:
   its own zoom and scroll;
 - naming a sheet the screenshot does not show or `xlsx read` cannot match.
 
-Visual confirmation needs `xlsx render`, which requires LibreOffice or Office;
-without one, say the change is verified structurally but not visually. Formula
-results stay uncalculated unless `xlsx recalc` runs on Windows with Microsoft
-Excel; do not present openpyxl's empty cache as a computed value.
+Visual confirmation needs `xlsx render`, which requires the DSH LibreOffice kit;
+without it, say the change is verified structurally but not visually. Formula
+results stay uncalculated until `xlsx recalc` runs (the kit recalculates on any
+platform); do not present openpyxl's empty cache as a computed value.
 
 ## When to stop and ask
 

package/assets/skills/shared/check_runtime.py

@@ -33,8 +33,8 @@ for _stream in (sys.stdout, sys.stderr):
 
 DEFAULT_ROOT = Path(__file__).resolve().parents[3]
 RENDERER_HINT = (
-    "docx/pptx/xlsx rendering needs LibreOffice, Microsoft Office, or WPS Office; "
-    "pdf rendering works without any of them (PyMuPDF)"
+    "docx/pptx/xlsx rendering needs the DSH LibreOffice kit, which ships with DeepSeek Harness; "
+    "pdf rendering needs only PyMuPDF"
 )
 
 
@@ -122,18 +122,19 @@ def cli_status(python: Path, cli: Path, timeout: float) -> dict:
 def renderer_summary(report: dict) -> dict:
     """Reduce the CLI renderer block to a simple availability answer."""
     renderers = report.get("renderers") or {}
-    office = renderers.get("microsoft_office") or {}
-    wps = renderers.get("kingsoft_wps") or {}
+    kit = renderers.get("kit") or {}
+    can_render = renderers.get("can_render") or {}
     available = {
-        "libreoffice": renderers.get("libreoffice") or None,
-        "microsoft_office": {k: office.get(k) or None for k in ("word", "powerpoint", "excel")},
-        "kingsoft_wps": {k: wps.get(k) or None for k in ("writer", "presentation", "spreadsheet")},
+        "kit": {
+            "available": bool(kit.get("available")),
+            "backend": kit.get("backend") or None,
+            "version": kit.get("version") or None,
+            "error": kit.get("error") or None,
+            "remedy": kit.get("remedy") or None,
+        },
+        "can_render": {k: bool(can_render.get(k)) for k in ("docx", "pptx", "xlsx", "pdf")},
     }
-    available["any"] = (
-        bool(available["libreoffice"])
-        or any(available["microsoft_office"].values())
-        or any(available["kingsoft_wps"].values())
-    )
+    available["any"] = bool(available["can_render"]["docx"])
     return available
 
 
@@ -244,8 +245,12 @@ def emit(args: argparse.Namespace, report: dict) -> None:
         print(f"  [{mark}] {item['distribution']:<16} {detail}{modules}")
     if "renderers" in report:
         r = report["renderers"]
-        print(f"renderer     libreoffice={r['libreoffice'] or 'none'}; "
-              f"office={r['microsoft_office']}; wps={r['kingsoft_wps']}")
+        kit = r["kit"]
+        detail = f"backend={kit['backend'] or 'none'}"
+        if kit["error"]:
+            detail += f"; error={kit['error']}"
+        print(f"renderer     libreoffice-kit available={kit['available']} {detail}; "
+              f"can_render={r['can_render']}")
     for warning in report["warnings"]:
         print(f"warning      {warning}")
     if report.get("error"):

package/assets/skills/shared/common-workflow.md

@@ -15,7 +15,7 @@ appended to the end of the active `SKILL.md`. It is a fenced JSON block:
 ```
 
 - `python` and `cli` are verified absolute paths. Use them verbatim and quote
-  them in commands. Never call a bare `python`, `py`, `soffice` or `pdftoppm`.
+  them in commands. Never call a bare `python`, `py`, or `pdftoppm`.
 - `skill` is the directory of the format pack; its scripts live under
   `<skill>/scripts/`.
 - `shared` is this directory (workflow and annotation recipes).
@@ -125,10 +125,10 @@ a blank, clipped or miscoloured raster is invisible inside the host file.
 | --- | --- | --- |
 | No `## Office runtime` JSON; skill says *No working Python runtime is available* | The plugin cannot install or find a compatible interpreter | Do not run helper commands, do not write a document by hand. Give the user the remedy command from the skill body, ask them to run it, then call `office_status` again. |
 | `office_status` shows `cli.exists: false`, or `python`/`cli` file not found | The bundled helper or its install is incomplete | Report the missing path. Do not substitute another tool that produces a different file. |
-| `render` fails: `no document renderer found: install LibreOffice, Microsoft Office, or WPS Office` | Create/read/edit work, but docx/pptx/xlsx cannot be rasterised here | Do not claim you inspected it. Say the file was built and validated structurally (read verb), but this machine has no renderer so you could not check its appearance; the preview stays unavailable until Microsoft Office, WPS Office, or LibreOffice is installed. `pdf render` still works. If the user needs visual confidence now, offer to rebuild from a spec or to present the unverified file explicitly labelled as such. |
+| `render` fails: `the LibreOffice renderer is not available` | The kit that DSH ships with was not found; create/read/edit still work but docx/pptx/xlsx cannot be rasterised | Do not claim you inspected it. Say the file was built and validated structurally (read verb), but the renderer is unavailable on this host so you could not check its appearance. The kit ships with DeepSeek Harness — installing this plugin inside the harness tree (or setting `DSH_LIBREOFFICE_KIT_CLI`) fixes it; a standalone LibreOffice/Office/WPS install does not. `pdf render` still works. If the user needs visual confidence now, offer to rebuild from a spec or to present the unverified file explicitly labelled as such. |
 | Annotation region does not land on anything, or the payload says `unmapped: true` | The drawn region cannot be tied to an object in the file | Do not silently shift the region or guess a cell/shape. Say what you could identify (preview page, text, resolved cells) and which item you could not locate, then ask the user for the text or cell. |
 | `{"ok": false, "error": "..."}` and non-zero exit | The spec was rejected (unknown key, bad type, missing file) | Read the error text, fix the spec key it names, re-run the same command. Never strip a failing block to make the command pass — that silently deletes user content. |
-| `xlsx recalc` fails with *requires Microsoft Excel or WPS Spreadsheets* | openpyxl cannot evaluate formulas | Report formula cells as uncalculated; do not invent computed values. |
+| `xlsx recalc` fails because the LibreOffice kit is missing | openpyxl cannot evaluate formulas, and the kit is the only calculation engine this plugin uses | Report formula cells as uncalculated; do not invent computed values. Fix the renderer first (install the plugin inside the harness tree) and re-run. |
 | The helper has no verb for what the requirement needs | The common path is short; the capability is not limited to it | Take the pack script route, or write a short snippet against `python-docx` / `openpyxl` / `python-pptx` / `pypdf` / `PyMuPDF` / `reportlab`, run it with `<python>`, then `read` the file back and render. Never refuse a job because a verb is missing. |
 | `read` returns an empty structure for a file the user supplied | Unsupported or corrupt input | Say what failed and stop; do not overwrite the user's file with an empty one. |