@beyondwork/docx-react-component 1.0.0

package/test/fixtures/docx/F09-comments-single-paragraph.md

@@ -0,0 +1,33 @@
+# F09 Comments anchored single paragraph
+
+## Source shape
+
+- file: `F09-comments-single-paragraph.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: single-paragraph comment anchors, comment references, and comment-part survival
+
+## Import expectation
+
+- single-paragraph comment anchors should import into runtime-owned comment state with stable anchor mapping
+- the relevant comment metadata should remain attached to the owning paragraph instead of falling back to opaque preserved markup
+
+## Edit expectation
+
+- supported text edits within the anchored paragraph remain allowed
+- anchor remapping must preserve the comment attachment or surface an explicit warning instead of silently detaching it
+
+## Export expectation
+
+- export should preserve comment-part content plus the main-story references needed to reattach the comment
+- reimported output should still resolve the same comment thread to the edited paragraph span
+
+## Validation expectation
+
+- package integrity should remain valid after supported edits
+- the source and supported edited exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- the comment should remain attached to the intended paragraph span after export

package/test/fixtures/docx/F10-threaded-comments-resolve.md

@@ -0,0 +1,33 @@
+# F10 Threaded comments and resolve
+
+## Source shape
+
+- file: `F10-threaded-comments-resolve.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: comment threads, reply ordering, and resolution metadata on single-paragraph anchors
+
+## Import expectation
+
+- threaded comments should import into runtime-owned thread state with reply order preserved
+- resolution metadata should remain available to the review UI rather than being flattened away
+
+## Edit expectation
+
+- supported thread navigation and text edits within the anchored paragraph remain allowed
+- thread metadata and resolution state must remain stable through supported edits
+
+## Export expectation
+
+- export should preserve comment thread structure, reply metadata, and resolution state
+- reimported output should still reconstruct the same thread shape on the same supported anchor range
+
+## Validation expectation
+
+- package integrity should remain valid after supported edits
+- the source and supported edited exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- threaded comments and resolution state should remain intact after export

package/test/fixtures/docx/F11-redlines-basic.md

@@ -0,0 +1,33 @@
+# F11 Redlines basic
+
+## Source shape
+
+- file: `F11-redlines-basic.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: run-level `w:ins` and `w:del` markup with accept or reject proof on the supported slice
+
+## Import expectation
+
+- run-level insertions and deletions should import into runtime-owned revision state
+- revision author and date metadata should remain attached to the imported revision records
+
+## Edit expectation
+
+- accept and reject actions on supported run-level insertions and deletions remain supported
+- supported text edits must not silently flatten imported revision markup outside the owned slice
+
+## Export expectation
+
+- export should preserve revision markup when no review action is applied
+- accepted and rejected exports should normalize the owned run-level changes without introducing unsupported revision rewrites
+
+## Validation expectation
+
+- package integrity should remain valid after supported review actions
+- the source and supported edited exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- tracked insertions and deletions should remain intelligible in Word after roundtrip or supported review actions

package/test/fixtures/docx/F12-redlines-paragraph-joins-splits.md

@@ -0,0 +1,33 @@
+# F12 Redlines paragraph joins and splits
+
+## Source shape
+
+- file: `F12-redlines-paragraph-joins-splits.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: paragraph-mark revision behavior and runtime-owned accept or reject proof for paragraph joins and splits
+
+## Import expectation
+
+- paragraph-mark revisions should import into runtime-owned revision state with boundary metadata preserved
+- the runtime should distinguish supported paragraph-mark cases from structural revision cases it does not own
+
+## Edit expectation
+
+- supported accept and reject actions on the owned paragraph-mark revision slice remain allowed
+- ambiguous or unsupported structural rewrites must warn or block rather than silently rewrite paragraph boundaries
+
+## Export expectation
+
+- export should preserve paragraph-mark revision markup when no supported review action is applied
+- accepted and rejected exports should normalize the owned paragraph boundary changes without losing surrounding content
+
+## Validation expectation
+
+- package integrity should remain valid after supported review actions
+- the source and supported edited exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- paragraph join and split behavior should remain intelligible in Word after supported review actions

package/test/fixtures/docx/F13-comments-on-deleted-text.md

@@ -0,0 +1,33 @@
+# F13 Comments on deleted text
+
+## Source shape
+
+- file: `F13-comments-on-deleted-text.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: comment anchors that interact with deleted text plus runtime diagnostics around comment and revision overlap
+
+## Import expectation
+
+- supported comment and revision metadata should import into runtime-owned state where the anchor remains representable
+- overlap cases that fall outside the owned slice must stay explicit through diagnostics rather than being silently flattened
+
+## Edit expectation
+
+- supported edits should preserve comment and deletion mapping where the runtime owns that interaction
+- unsupported overlap cases must warn or block rather than detach anchors or rewrite deleted content silently
+
+## Export expectation
+
+- export should preserve the comment and deletion interaction for owned cases
+- roundtripped output should keep explicit overlap behavior instead of collapsing the review structure
+
+## Validation expectation
+
+- package integrity should remain valid after supported edits
+- the source and supported edited exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- comment and deleted-text behavior should remain explicit and reviewable after export

package/test/fixtures/docx/F14-revisions-in-tables-and-lists.md

@@ -0,0 +1,33 @@
+# F14 Revisions in tables and lists
+
+## Source shape
+
+- file: `F14-revisions-in-tables-and-lists.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: structural revision markup inside table and list structures that the current runtime does not own semantically
+
+## Import expectation
+
+- surrounding supported story content may import into canonical editable state
+- structural revision markup inside tables or list structure should remain preserve-only and explicitly disclosed
+
+## Edit expectation
+
+- supported edits may occur outside the preserved structural revision regions
+- preserved structural revision regions must remain atomic and non-editable on the current live path
+
+## Export expectation
+
+- export should preserve the original structural revision markup without semantic rewriting
+- table and list revision structure should survive roundtrip intact as preserve-only content
+
+## Validation expectation
+
+- package integrity should remain valid after supported surrounding edits
+- the source and preserve-only roundtrip exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- structural review markup in tables and lists should remain intact after export

package/test/fixtures/docx/F15-sections-headers-footers.md

@@ -0,0 +1,33 @@
+# F15 Sections and headers footers
+
+## Source shape
+
+- file: `F15-sections-headers-footers.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: `w:sectPr`, header parts, footer parts, and the relationship wiring that keeps them attached to the document
+
+## Import expectation
+
+- body story content may import into canonical editable text where supported
+- section properties plus header and footer content should remain preserve-only package-backed surfaces
+
+## Edit expectation
+
+- supported edits may occur in the main story outside preserved section boundaries
+- section, header, and footer surfaces must remain atomic and non-editable on the current live path
+
+## Export expectation
+
+- export should preserve header and footer parts, relationship targets, and section-property wiring
+- reattached package state should survive roundtrip without semantic rewriting of the preserved surfaces
+
+## Validation expectation
+
+- package integrity should remain valid after supported surrounding edits
+- the source and preserve-only roundtrip exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- section behavior and header or footer content should remain intact after export

package/test/fixtures/docx/F16-footnotes-endnotes.md

@@ -0,0 +1,33 @@
+# F16 Footnotes and endnotes
+
+## Source shape
+
+- file: `F16-footnotes-endnotes.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: note references in the main story plus note-part survival in `footnotes.xml` and `endnotes.xml`
+
+## Import expectation
+
+- body story content may import into canonical editable text where supported
+- note references and note parts should remain preserve-only package-backed content on the current live path
+
+## Edit expectation
+
+- supported edits may occur around preserved note references without rewriting note structure
+- note references and note content must remain atomic and non-editable until first-class note support exists
+
+## Export expectation
+
+- export should preserve note references, note parts, and the relationships that keep them attached to the package
+- reattached note content should survive roundtrip without semantic rewriting
+
+## Validation expectation
+
+- package integrity should remain valid after supported surrounding edits
+- the source and preserve-only roundtrip exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- footnote and endnote references should continue to resolve correctly after export

package/test/fixtures/docx/F17-fields-and-toc.md

@@ -0,0 +1,33 @@
+# F17 Fields and TOC
+
+## Source shape
+
+- file: `F17-fields-and-toc.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: field-code markup, TOC-related field structures, and preserve-only field survival
+
+## Import expectation
+
+- body story content may import into canonical editable text where supported
+- field-code markup and TOC structures should remain preserve-only package-backed content on the current live path
+
+## Edit expectation
+
+- supported edits may occur around preserved field regions without rewriting field semantics
+- field-code and TOC surfaces must remain atomic and non-editable until first-class support exists
+
+## Export expectation
+
+- export should preserve `w:fldChar`, `w:instrText`, `w:fldSimple`, and related field markup required by the source package
+- reattached field structures should survive roundtrip without semantic rewriting
+
+## Validation expectation
+
+- package integrity should remain valid after supported surrounding edits
+- the source and preserve-only roundtrip exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- field behavior and TOC structure should remain intact after export

package/test/fixtures/docx/F18-content-controls-template.md

@@ -0,0 +1,33 @@
+# F18 Content controls template
+
+## Source shape
+
+- file: `F18-content-controls-template.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: `w:sdt` content-control markup, locking semantics, and preserve-only survival
+
+## Import expectation
+
+- surrounding supported story content may import into canonical editable text
+- content-control markup should remain preserve-only package-backed content rather than becoming editable canonical structure
+
+## Edit expectation
+
+- supported edits may occur outside the preserved content-control region
+- the `w:sdt` surface must remain atomic and non-editable on the current live path
+
+## Export expectation
+
+- export should preserve the original content-control subtree and any related package state
+- reattached `w:sdt` markup should survive roundtrip without semantic rewriting
+
+## Validation expectation
+
+- package integrity should remain valid after supported surrounding edits
+- the source and preserve-only roundtrip exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- the content-control surface should remain intact and locked after export

package/test/fixtures/docx/F19-custom-xml-doc-assembly.md

@@ -0,0 +1,35 @@
+# F19 Custom XML doc assembly
+
+## Source shape
+
+- file: `F19-custom-xml-doc-assembly.docx`
+- source package findings: `0`
+- source SDK findings: `1`
+- observed focus: `w:customXml` wrapper markup plus `/customXml/item1.xml` and `/customXml/itemProps1.xml` package parts
+- inherited SDK note: the source document carries an undeclared `w:uri` attribute on `w:customXml` in `word/document.xml`
+
+## Import expectation
+
+- surrounding supported story content may import into canonical editable text
+- the custom XML wrapper and related custom XML parts should remain preserve-only package-backed content on the current live path
+
+## Edit expectation
+
+- supported edits may occur outside the preserved custom XML region
+- the `w:customXml` wrapper and related payload must remain atomic and non-editable until first-class support exists
+
+## Export expectation
+
+- export should preserve the custom XML wrapper plus the related `/customXml` package parts and relationships
+- roundtrip should remain delta-neutral with respect to the inherited source SDK finding unless the source fixture itself is corrected explicitly
+
+## Validation expectation
+
+- package integrity should remain valid after supported surrounding edits
+- preserve-only roundtrip exports should not introduce additional package or SDK findings beyond the inherited source count of `1`
+- this fixture is preserve-only proof, not a zero-finding supported-roundtrip claim
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- the custom XML wrapper and related package payload should remain intact after export

package/test/fixtures/docx/F20-unknown-ooxml-and-alternatecontent.md

@@ -0,0 +1,33 @@
+# F20 Unknown OOXML and AlternateContent
+
+## Source shape
+
+- file: `F20-unknown-ooxml-and-alternatecontent.docx`
+- source package findings: `0`
+- source SDK findings: `0`
+- observed focus: `mc:Ignorable`, `mc:AlternateContent`, unknown namespaced OOXML, preserved package parts, and `altChunk` survival
+
+## Import expectation
+
+- surrounding supported story content may import into canonical editable text
+- unknown OOXML, markup-compatibility constructs, and related package parts should remain preserve-only package-backed content
+
+## Edit expectation
+
+- supported edits may occur outside the preserved unknown-content regions
+- unknown OOXML and alternate-content surfaces must remain atomic and non-editable on the current live path
+
+## Export expectation
+
+- export should preserve `mc:Ignorable`, `mc:AlternateContent`, unknown namespace declarations, `altChunk` references, and related preserved package parts
+- roundtrip should keep the source package’s markup-compatibility envelope intact without semantic rewriting
+
+## Validation expectation
+
+- package integrity should remain valid after supported surrounding edits
+- the source and preserve-only roundtrip exports should remain at `0` package findings and `0` SDK findings
+
+## Word expectation
+
+- Word should reopen the edited package without repair prompts
+- unknown OOXML and alternate-content fallback behavior should remain intact after export

package/test/fixtures/docx/F21-malformed-broken-docx.md

@@ -0,0 +1,33 @@
+# F21 Malformed broken docx
+
+## Source shape
+
+- file: `F21-malformed-broken-docx.docx`
+- source package findings: `0`
+- source SDK or open findings: `1`
+- observed focus: unresolved package relationship state where `word/_rels/document.xml.rels` targets `/word/header1.xml` but that part is missing from the package
+
+## Import expectation
+
+- the importer must fail closed into diagnostics or read-only mode rather than claiming a trustworthy editable session
+- the malformed relationship graph must remain explicit as an unsupported-fatal package condition
+
+## Edit expectation
+
+- editing that depends on a trusted canonical session must remain blocked
+- the runtime must not silently repair, drop, or rewrite the broken package state
+
+## Export expectation
+
+- export must be rejected for this fixture
+- a successful export would be a regression unless the contract is revised deliberately
+
+## Validation expectation
+
+- ZIP-level package inspection may still open, but Open XML SDK validation should fail when the package is opened as a `WordprocessingDocument`
+- this fixture proves fail-closed malformed-package handling, not successful roundtrip
+
+## Word expectation
+
+- there is no supported editing or export compatibility claim for this fixture
+- the only acceptance bar is explicit diagnostics and blocked export instead of silent destructive repair

package/test/fixtures/docx/README.md

@@ -0,0 +1,74 @@
+# DOCX Fixtures
+
+This directory is the durable regression corpus for OOXML import, export, preservation, and compatibility proof.
+
+Each fixture must have:
+
+- a stable fixture ID `F01` through `F21`
+- a human-readable fixture name
+- a declared feature-class focus: `supported-roundtrip`, `preserve-only`, or `unsupported-fatal`
+- companion notes describing import expectations, edit constraints, export expectations, and Word reopen assertions
+- proof-bearing wave ownership so later waves cannot claim compatibility without the named fixture
+
+The fixture manifest at `fixtures.manifest.json` now links every frozen fixture entry to its companion note through a stable `noteFileName`.
+
+## Fixture registry
+
+| Fixture | Name | Primary focus | Feature class focus | Proof-bearing wave(s) |
+| --- | --- | --- | --- | --- |
+| F01 | Basic contract skeleton | paragraphs, runs, whitespace, paragraph split/merge | `supported-roundtrip` | Wave 3, Wave 10 |
+| F02 | Headings and styles contract | heading styles, paragraph style references, outline-level preservation | `supported-roundtrip` | Wave 3, Wave 10 |
+| F03 | Legal outline numbering | nested numbered and bulleted lists | `supported-roundtrip` | Wave 5, Wave 10 |
+| F04 | Restart numbering schedules | list restart semantics and overrides | `supported-roundtrip` | Wave 5, Wave 10 |
+| F05 | Table-heavy agreement | preserve-only table structure, `tblGrid`, and package-backed cell-content survival | `preserve-only` | Wave 10, Wave 12 if promoted |
+| F06 | Merged-cells signature table | preserve-only horizontal and vertical merged-cell survival | `preserve-only` | Wave 10, Wave 12 if promoted |
+| F07 | Inline images exhibit | inline media parts and relationship integrity | `supported-roundtrip` | Wave 5, Wave 10 |
+| F08 | Hyperlinks exhibit list | external hyperlink rels in body and tables | `supported-roundtrip` | Wave 3, Wave 10 |
+| F09 | Comments anchored single paragraph | supported comment anchors through edits | `supported-roundtrip` | Wave 5, Wave 10 |
+| F10 | Threaded comments and resolve | threaded replies and resolution metadata | `supported-roundtrip` | Wave 5, Wave 10 |
+| F11 | Redlines basic | tracked insertions and deletions with accept/reject | `supported-roundtrip` | Wave 6, Wave 10 |
+| F12 | Redlines paragraph joins/splits | paragraph-mark revision behavior | `supported-roundtrip` | Wave 6, Wave 10 |
+| F13 | Comments on deleted text | comment and deletion interaction diagnostics | `supported-roundtrip` | Wave 6, Wave 10 |
+| F14 | Revisions in tables and lists | structural revision preservation | `preserve-only` | Wave 6, Wave 10 |
+| F15 | Sections + headers/footers | out-of-band section and header/footer survival | `preserve-only` | Wave 7, Wave 10 |
+| F16 | Footnotes and endnotes | note-part survival and mapping | `preserve-only` | Wave 7, Wave 10 |
+| F17 | Fields and TOC | field-code and TOC preservation | `preserve-only` | Wave 7, Wave 10 |
+| F18 | Content controls template | SDT locking and survival | `preserve-only` | Wave 7, Wave 10 |
+| F19 | Custom XML doc assembly | `w:customXml` wrappers and custom XML parts | `preserve-only` | Wave 7, Wave 10 |
+| F20 | Unknown OOXML and AlternateContent | opaque OOXML preservation and markup compatibility | `preserve-only` | Wave 7, Wave 10 |
+| F21 | Malformed/broken docx | safe failure on malformed XML or broken relationships | `unsupported-fatal` | Wave 7, Wave 10 |
+
+## Required companion notes
+
+Every fixture note should state:
+
+- source shape: the relevant parts, relationships, and OOXML features inside the package
+- import expectation: whether the fixture becomes canonical content, preserved package state, opaque placeholders, or blocked diagnostics
+- edit expectation: what is editable, what is locked, and what destructive actions must warn or block
+- export expectation: whether the serializer regenerates or reattaches the affected surfaces
+- validation expectation: package checks, compatibility-report expectations, and Open XML SDK validation applicability
+- Word expectation: whether Word reopen must match supported editing semantics or preserve-only survival semantics
+
+## Proof policy
+
+- Do not claim compatibility for a feature without naming the exact fixture IDs that prove it.
+- Do not replace a preserve-only fixture with a browser-render assertion.
+- `F05` and `F06` currently prove package-backed preserve-only table survival, not runtime-backed table editing.
+- `F19` currently carries one inherited source SDK finding in its custom XML wrapper markup; preserve-only proof for that fixture is judged against a delta-neutral source baseline until the source artifact itself is corrected.
+- If a fixture expands scope, update this registry and the OOXML contract doc in the same change.
+- If a malformed fixture such as F21 starts exporting successfully, treat that as a bug until the contract is explicitly revised.
+
+Wave 1 note:
+
+- The fixture registry is contract-frozen as the validation backbone for later implementation waves, even though the fixture files themselves still land incrementally.
+
+## Representative Scenario Artifacts
+
+Representative real-world documents live under [test/fixtures/scenarios/docx/README.md](/home/coder/docx-react-component/test/fixtures/scenarios/docx/README.md).
+
+- They supplement the frozen F01-F21 corpus and do not replace release-gate fixtures.
+- They exercise realistic document combinations that cut across multiple feature classes.
+- They use source-vs-export validator delta tracking because real customer-style documents may already carry source SDK findings.
+- Word reopen and preserve-only survival remain the decisive acceptance gates for those scenario artifacts.
+
+Password-to-open Office containers are currently handled upstream of the component. Deferred reference material remains under [test/fixtures/encrypted-docx/README.md](/home/coder/docx-react-component/test/fixtures/encrypted-docx/README.md), but it is not part of the active F01-F21 release-gate corpus.

package/test/fixtures/docx/certification-manifest.json

@@ -0,0 +1,104 @@
+{
+  "manifestVersion": "docx-certification/1",
+  "wave": 10,
+  "bundleRoot": ".tmp/wave-10-certification",
+  "automationRoute": "/api/fixtures/[fixtureId]/run",
+  "releaseGateFixtures": [
+    "F01",
+    "F02",
+    "F03",
+    "F04",
+    "F05",
+    "F06",
+    "F07",
+    "F08",
+    "F09",
+    "F10",
+    "F11",
+    "F12",
+    "F13",
+    "F14",
+    "F15",
+    "F16",
+    "F17",
+    "F18",
+    "F19",
+    "F20",
+    "F21"
+  ],
+  "supportedRoundtripFixtures": [
+    "F01",
+    "F02",
+    "F03",
+    "F04",
+    "F07",
+    "F08",
+    "F09",
+    "F10",
+    "F11",
+    "F12",
+    "F13"
+  ],
+  "preserveOnlyFixtures": [
+    "F05",
+    "F06",
+    "F14",
+    "F15",
+    "F16",
+    "F17",
+    "F18",
+    "F19",
+    "F20"
+  ],
+  "unsupportedFatalFixtures": [
+    "F21"
+  ],
+  "representativeScenarios": [
+    "S01",
+    "S02"
+  ],
+  "manualReviewFixtures": [
+    "F01",
+    "F03",
+    "F05",
+    "F09",
+    "F11",
+    "F12",
+    "F15",
+    "F20"
+  ],
+  "manualReviewScenarios": [
+    "S01"
+  ],
+  "expectedBlockedScenarios": [
+    "S02"
+  ],
+  "requiredArtifacts": [
+    "regression-report.json",
+    "fixture-coverage.json",
+    "certification-freshness.json",
+    "accessibility-signoff.md",
+    "design-conformance.md",
+    "performance-budget.json",
+    "large-doc-smoke.json",
+    "word-desktop-certification.md",
+    "word-web-certification.md"
+  ],
+  "freshnessPolicy": {
+    "requireRepoCommit": true,
+    "requireCleanWorkingTree": true,
+    "requiredProofWave": 10,
+    "requiredCommitPrefixLength": 12,
+    "rejectLegacyRoots": [
+      ".tmp/wave-8-railway-pilot",
+      ".tmp/wave-9-pilot"
+    ]
+  },
+  "notes": [
+    "F01 through F21 stay frozen as the v1 release-gate corpus.",
+    "Supported-roundtrip fixtures must all run through /api/fixtures/[fixtureId]/run for Wave 10 machine certification.",
+    "S01 and S02 are required Wave 10 certification scenarios but remain non-release-gate artifacts.",
+    "S02 is an explicit fail-closed scenario in the bounded v1 contract: review actions that would require remapping preserve-only comment anchors must block export instead of rewriting anchors unsafely.",
+    "Fresh Wave 10 evidence must be generated on the current commit; older Wave 8 or Wave 9 bundles cannot satisfy this manifest."
+  ]
+}