@beyondwork/docx-react-component 1.0.0 → 1.0.2

package/docs/plans/waves/reviews/wave-35-cont-qa.md

@@ -1,145 +0,0 @@
-# Wave 35 cont-QA Review
-
-- Wave: 35
-- Agent: A0
-- Role: cont-QA
-- Reviewed: 2026-04-06
-- Verdict: PASS
-
----
-
-## Summary
-
-Wave 35 targets the `track-change-extensions` component and declares a single promotion: `baseline-proved`. The implementation is owned by A1. A8 performed integration synthesis. A9 confirmed shared-plan documentation closure.
-
-This review judges the landed evidence against the declared exit contract and component promotion target.
-
----
-
-## Exit Contract Verification — A1
-
-Declared exit contract:
-- completion: authoritative
-- durability: durable
-- proof: integration
-- doc-impact: none
-
-### Deliverables check
-
-All seven declared deliverables are confirmed present in the landed tree:
-
-| File | Status |
-|---|---|
-| `src/io/ooxml/parse-revisions.ts` | Present — `parseTblPropertyRevisions()` and `parseSectPrRevisions()` confirmed at lines 478, 525 |
-| `src/io/export/serialize-revisions.ts` | Present — `serializePropertyChangeMarkup()` confirmed at line 335 |
-| `src/review/store/revision-types.ts` | Present — `PropertyChangeData`, `MoveData`, `SupportedRevisionKind` includes `'property-change'` confirmed |
-| `src/review/store/revision-store.ts` | Present — `createRevisionRecord` passes through `propertyChangeData` and `moveData` (declared in proof bundle) |
-| `src/model/canonical-document.ts` | Present — `RevisionPropertyChangeData`, `RevisionMoveData`, optional metadata fields confirmed |
-| `test/review/property-change-revisions.test.ts` | Present — 10 tests |
-| `test/review/move-revisions.test.ts` | Present — 7 tests |
-| `.tmp/wave-35-track-proof/revisions.json` | Present — proof bundle with full test results and interface change inventory |
-
-All deliverables: **confirmed**.
-
-### Proof bundle verification
-
-Proof artifact: `.tmp/wave-35-track-proof/revisions.json`
-
-New test results from the proof bundle:
-- `property-change-revisions.test.ts`: 10/10 passed, 0 failed
-- `move-revisions.test.ts`: 7/7 passed, 0 failed
-
-Existing revision test results (regression check):
-- `revision-store.test.ts`: 8/8 passed, 0 failed
-- `revision-actions.test.ts`: 11/11 passed, 0 failed
-
-Total: 17 new tests passing, 19 existing tests unaffected (0 regressions).
-
-Proof level: **integration** — satisfied. New tests prove accept/reject paths, preserve-only behavior, linked move IDs, and round-trip serialization. Existing tests confirm no regressions in the revision layer.
-
-### Interface changes verified
-
-Five interface files changed as declared:
-1. `src/review/store/revision-types.ts` — `SupportedRevisionKind` union extended, `PropertyChangeData`, `MoveData`, `PropertyChangeRevision`, `MoveRevision` added
-2. `src/review/store/revision-store.ts` — metadata passthrough added
-3. `src/model/canonical-document.ts` — `RevisionPropertyChangeData`, `RevisionMoveData` added; `RevisionRecord.kind` union extended
-4. `src/io/ooxml/parse-revisions.ts` — two new parsing functions; moveFrom/moveTo and pPrChange/rPrChange carry structured metadata
-5. `src/io/export/serialize-revisions.ts` — `serializePropertyChangeMarkup()` function added; handles accept (remove `*PrChange` element) and reject (replace container with `beforeContainerXml`)
-
-All interface changes: **confirmed landed**.
-
-### Architecture alignment
-
-Per `docs/reference/repository-guidance.md`:
-- Changes route through the canonical model (`src/model/canonical-document.ts`) — satisfied
-- OOXML content is not silently dropped: pPrChange and rPrChange are preserve-only with `PropertyChangeData` in metadata; moveFrom/moveTo are preserve-only with `MoveData` and linked `moveId` — satisfied
-- Actionable property-change kinds (sectPrChange, tblPrChange) have defined accept/reject semantics — satisfied
-- Wave planning lessons rule 12 ("one canonical contract per seam"): the revision contract is extended additively; no parallel runtime envelope created — satisfied
-
-No architecture violations identified.
-
----
-
-## Component Promotion Verification
-
-Declared promotion: `track-change-extensions` → `baseline-proved`
-
-Component matrix check (`.json` and `.md`):
-- `component-cutover-matrix.json` line 1037: `"currentLevel": "baseline-proved"` for `track-change-extensions` — **confirmed**
-- `component-cutover-matrix.md` row for `track-change-extensions`: `baseline-proved` with proof surfaces listed — **confirmed**
-- Wave 35 promotion entry present in both files — **confirmed**
-
-The declared promotion is satisfied by the landed proof.
-
----
-
-## A8 Integration Synthesis Check
-
-Integration recommendation: `ready-for-doc-closure`
-
-Key integration claims against landed state:
-- "A1 proof complete (17/17 tests, 0 regressions)" — confirmed by proof bundle
-- "5 interface changes in revision layer" — confirmed (5 files)
-- "component matrix and current-state already reflect baseline-proved promotion" — confirmed by direct inspection
-- "0 blockers, 0 conflicts, 0 proof gaps" — consistent with landed state
-
-A8 recommendation: **consistent with landed evidence**.
-
----
-
-## Documentation Closure Check
-
-A9 coordination record (`coord-decision-f0242c53`): "All shared-plan docs already aligned — no-change for wave 35"
-
-Verification against actual doc state:
-- `docs/plans/current-state.md`: Wave 35 entry present at "Active Maturity Line" — 17/17 tests, proof artifact path, `track-change-extensions` at `baseline-proved` — **confirmed**
-- `docs/plans/component-cutover-matrix.md`: `track-change-extensions` row present with `baseline-proved` and correct proof surfaces — **confirmed**
-- `docs/plans/component-cutover-matrix.json`: `currentLevel: "baseline-proved"` and promotions entry for wave 35 — **confirmed**
-
-The three "documentation gaps" listed in the integration report (`A1:shared:docs/plans/component-cutover-matrix.md`, `A1:shared:docs/plans/component-cutover-matrix.json`, `component-matrix:track-change-extensions`) were tracker residue from A1's handoff before A9 ran. Actual doc state satisfies all three — no gaps remain.
-
-A9 no-change declaration: **accepted** (docs verified against actual file state).
-
-Documentation gate: **closed**.
-
----
-
-## Blocking Set
-
-None. All gates clear.
-
----
-
-## Gate Summary
-
-| Gate | Status | Evidence |
-|---|---|---|
-| Architecture | pass | Canonical model extended additively; no DOM shortcuts; OOXML preserved or structured |
-| Integration | pass | A8 ready-for-doc-closure; 0 conflicts, 0 proof gaps |
-| Durability | pass | 17/17 new tests, 0 regressions in existing 19 revision tests |
-| Live | pass | No live deployment claimed; baseline-proved does not require live proof |
-| Docs | pass | component matrix and current-state confirmed aligned; A9 no-change accepted |
-
----
-
-Verdict: PASS

package/docs/plans/waves/reviews/wave-4-cont-qa.md

@@ -1,47 +0,0 @@
-# Wave 4 cont-QA Report
-
-## 2026-03-26T14:06:41Z Reconciliation Pass
-
-Wave 4 is closed under the replanned architecture-only scope.
-
-Evidence reviewed:
-
-- `docs/reference/repository-guidance.md`
-- `docs/reference/wave-planning-lessons.md`
-- `docs/plans/master-plan.md`
-- `docs/plans/current-state.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/plans/component-cutover-matrix.json`
-- `docs/plans/waves/README.md`
-- `docs/plans/waves/wave-4.md`
-- `docs/plans/waves/wave-5.md`
-- `docs/plans/waves/reviews/wave-4-structure-proof.md`
-- `docs/roadmap.md`
-- `src/ui/WordReviewEditor.tsx`
-- `src/ui/editor-surface/editor-surface.tsx`
-- `src/preservation/opaque-fragment-store.ts`
-- `src/validation/compatibility-report.ts`
-- `test/ui/word-review-editor.test.tsx`
-
-Reconciliation:
-
-- Earlier blocked Wave 4 passes evaluated a superseded closure bar that still treated `F03`/`F05`/`F06`/`F07` structural baseline proof as a Wave 4 deliverable.
-- The current shared plan closes Wave 4 as the live shell architecture bridge: runtime-owned editing, review projections, preservation substrate, and compatibility-report derivation.
-- The historical structural packet in [`docs/plans/waves/reviews/wave-4-structure-proof.md`](/home/coder/docx-react-component/docs/plans/waves/reviews/wave-4-structure-proof.md) remains useful carry-forward evidence, but it is no longer the Wave 4 closure gate.
-- Structural fixture proof and comment OOXML roundtrip proof moved to Wave 5 and are already reflected there in the current shared-plan docs.
-
-Gate judgment:
-
-- Architecture: pass. The live `WordReviewEditor` path, runtime-owned review surfaces, preservation substrate, and compatibility derivation are the actual Wave 4 deliverables and are consistently described.
-- Integration: pass. Wave 4 no longer needs to close the structural fixture packet itself; that proof is a Wave 5 responsibility and no longer blocks the architecture slice.
-- Durability: pass. The promoted Wave 4 components close at `repo-landed`, not `baseline-proved`, and the shared docs now honor that narrower bar.
-- Live: pass. This wave has no standalone deploy target or live-service gate.
-- Docs: pass. `README`, `roadmap`, `master-plan`, `current-state`, and the component matrix now tell one consistent Wave 4 story.
-
-Residual carry-forward:
-
-- `F03`/`F05`/`F06`/`F07` structural baseline proof belongs to Wave 5, not Wave 4.
-- Comment OOXML roundtrip proof also belongs to Wave 5.
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave 4 closes as the replanned architecture slice; structural baseline proof moved to and closed in Wave 5
-Verdict: PASS

package/docs/plans/waves/reviews/wave-4-structure-proof.md

@@ -1,69 +0,0 @@
-# Wave 4 Structural Proof
-
-## Status Note
-
-This packet is historical carry-forward evidence from the pre-replan structural pass. It remains useful as a record of what was repo-landed before the live-path proof line stabilized, but it is not the controlling Wave 4 closure gate anymore. Numbering and inline-image closure moved forward into the later live-path proof set; `F05` and `F06` remain preserve-only table/package evidence until the deferred legal-fidelity packet lands first-class tables.
-
-## 2026-03-26T11:04:31Z Structural Fixture Bundle Refresh
-
-Owned deliverables verified:
-
-- `docs/plans/waves/reviews/wave-4-structure-proof.md`
-- `test/fixtures/docx/F03-legal-outline-numbering.docx`
-- `test/fixtures/docx/F05-table-heavy-agreement.docx`
-- `test/fixtures/docx/F06-merged-cells-signature-table.docx`
-- `test/fixtures/docx/F07-inline-images-exhibit.docx`
-- `.tmp/wave-4-structure/structure-roundtrip-report.json`
-- `.tmp/wave-4-structure/sdk-validation-report.json`
-- `.tmp/wave-4-structure/fixture-summary.md`
-
-Proof commands executed:
-
-- `dotnet build services/openxml-validator/OpenXmlValidator.Api.csproj`
-- `curl -fsS http://127.0.0.1:5080/health`
-- `cd services/react-word-editor && ./node_modules/.bin/tsc --ignoreConfig --pretty false --target ES2022 --module nodenext --moduleResolution nodenext --lib ES2022,DOM --types node --typeRoots ./node_modules/@types --esModuleInterop --strict --ignoreDeprecations 6.0 --allowImportingTsExtensions --rewriteRelativeImportExtensions --rootDir ../.. --outDir ../../.tmp/wave-4-structure/build-runtime ../../src/model/cds-1.0.0.ts ../../src/model/canonical-document.ts ../../src/core/commands/list-commands.ts ../../src/io/ooxml/part-manifest.ts ../../src/io/ooxml/parse-main-document.ts ../../src/io/ooxml/parse-numbering.ts ../../src/io/ooxml/parse-tables.ts ../../src/io/ooxml/parse-inline-media.ts ../../src/io/normalize/normalize-text.ts ../../src/io/export/export-session.ts ../../src/io/export/serialize-main-document.ts ../../src/io/export/serialize-numbering.ts ../../src/io/export/serialize-tables.ts ../../src/io/opc/package-reader.ts ../../src/io/opc/package-writer.ts ../../test/io/numbering-roundtrip.test.ts ../../test/io/table-media-roundtrip.test.ts`
-- historical capture note: the 2026-03-26 strict compile attempt hit a then-current import mismatch in `src/core/commands/list-commands.ts` (`CanonicalDocumentEnvelope` vs. the model-layer `CanonicalDocument`). The current repo source no longer carries that drift; the fallback below is retained only as part of the historical capture record.
-- `cd services/react-word-editor && ./node_modules/.bin/tsc --noCheck --ignoreConfig --pretty false --target ES2022 --module nodenext --moduleResolution nodenext --lib ES2022,DOM --types node --typeRoots ./node_modules/@types --esModuleInterop --strict --ignoreDeprecations 6.0 --allowImportingTsExtensions --rewriteRelativeImportExtensions --rootDir ../.. --outDir ../../.tmp/wave-4-structure/build-runtime ../../src/model/cds-1.0.0.ts ../../src/model/canonical-document.ts ../../src/core/commands/list-commands.ts ../../src/io/ooxml/part-manifest.ts ../../src/io/ooxml/parse-main-document.ts ../../src/io/ooxml/parse-numbering.ts ../../src/io/ooxml/parse-tables.ts ../../src/io/ooxml/parse-inline-media.ts ../../src/io/normalize/normalize-text.ts ../../src/io/export/export-session.ts ../../src/io/export/serialize-main-document.ts ../../src/io/export/serialize-numbering.ts ../../src/io/export/serialize-tables.ts ../../src/io/opc/package-reader.ts ../../src/io/opc/package-writer.ts ../../test/io/numbering-roundtrip.test.ts ../../test/io/table-media-roundtrip.test.ts`
-- `node --test .tmp/wave-4-structure/build-runtime/test/io/numbering-roundtrip.test.js .tmp/wave-4-structure/build-runtime/test/io/table-media-roundtrip.test.js`
-- transient validator run held open for the proof refresh shell:
-- `dotnet run --project services/openxml-validator/OpenXmlValidator.Api.csproj --urls http://127.0.0.1:5080`
-- repo-root proof runner `node .tmp/wave-4-structure/generate-structure-proof.mjs` using `.tmp/wave-4-structure/build-runtime/src/...` imports to:
-- load real F03/F05/F06/F07 fixtures
-- parse and normalize each fixture through the current repo import path
-- export a no-op roundtrip variant into `.tmp/wave-4-structure/exports/`
-- validate both source and roundtrip packages through `http://127.0.0.1:5080/validate`
-- write `.tmp/wave-4-structure/structure-roundtrip-report.json`
-- write `.tmp/wave-4-structure/sdk-validation-report.json`
-
-Durable proof outcome:
-
-- This historical packet recorded a `--noCheck` fallback after a then-current `src/core/commands/list-commands.ts` import mismatch. The current repo source no longer needs that specific workaround, but this document still records the original capture rather than fresh proof.
-- Focused runtime tests passed `4/4`:
-- `numbering-roundtrip.test`
-- `table-media-roundtrip.test`
-- All four source fixtures are now valid `.docx` packages under the Open XML SDK validator.
-- `F03` intentionally carries restart-numbering coverage inside the owned fixture set by using two numbering instances (`numId=1` and `numId=2`) in one legal-outline document.
-- `F03` source and roundtrip packages are both SDK-valid, but the repo still drops list semantics on import or export:
-- source `w:numPr` count is `8`
-- roundtrip `w:numPr` count is `0`
-- normalized numbered paragraph count is `0`
-- restart numbering with `numId=2` disappears from canonical state and export
-- `F05` stays package-valid and preserves `w:tbl` plus `w:tblGrid` on a no-op roundtrip, but the table imports as opaque preserved OOXML instead of a typed table surface.
-- `F06` stays package-valid and preserves `w:gridSpan` plus `w:vMerge` on a no-op roundtrip, but merged-cell tables also remain opaque preserved OOXML instead of canonical table state.
-- `F07` source is SDK-valid, but the roundtrip package fails SDK validation because the serializer emits preserved drawing XML without redeclaring the `wp`, `a`, and `pic` namespaces on `word/document.xml`.
-- `F07` also still imports the drawing as `opaque_inline` content rather than a typed image node.
-
-Result:
-
-- Wave 4 structural fixtures and refreshed proof artifacts are durably landed.
-- The owned proof bundle is authoritative for the current repo state, but `compatibility-and-word-validation` is still a `gap`, not `baseline-proved`.
-- The current blockers are:
-- numbering metadata is not carried into canonical state for `F03`
-- tables and merged-cell tables are preserve-only for `F05` and `F06`
-- inline-image roundtrip exports are not SDK-valid for `F07`
-
-Follow-up required outside A5 ownership:
-
-- A1: carry `w:numPr`, `numId`, `ilvl`, and restart semantics into canonical numbering state and back out through export.
-- A2: move tables and inline images off opaque preservation paths into typed structural import or export support.
-- A2: preserve or re-emit required drawing namespaces so exported image fixtures remain SDK-valid.

package/docs/plans/waves/reviews/wave-5-comment-proof.md

@@ -1,158 +0,0 @@
-# Wave 5 Comment Baseline Proof
-
-## Scope
-
-Agent A5 owns the Wave 5 baseline proof bundle for `comments-and-anchor-mapping`.
-
-Owned deliverables:
-
-- `docs/plans/waves/reviews/wave-5-comment-proof.md`
-- `test/fixtures/docx/F09-comments-single-paragraph.docx`
-- `test/fixtures/docx/F10-threaded-comments-resolve.docx`
-- `test/fixtures/docx/F13-comments-on-deleted-text.docx`
-
-Required proof artifacts:
-
-- `.tmp/wave-5-comments/comment-anchor-report.json`
-- `.tmp/wave-5-comments/thread-roundtrip-report.json`
-- `.tmp/wave-5-comments/comment-ui-proof.json`
-
-Supplemental proof artifacts captured for this note:
-
-- `.tmp/wave-5-comments/fixture-sdk-validation.json`
-- `.tmp/wave-5-comments/s01-validator-delta.json`
-
-## Commands
-
-```bash
-dotnet run --project .tmp/wave-5-comments/CommentFixtureProof.csproj
-pnpm exec tsx .tmp/wave-5-comments/generate-comment-proofs.ts
-pnpm exec tsx --test test/io/comment-roundtrip.test.ts test/review/comment-store.test.ts test/review/comment-remapping.test.ts test/core/mapping.test.ts test/validation/compatibility-engine.test.ts test/ui/comment-review-surface.test.tsx test/ui/word-review-editor.interaction.test.tsx
-pnpm --filter @docx-react-component/react-word-editor-harness test
-```
-
-## Durable Proof
-
-Fixture validation artifact:
-
-- `.tmp/wave-5-comments/fixture-sdk-validation.json`
-- generated at `2026-03-26T11:47:45.9211205Z`
-- generator: `DocumentFormat.OpenXml 3.5.1.0`
-
-Anchor remap artifact:
-
-- `.tmp/wave-5-comments/comment-anchor-report.json`
-- generated at `2026-03-26T11:47:29.138Z`
-- result: `allCasesPassed = true`
-
-Round-trip artifact:
-
-- `.tmp/wave-5-comments/thread-roundtrip-report.json`
-- generated by `test/io/comment-roundtrip.test.ts`
-- supported fixture: comment id `7` stayed stable across parse, edit, and export
-- supported import fidelity: leading and trailing whitespace in single-paragraph comment bodies now stays intact across parse and export
-- preserve-only fixture: comment id `9` imported detached and stayed out of active serialization
-
-UI integration artifact:
-
-- `.tmp/wave-5-comments/comment-ui-proof.json`
-- generated at `2026-03-26T11:48:23.139Z`
-- result: all recorded assertions are `true`
-
-Scenario smoke artifact:
-
-- `.tmp/wave-5-comments/s01-validator-delta.json`
-- generated at `2026-03-26T11:47:45.9211205Z`
-- `S01` expected vs actual validator delta: package `0 -> 0`, SDK `10 -> 10`
-
-## Fixture Results
-
-`F09` (`test/fixtures/docx/F09-comments-single-paragraph.docx`)
-
-- nested single-paragraph comment anchors on one paragraph
-- package entries: `5`
-- package findings: `0`
-- SDK findings: `0`
-- comment ids: `0`, `1`
-- anchor ids in `word/document.xml`: `0`, `1`
-
-`F10` (`test/fixtures/docx/F10-threaded-comments-resolve.docx`)
-
-- threaded reply plus resolution metadata
-- package entries: `8`
-- package findings: `0`
-- SDK findings: `0`
-- package includes `word/commentsExtended.xml`, `word/commentsIds.xml`, and `word/people.xml`
-- `commentsExtended` records root `paraId=00AAA111 done=true`
-- reply entry records `paraId=00AAA222 paraIdParent=00AAA111`
-
-`F13` (`test/fixtures/docx/F13-comments-on-deleted-text.docx`)
-
-- comment range wraps deleted revision content
-- package entries: `5`
-- package findings: `0`
-- SDK findings: `0`
-- `deletedRunCount = 1`
-- comment range id: `0`
-
-## Remap And UI Coverage
-
-`comment-anchor-report.json` covers:
-
-- overlapping single-paragraph anchors surviving inline edit
-- delete-through behavior detaching the stored anchor instead of dropping the thread
-- paragraph merge remapping an anchored range deterministically across a structural edit
-
-Observed remap outcomes:
-
-- overlap case: outer range `6-16 -> 6-24`, inner range `11-16 -> 19-24`
-- delete-through case: anchor detached with `reason=deleted`, `lastKnownRange=7-9`
-- paragraph merge case: range `6-10 -> 5-9`
-
-`comment-ui-proof.json` covers:
-
-- initial detached thread visibility
-- runtime-added thread count increase from `1` to `2`
-- anchor decoration visibility after add
-- resolve transition from open to resolved
-- compatibility report still advertising `comments-single-paragraph` with `blockExport=false`
-
-## Validation Runs
-
-Focused TypeScript proof run:
-
-- command: `pnpm exec tsx --test test/io/comment-roundtrip.test.ts test/review/comment-store.test.ts test/review/comment-remapping.test.ts test/core/mapping.test.ts test/validation/compatibility-engine.test.ts test/ui/comment-review-surface.test.tsx test/ui/word-review-editor.interaction.test.tsx`
-- result: `28/28` passing
-
-Live runtime correction:
-
-- `src/core/commands/index.ts` now routes content-changing edits through detached-anchor normalization instead of raw anchor remap only
-- `src/runtime/document-runtime.ts` now exposes `comments.activeCommentId` in `RuntimeRenderSnapshot`
-- `src/ui/WordReviewEditor.tsx` now passes that runtime value through to `EditorSurface`
-- `src/io/ooxml/parse-comments.ts` now preserves leading and trailing whitespace for supported imported comment bodies instead of trimming them away
-- the live shell regression is covered in `test/ui/word-review-editor.interaction.test.tsx`
-
-Harness scenario-manifest run:
-
-- command: `pnpm --filter @docx-react-component/react-word-editor-harness test`
-- result: `4/4` passing
-
-## Word Caveat
-
-`F13` proves that a comment range wrapped around deleted text is structurally valid OOXML with zero SDK findings. Word UI behavior for deleted commented text is still pending Word desktop and Word web certification.
-
-Inference from the encoded structure:
-
-- once the commented content is deleted, reviewers should expect the comment to surface through revision-oriented review UI rather than as a normal inline active-range highlight
-- the fixture exists to keep that behavior explicit and diagnosable, not to hide the edge case behind a false “clean” baseline
-
-## Result
-
-Wave 5 comment baseline proof is met at the durable local integration level:
-
-- the missing F09/F10/F13 fixtures now exist
-- all three fixtures validate with zero package findings and zero SDK findings in the local SDK proof run
-- the comment remap artifact covers overlapping and edited-anchor cases, and supported single-paragraph comment-body whitespace now roundtrips without trimming
-- the round-trip artifact captures supported single-paragraph stability and preserve-only multi-paragraph handling
-- the UI artifact shows detached, open, and resolved comment state flowing through the live editor shell
-- `S01` was recorded separately as a scenario delta artifact rather than treated as a zero-finding release-gate fixture

package/docs/plans/waves/reviews/wave-5-cont-qa.md

@@ -1,68 +0,0 @@
-# Wave 5 cont-QA Report
-
-## 2026-03-26T12:50:19Z Manual Closure Pass
-
-Wave 5 is now clean enough to close.
-
-Evidence reviewed:
-
-- `docs/reference/repository-guidance.md`
-- `docs/reference/ooxml-compliance.md`
-- `docs/roadmap.md`
-- `docs/plans/master-plan.md`
-- `docs/plans/current-state.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/plans/component-cutover-matrix.json`
-- `docs/plans/waves/wave-5.md`
-- `docs/plans/waves/reviews/wave-5-comment-proof.md`
-- `src/api/public-types.ts`
-- `src/core/commands/index.ts`
-- `src/io/ooxml/parse-comments.ts`
-- `src/io/export/serialize-comments.ts`
-- `src/review/store/comment-remapping.ts`
-- `src/review/store/comment-thread.ts`
-- `src/review/store/revision-store.ts`
-- `src/runtime/document-runtime.ts`
-- `src/runtime/review-runtime.ts`
-- `src/ui/WordReviewEditor.tsx`
-- `src/ui/comments/comment-sidebar.tsx`
-- `src/ui/comments/comment-thread-view.tsx`
-- `test/io/comment-roundtrip.test.ts`
-- `test/io/numbering-roundtrip.test.ts`
-- `test/io/table-media-roundtrip.test.ts`
-- `test/review/comment-remapping.test.ts`
-- `test/review/comment-store.test.ts`
-- `test/review/revision-store.test.ts`
-- `test/ui/comment-review-surface.test.tsx`
-- `test/ui/structural-surface.test.tsx`
-- `test/ui/word-review-editor.interaction.test.tsx`
-- `.tmp/wave-5-comments/comment-anchor-report.json`
-- `.tmp/wave-5-comments/thread-roundtrip-report.json`
-- `.tmp/wave-5-comments/comment-ui-proof.json`
-- `.tmp/wave-5-comments/fixture-sdk-validation.json`
-- `.tmp/wave-5-comments/s01-validator-delta.json`
-
-Validation rerun:
-
-- `pnpm exec tsx --test test/io/comment-roundtrip.test.ts test/review/comment-store.test.ts test/review/comment-remapping.test.ts test/core/mapping.test.ts test/validation/compatibility-engine.test.ts test/ui/comment-review-surface.test.tsx test/ui/word-review-editor.interaction.test.tsx`
-- `pnpm exec tsx --test test/io/numbering-roundtrip.test.ts test/io/table-media-roundtrip.test.ts test/ui/structural-surface.test.tsx`
-- `pnpm --filter @docx-react-component/react-word-editor-harness test`
-- `pnpm run wave:doctor`
-- `git diff --check`
-
-Gate judgment:
-
-- Architecture: pass. Comments remain detached from the content tree, anchors only move through transaction mappings, and the live shell now surfaces runtime-owned active-thread state and detached-anchor warnings.
-- Integration: pass. Comment import/export, remapping, structural fixtures, and review UI now line up on one runtime-owned editing path.
-- Durability: pass. Durable artifacts exist under `.tmp/wave-5-comments/`, and the structural/comment test surface reran green after the runtime active-thread and detachment fixes.
-- Live: pass. `S01` remains a delta-tracked scenario artifact with a stable `10 -> 10` SDK-finding baseline, and the harness manifest/tests remain green.
-- Docs: pass. Shared-plan docs and the component matrix now reflect Wave 5 closure, while tracked changes remain bounded to `repo-landed`.
-
-Residual later-scope work:
-
-- tracked-change OOXML import/export and accept/reject flows remain Wave 6 work
-- package-level preservation baseline and malformed-document diagnostics remain later-wave work
-- `S02` remains the primary real-world redline scenario for Wave 6 and later
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave-5 manually closed after structural and comment proof reran green and the live runtime now exposes active-thread plus detached-anchor state end to end
-Verdict: PASS