dsh-tool-docx

LIMITATIONS

Known limitations

- **Legacy `.doc` (OLE) is unsupported** — binary OLE needs LibreOffice or Word COM conversion; the tools fail with `DOCX_LEGACY_DOC` and a hint to convert to `.docx` first. - **Round-trip regenerates the document** — styles, page setup, headers/footers, and section breaks are not preserved; an edit rebuilds the body with default styles, keeping only title/author/created and embedded images. Layout fidelity is not a goal of the round trip. - **Merged table cells approximate** — `gridSpan`/`vMerge` degrade to plain pipe-table cells with a warning; footnotes, endnotes, text boxes, and page breaks are dropped (warnings included). - **The sandbox controller duplicates `dsh-tool-fs`** — extracting a shared `FsSandboxController` is deferred; the two copies must be kept in sync until then. - **Markdown input subset** — blockquotes, horizontal rules, and nested fences are not represented; they degrade to paragraphs with a warning (fenced code becomes code-styled paragraphs). - **Structured error codes under the tsx source run** — when the harness launches from source (`node --import tsx/esm`, the dev launcher), the healed `$DSH_HOME/profiles/node_modules` junction resolves as a second module instance of the peer Service Definition packages, so plugin errors fail the host's `instanceof HarnessError` check and `error.info.code` is omitted from tool results. The model-facing message — including the `[sandbox: …]` markers and escalation hints — is unaffected, and built-bin launches (plain Node) share one instance and preserve the codes.