What the PowerPoint tests were designed to answer
PowerPoint can store older comments and newer Microsoft 365 threaded comments in different package parts. A reliable exporter must identify the schema before interpreting replies or resolution state.
The acceptance checks therefore cover real saved fixtures, relationship traversal, thread identity, slide order, workbook fields, and conservative handling of unknown structures.
Can legacy and modern comment relationships be recognized without treating an unknown relationship as ordinary comment data?
Can a modern reply keep its parent comment ID and inherit only a verified parent thread state?
Can rows retain presentation order, slide number, and slide title for handoff?
Can every result include the comment register and the coverage notes that explain its limits?
Tested claims and current status
The released claims come from PowerPoint for Windows round-trip fixtures, OOXML parser tests, workbook checks, and browser download verification.
| Area | Status | What the evidence shows |
|---|---|---|
| Microsoft 365 modern root comment | Validated | A real modern fixture exports the root comment with slide, author, text, date, and resolved status. |
| Modern nested reply | Validated | The same fixture exports one reply with the correct parent ID and verified parent thread status. |
| Legacy PowerPoint comment | Validated | A PowerPoint Save As round-trip fixture exports the legacy comment in slide order with Open status. |
| Unknown modern status detail | Explicit unknown | Unavailable status information produces a coverage warning rather than an invented resolved or active value. |
| Unknown comment relationship | Export blocked | A detected unsupported relationship returns COMMENT_COVERAGE_BLOCKED instead of an incomplete workbook. |
What the Excel workbook is expected to contain
The workbook keeps extracted review rows and the explanation of their coverage in one file.
IDs, parent IDs, thread type, status, slide number, slide title, author, date, comment text, response, disposition, and row coverage.
Detected comment schema, validated boundaries, safety limits, and any warning that affects interpretation.
A frozen header, filters, stable ordering, and safe cell values make the workbook usable as a review register.
The exporter handles one macro-free PPTX and stops above its file, package, XML-part, or 5,000-row limits.
What this evidence does not prove
It does not claim coverage for every future PowerPoint schema, cloud-only collaboration state, deleted comments, comments that are no longer stored in the PPTX, or visual slide annotations outside the detected comment models.
Legacy comments do not expose modern replies or resolved state. They are exported as Open with a coverage explanation rather than mapped to unsupported thread semantics.