matevip b4ebab65c7 feat(tool): docx image embedding + multi-file render ... Two follow-up improvements on top of renderDocxFromFile so the docx pipeline can handle real long-form deliverables instead of just prose-only memos. Image embedding (P1). MarkdownDocxRenderer now recognizes single-line  markdown and embeds the referenced file via POI's XWPFRun.addPicture(): - PNG / JPG / GIF / BMP read straight from disk - SVG rasterized via Apache Batik (PNGTranscoder, target width 1400px) before embedding — OOXML stores raster images, so any vector source needs conversion. Batik runs in-JVM, no rsvg-convert / cairo on host. - Pictures are pinned to roughly the printable page width (≈ 5.77 in for A4 minus default 1800-twip margins) and given a 4:3 height fallback. Mixing images inline with other paragraph text is not supported by design — the markdown subset assumes one image per block paragraph. Inline images would require splitting paragraphs across runs with explicit positioning, well beyond what this renderer covers. - Failure modes (missing file, unsupported format, Batik blowing up) emit an italicised "[image: alt — reason]" placeholder so the rest of the document still renders; the agent can read its own log to see why the picture didn't make it. - Adds two transitive deps via pom: batik-transcoder + batik-codec at 1.18, ~10 MB combined. Worth it given the alternative is shelling out to system tooling. Multi-file render (P2-lite). New tool renderDocxFromFiles(List<String> filePaths, filename, pageSize) reads several markdown files in order and renders one combined docx. Lets the agent split a 30-page proposal into cover.md / ch1.md / ch2.md / appendix.md and produce a single deliverable in one tool call. Each path goes through WorkspacePathGuard.validatePath; any empty or unreadable file aborts with a typed error so the agent fixes its file list before retrying. Files are joined with a blank line — no separator markup is injected, headings carry over cleanly. I deliberately did NOT build the heavier mutable-docx state ("appendDocxChapter / finalizeDocx") flavor of P2: the multi-file form covers the same workflow with no per-conversation state to clean up, and the agent can iterate by rewriting the chapter file and re-running the tool. Stateful append can come later if a streaming use case actually shows up. renderDocx and renderDocxFromFile @Tool descriptions updated to point the agent at renderDocxFromFile for >5 KB markdown and to advertise the new image-embedding capability.		2026-04-27 08:42:03 +08:00
..
main	feat(tool): docx image embedding + multi-file render	2026-04-27 08:42:03 +08:00
test/java/vip/mate	feat(memory): Dream v2 Phase 1 — lifecycle mediator foundation	2026-04-20 17:31:21 +08:00