What the DOCX research was designed to answer
A DOCX is a ZIP package containing XML, relationships, and media. Text conversion alone does not prove that image order, file bytes, and relative paths remain usable after the document moves.
The acceptance checks therefore treat the Markdown file, image assets, and coverage report as one result rather than three unrelated downloads.
Do headings, paragraphs, emphasis, links, lists, and simple tables remain readable in Markdown?
Do supported images appear between the same surrounding text markers as the source document?
Can the unzipped package move to another folder without breaking assets/ references?
Are unsupported Word objects reported before the user relies on the package?
Tested claims and current status
The released claims come from OOXML fixtures, integration tests, browser downloads, and a production sample. They describe the current parser rather than every possible Word document.
| Area | Status | What the evidence shows |
|---|---|---|
| Core document structure | Validated | Headings, paragraphs, emphasis, links, lists, and simple tables passed integration checks. |
| Raster image bytes | Validated | PNG assets in the ZIP match real embedded media and are not placeholders or data URLs. |
| Image source order | Validated | Two images remain between the same three surrounding text markers used by the fixture. |
| Relative asset paths | Validated | Markdown points to stable assets/image-001.png style paths inside the ZIP. |
| Unsupported Word objects | Warning | Equations, VML, charts, SmartArt, legacy objects, and complex text boxes enter the coverage report. |
| Invalid or unsupported packages | Blocked | Old .doc, macro-enabled, encrypted, damaged, or empty packages do not receive a false success result. |
What the downloaded ZIP is expected to contain
The result is intentionally a package. Separating the Markdown from the assets directory would break the portability claim that the fixtures verify.
The document structure and image references are written into a readable .md file.
Supported embedded raster images are copied as real files with stable names.
conversion-report.json records counts and warnings for objects that need review.
Repeated conversions of the same input keep the same logical asset naming and order.
What this evidence does not prove
It does not promise visual parity for equations, complex tables, charts, SmartArt, drawing layers, VML, legacy objects, or complex text boxes.
It also does not prove that comments or tracked changes will survive as Markdown review semantics. The Word Review Exporter remains the dedicated workflow for that data.