@beyondwork/docx-react-component 1.0.0 → 1.0.1

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

@@ -1,60 +0,0 @@
-# Wave 20 Continuous QA
-
-Generated on `2026-04-03T11:40:00Z` for Wave 20 / A0.
-
-## Agent Evidence Collected
-
-- A1 delivered the required proof bundle at `.tmp/wave-20-table-proof/test-summary.json`. The bundle proves the owned schema and command tests plus a green repo test run, but it does not prove the shipped editor path uses those deliverables.
-- A2 delivered the required proof bundle at `.tmp/wave-20-table-proof/roundtrip-summary.json`. That bundle proves package-backed table parse and serialize round-trip stability for F05, F06, and synthetic formatting coverage.
-- A8 published `.tmp/main-wave-launcher/integration/wave-20.md` with `ready-for-doc-closure`, but that recommendation is superseded by the later canonical blocker `coord-blocker-cfe321ae`.
-- A9 updated `docs/plans/component-cutover-matrix.md`, `docs/plans/component-cutover-matrix.json`, and `docs/plans/current-state.md`, and reported `no-change` intent for `docs/roadmap.md`, `docs/plans/master-plan.md`, and `docs/plans/migration.md`. No role-owned `[wave-doc-closure]` marker was emitted.
-
-## Current Truth
-
-1. Repo validation passes, but the new proof remains isolated to unit and XML round-trip slices.
-
-- `pnpm test:repo` passed with `217` tests and `0` failures.
-- A1's proof bundle covers `node --test test/runtime/table-schema.test.ts test/runtime/table-commands.test.ts` and `pnpm test:repo`.
-- A2's proof bundle covers `test/io/table-roundtrip.test.ts`.
-- No landed test edits a table cell through the shipped `WordReviewEditor` / runtime path and then exports and reopens the `.docx` without repair.
-
-2. The shipped editor path does not wire table nodes into the live surface.
-
-- A direct Wave 20 smoke check on `test/fixtures/docx/F05-table-heavy-agreement.docx` showed the canonical snapshot contains top-level blocks `paragraph`, `table`, `paragraph`, `table`, `opaque_block`.
-- The same fixture, after `createDocumentRuntime(...).getRenderSnapshot()`, exposed live surface block kinds `paragraph`, `paragraph`, `paragraph`, `paragraph`, `opaque_block`. No table blocks reached the live surface.
-- `src/runtime/surface-projection.ts:42` only special-cases `opaque_block` and otherwise routes top-level blocks through `createParagraphBlock`, so canonical `table` nodes do not become table surface blocks.
-- `src/ui-tailwind/editor-surface/pm-state-from-snapshot.ts:64` only builds paragraph or opaque-block ProseMirror nodes.
-- `src/ui-tailwind/editor-surface/pm-schema.ts:10` has no `table`, `table_row`, `table_cell`, or `table_header_cell` node definitions.
-- `src/ui-tailwind/editor-surface/tw-prosemirror-surface.tsx:131` creates the `EditorView` without registering table node views. `src/ui-tailwind/editor-surface/tw-table-node-view.tsx` is not referenced by the shipped surface path.
-- Wave requirement 2, `docx import → edit → export → reopen without repair`, is therefore not proven and is contradicted by the current runtime wiring.
-
-3. The existing live-path regression guard for tables is a false positive.
-
-- `test/io/docx-session.test.ts:456` claims F05 and F06 remain preserve-only on the live package-backed session path.
-- That test only asserts that the canonical snapshot contains at least one `opaque_block`.
-- On F05, the canonical snapshot already contains real `table` nodes plus a separate `opaque_block` for section properties.
-- The test can therefore pass even when tables are not exposed as live editable table structures and are not verified as whole locked table blocks on the live surface.
-
-4. Shared-plan docs are not closable and now overclaim the landed state.
-
-- No `[wave-doc-closure]` marker exists in `.tmp/main-wave-launcher/coordination/wave-20.jsonl`.
-- `docs/plans/current-state.md:36` and `docs/plans/current-state.md:71` now state that `table-editing` was promoted to `baseline-proved`.
-- `docs/plans/component-cutover-matrix.md:56` and `docs/plans/component-cutover-matrix.json:713` now set `table-editing` to `baseline-proved`.
-- Those updates conflict with the runtime evidence above and with A2's earlier coordination note that the live runtime path remained preserve-only until runtime-backed editing proof landed.
-- `docs/roadmap.md`, `docs/plans/master-plan.md`, and `docs/plans/migration.md` remain unchanged in the worktree, and A9 did not publish a role-owned `closed` or valid `no-change` doc-closure marker.
-
-5. A8's integration recommendation is no longer valid for closure.
-
-- `.tmp/main-wave-launcher/integration/wave-20.md` still recommends `ready-for-doc-closure`.
-- The current canonical control-plane state is `blocked` on `coord-blocker-cfe321ae`.
-- Under the Wave closure rules, the later canonical blocker overrides the earlier integration recommendation.
-
-## Blocking Set
-
-1. The shipped `WordReviewEditor` / runtime path does not render or edit tables end to end, so the declared `table-editing -> baseline-proved` promotion is not honestly met.
-2. Durability proof is insufficient for the shipped path because the repo lacks a real `table cell edit -> export -> reopen` test and the current preserve-only regression test is a false positive.
-3. Shared-plan docs now overclaim `table-editing` as `baseline-proved`, and documentation closure is not complete because no role-owned `[wave-doc-closure]` outcome exists.
-4. A8's `ready-for-doc-closure` recommendation is contradicted by later canonical evidence and cannot be accepted as the final integration state.
-
-[wave-gate] architecture=blocked integration=blocked durability=blocked live=blocked docs=blocked detail=Live table path is unwired, proof is incomplete for shipped behavior, and docs now overclaim baseline-proved
-Verdict: BLOCKED

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

@@ -1,48 +0,0 @@
-# Wave 25 Continuous QA
-
-Generated on `2026-04-03T12:02:55Z` for Wave 25 / A0.
-
-## Agent Evidence Collected
-
-- A1 landed `src/formats/xlsx/model/workbook.ts`, `src/formats/xlsx/model/sheet.ts`, `src/formats/xlsx/model/cell.ts`, `src/formats/xlsx/model/styles.ts`, `test/formats/xlsx/model/workbook.test.ts`, and `.tmp/wave-25-xlsx-proof/model-tests.json`. The proof bundle reports `46` passed and `0` failed tests.
-- A2's attempt result still shows missing deliverables: `src/formats/xlsx/io/xlsx-session.ts`, `test/formats/xlsx/io/xlsx-import.test.ts`, and `.tmp/wave-25-xlsx-proof/import-tests.json`.
-- `pnpm test:repo` passed with `263` tests and `0` failures, but there is still no landed xlsx import test file under `test/formats/xlsx/io/`.
-- A8's authored integration artifact at `.tmp/main-wave-launcher/integration/wave-25.md` still recommends `needs-more-work`. No Wave 25 role-owned `[wave-integration]` marker exists in `.tmp/main-wave-launcher/coordination/wave-25.jsonl` or `.tmp/main-wave-launcher/results/wave-25/`.
-- A9 applied shared-doc edits, but the shared docs now claim `xlsx-import-and-normalization` is `baseline-proved` before the A2 proof gap is closed. No Wave 25 role-owned `[wave-doc-closure]` marker exists in `.tmp/main-wave-launcher/coordination/wave-25.jsonl` or `.tmp/main-wave-launcher/results/wave-25/`.
-
-## Current Truth
-
-1. Repo-local validation is green, but Wave 25 still lacks the required import proof from real `.xlsx` files.
-
-- `pnpm test:repo` passed with `263` tests and `0` failures.
-- `.tmp/main-wave-launcher/results/wave-25/attempt-1/A2.json:38`, `.tmp/main-wave-launcher/results/wave-25/attempt-1/A2.json:43`, and `.tmp/main-wave-launcher/results/wave-25/attempt-1/A2.json:48` still show the missing `xlsx-session.ts`, import test, and import proof bundle.
-- Without those deliverables and proof artifacts, the declared `xlsx-import-and-normalization -> baseline-proved` promotion is not honestly met.
-
-2. The canonical workbook model does not yet satisfy the architecture doc it is supposed to match.
-
-- `docs/architecture/xlsx/canonical-workbook-model-and-commands.md:15` requires the workbook model to remain serializable, and `docs/architecture/xlsx/canonical-workbook-model-and-commands.md:101` requires formula records to retain reference tokens for remapping.
-- `src/formats/xlsx/model/workbook.ts:102`, `src/formats/xlsx/model/sheet.ts:92`, `src/formats/xlsx/model/sheet.ts:97`, `src/formats/xlsx/model/sheet.ts:102`, and `src/formats/xlsx/model/styles.ts:62` all use `Map`-backed canonical stores, so the current workbook state is not directly serializable.
-- `src/formats/xlsx/model/cell.ts:82` defines `FormulaCell` with only `formula`, optional `cachedValue`, and `styleRef`; it does not retain the formula-reference token or remapping structure required by the canonical model doc.
-
-3. Shared-plan docs are not closable and currently overclaim the import component.
-
-- `docs/plans/component-cutover-matrix.md:60` and `docs/plans/component-cutover-matrix.md:61` now mark both xlsx components as `baseline-proved`.
-- `docs/plans/component-cutover-matrix.json:790` and `docs/plans/component-cutover-matrix.json:813` do the same in the JSON matrix.
-- `docs/plans/current-state.md:37`, `docs/plans/current-state.md:38`, and `docs/plans/current-state.md:68` say Wave 25 promoted `xlsx-import-and-normalization` to `baseline-proved` while `docs/plans/current-state.md:77` simultaneously records the A2 gap. That is not a closable shared-plan state.
-- `docs/roadmap.md`, `docs/plans/master-plan.md`, and `docs/plans/migration.md` have no Wave 25 role-owned `closed` or `no-change` closure note from A9.
-
-4. Integration closure has not been reached.
-
-- `.tmp/main-wave-launcher/integration/wave-25.md:3` still says `Recommendation: needs-more-work`.
-- `.tmp/main-wave-launcher/integration/wave-25.md:37` and `.tmp/main-wave-launcher/integration/wave-25.md:38` still carry the A2 proof gap.
-- There is no Wave 25 `[wave-integration]` marker in the coordination log or result artifacts, so the wave never reached `ready-for-doc-closure`.
-
-## Blocking Set
-
-1. A2 has not delivered `src/formats/xlsx/io/xlsx-session.ts`, `test/formats/xlsx/io/xlsx-import.test.ts`, or `.tmp/wave-25-xlsx-proof/import-tests.json`, so `xlsx-import-and-normalization` is unproven at `baseline-proved`.
-2. A1's workbook model still conflicts with the canonical xlsx architecture on serializability and formula-remapping structure, so `xlsx-canonical-workbook-model` is not yet honestly aligned with its own contract.
-3. A8 has not published a positive integration closure. The authored integration artifact still says `needs-more-work`, and no Wave 25 `[wave-integration]` marker exists.
-4. A9 has not closed shared-plan docs. The current shared docs overclaim `xlsx-import-and-normalization` as `baseline-proved`, and no Wave 25 `[wave-doc-closure]` marker or explicit `closed`/`no-change` note exists for `docs/roadmap.md`, `docs/plans/master-plan.md`, and `docs/plans/migration.md`.
-
-[wave-gate] architecture=blocked integration=blocked durability=blocked live=blocked docs=blocked detail=Import proof is missing, shared docs overclaim the import promotion, integration/doc closure markers are absent, and the workbook model still conflicts with the canonical xlsx architecture doc
-Verdict: BLOCKED

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

@@ -1,46 +0,0 @@
-# Wave 28 cont-QA
-
-## 2026-04-05T11:06:30Z
-
-### Scope checked
-
-- Required context read: `README.md`, `docs/reference/repository-guidance.md`, `docs/research/agent-context-sources.md`, `docs/reference/wave-planning-lessons.md`, `docs/roadmap.md`, `docs/plans/waves/wave-28.md`.
-- Canonical wave state re-read before judgment: `.tmp/main-wave-launcher/inboxes/wave-28/shared-summary.md`, `.tmp/main-wave-launcher/inboxes/wave-28/A0.md`, `.tmp/main-wave-launcher/messageboards/wave-28.md`, `.tmp/main-wave-launcher/coordination/wave-28.jsonl`, `.tmp/main-wave-launcher/control-plane/wave-28.jsonl`.
-- Validation run locally on the current worktree: `pnpm test:repo` -> pass, `308` passed, `0` failed.
-
-### Authoritative evidence
-
-- A1 now has durable proof. `.tmp/wave-28-parity-proof/tables-formatting.json` exists and records `status: met` with `pnpm test:repo` passing `308/308`. The owned code and tests are present in `src/runtime/table-commands.ts`, `src/ui-tailwind/editor-surface/pm-command-bridge.ts`, `src/ui-tailwind/editor-surface/pm-schema.ts`, `src/core/commands/formatting-commands.ts`, and `test/core/formatting-commands.test.ts`.
-- A2 is only partial. `src/core/commands/image-commands.ts` and `src/ui-tailwind/editor-surface/search-plugin.ts` exist, but `test/core/image-commands.test.ts`, `test/ui-tailwind/search-plugin.test.ts`, and `.tmp/wave-28-parity-proof/image-search.json` are still missing.
-- A3 is still absent. `src/api/use-docx-editor.ts`, `src/cli/index.ts`, `src/cli/commands.ts`, `test/api/use-docx-editor.test.ts`, `test/cli/cli.test.ts`, and `.tmp/wave-28-parity-proof/hook-cli.json` do not exist.
-- No authoritative integration closure exists yet. There is still no `[wave-integration]` marker in `.tmp/main-wave-launcher/coordination/wave-28.jsonl` or `.tmp/main-wave-launcher/control-plane/wave-28.jsonl`.
-- No authoritative documentation closure exists yet. There is still no `[wave-doc-closure]` marker in `.tmp/main-wave-launcher/coordination/wave-28.jsonl` or `.tmp/main-wave-launcher/control-plane/wave-28.jsonl`.
-
-### Contract review
-
-- A1 exit contract: satisfied.
-- A2 exit contract: not satisfied. Missing required tests and missing required proof bundle.
-- A3 exit contract: not satisfied. Missing owned implementation files, tests, and proof bundle.
-- Component promotion `editor-feature-parity -> baseline-proved`: not satisfied. Only the A1 slice has durable proof; the A2 and A3 slices required by Wave 28 are not proved.
-
-### Documentation review
-
-- `docs/plans/component-cutover-matrix.md` and `docs/plans/component-cutover-matrix.json` now record `editor-feature-parity` at `baseline-proved`.
-- `docs/roadmap.md`, `docs/plans/current-state.md`, and `docs/plans/master-plan.md` now describe Wave 28 features as landed, including search plugin, `useDocxEditor`, and CLI surfaces.
-- Those shared-plan updates currently overclaim the landed state because A2 still lacks its required tests and proof bundle, and A3 has not landed its owned files at all.
-- `docs/plans/migration.md` correctly appears to be `no-change`, but A9 has not emitted the required structured doc-closure result.
-
-### Smallest blocking set
-
-1. A2 has not satisfied its Wave 28 deliverables because `test/core/image-commands.test.ts`, `test/ui-tailwind/search-plugin.test.ts`, and `.tmp/wave-28-parity-proof/image-search.json` are missing.
-2. A3 has not satisfied its Wave 28 deliverables because `src/api/use-docx-editor.ts`, `src/cli/index.ts`, `src/cli/commands.ts`, `test/api/use-docx-editor.test.ts`, `test/cli/cli.test.ts`, and `.tmp/wave-28-parity-proof/hook-cli.json` are missing.
-3. A8 has not produced the required integration closure marker `[wave-integration]`, so the wave is not at `ready-for-doc-closure`.
-4. A9 has not produced the required documentation closure marker `[wave-doc-closure]`, and the shared docs currently overclaim baseline-proved promotion for missing A2/A3 work.
-
-### Notes on projections vs canonical state
-
-- The generated shared summary still reports the old matrix-doc gap. That projection is stale; the matrix files themselves were updated.
-- The wave remains blocked anyway because the canonical implementation and closure markers still do not support the declared promotion.
-
-[wave-gate] architecture=concerns integration=blocked durability=blocked live=pass docs=blocked detail=A1 is proved, but A2 and A3 are incomplete, no A8/A9 closure markers exist, and shared docs overclaim missing work.
-Verdict: BLOCKED

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

@@ -1,53 +0,0 @@
-# Wave 29 cont-QA
-
-## 2026-04-05T13:06Z
-
-Reviewed the wave definition, repository guidance, agent-context sources, wave-planning lessons, current shared summary/inbox/board projections, canonical coordination log, control-plane status, current worktree, and proof artifacts.
-
-### Exit contract review
-
-- A1: satisfied for the owned paragraph/run slice. Present in the worktree:
-  - `src/model/canonical-document.ts`
-  - `src/io/ooxml/parse-main-document.ts`
-  - `src/io/export/serialize-main-document.ts`
-  - `src/io/normalize/normalize-text.ts`
-  - `test/io/paragraph-properties-roundtrip.test.ts`
-  - `.tmp/wave-29-parsing-proof/paragraph-run.json`
-- A1 validation:
-  - Local check run by cont-QA: `pnpm exec tsx --test test/io/paragraph-properties-roundtrip.test.ts` -> pass
-  - A1-reported wave evidence: `pnpm test:repo` -> 366 pass, 0 fail
-- A2: blocked. No landed A2-owned code/test/proof changes are present yet under:
-  - `src/io/ooxml/parse-tables.ts`
-  - `src/io/export/serialize-tables.ts`
-  - `src/io/ooxml/parse-fields.ts`
-  - `test/io/table-properties-roundtrip.test.ts`
-  - `test/io/fields-bookmarks.test.ts`
-  - `.tmp/wave-29-parsing-proof/tables-fields.json`
-- A8: blocked. The integration artifact remains stale at `needs-more-work`, and no final `[wave-integration]` marker is present.
-- A9: blocked. Shared-plan edits exist in:
-  - `docs/plans/component-cutover-matrix.md`
-  - `docs/plans/component-cutover-matrix.json`
-  - `docs/plans/current-state.md`
-  - `docs/plans/master-plan.md`
-  - `docs/roadmap.md`
-- A9 has not emitted `[wave-doc-closure] state=closed|no-change`, and the current diffs overclaim `ooxml-parsing-fidelity` as `baseline-proved` before the A2 proof bundle and wave-level closure exist.
-
-### Component promotion review
-
-- `ooxml-parsing-fidelity -> baseline-proved`: not yet satisfied.
-- A1 now provides durable proof for the paragraph/run slice, but the shared component still depends on the missing A2 table/fields/bookmarks deliverables, a truthful A8 integration closure, and a truthful A9 doc closure.
-
-### Canonical state checks
-
-- Proof registry: `pnpm exec wave control proof get --lane main --wave 29` returned an empty `entries` list.
-- Rerun state: `pnpm exec wave control rerun get --lane main --wave 29` returned `rerunRequest: null`.
-- Wave control status remains blocked on `wave-29-shared-plan-docs`.
-
-### Smallest blocking set
-
-1. A2 must land its owned code/tests and `.tmp/wave-29-parsing-proof/tables-fields.json`.
-2. A8 must publish final integration output with a closing `[wave-integration]` marker.
-3. A9 must reconcile the shared-plan docs to the actual proof state and emit `[wave-doc-closure] state=closed|no-change`; current diffs still overclaim the promotion.
-
-[wave-gate] architecture=concerns integration=blocked durability=blocked live=pass docs=blocked detail=A1 is proved, but A2 proof plus truthful integration/doc closure are still missing
-Verdict: BLOCKED

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

@@ -1,53 +0,0 @@
-# Wave 3 cont-QA Report
-
-## 2026-03-26T10:36:30Z Manual Closure Pass
-
-Wave 3 is now clean enough to close.
-
-Evidence reviewed:
-
-- `docs/reference/repository-guidance.md`
-- `docs/reference/ooxml-compliance.md`
-- `docs/roadmap.md`
-- `docs/plans/current-state.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/plans/component-cutover-matrix.json`
-- `docs/plans/waves/reviews/wave-3-core-proof.md`
-- `docs/plans/waves/reviews/wave-3-validator-proof.md`
-- `src/core/schema/text-schema.ts`
-- `src/core/commands/text-commands.ts`
-- `src/core/state/text-transaction.ts`
-- `src/io/export/serialize-main-document.ts`
-- `src/ui/WordReviewEditor.tsx`
-- `test/io/text-roundtrip.test.ts`
-- `test/ui/word-review-editor.test.tsx`
-- `.tmp/wave-3-core-text/text-roundtrip-report.json`
-- `.tmp/wave-3-core-text/sdk-validation-report.json`
-- `.tmp/wave-3-core-text/ui-smoke-report.json`
-- `.tmp/wave-3-core-text/f08-relationship-audit.json`
-
-Validation rerun:
-
-- `git diff --check`
-- `cd services/react-word-editor && ./node_modules/.bin/tsc --noCheck --ignoreConfig --pretty false --target ES2022 --module nodenext --moduleResolution nodenext --lib ES2022,DOM --types node,react,react-dom --typeRoots ./node_modules/@types --esModuleInterop --strict --ignoreDeprecations 6.0 --allowImportingTsExtensions --rewriteRelativeImportExtensions --jsx react-jsx --outDir ../../.tmp/wave-3-core-text/build-runtime ../../src/api/public-types.ts ../../src/core/selection/mapping.ts ../../src/core/state/editor-state.ts ../../src/core/schema/text-schema.ts ../../src/core/state/text-transaction.ts ../../src/core/commands/text-commands.ts ../../src/io/ooxml/part-manifest.ts ../../src/io/opc/package-reader.ts ../../src/io/opc/package-writer.ts ../../src/io/opc/docx-package.ts ../../src/io/export/export-session.ts ../../src/io/export/minimal-docx.ts ../../src/io/export/serialize-main-document.ts ../../src/io/normalize/normalize-text.ts ../../src/io/ooxml/parse-main-document.ts ../../src/runtime/document-runtime.ts ../../src/ui/editor-surface/editor-surface.tsx ../../src/ui/toolbar/core-toolbar.tsx ../../src/ui/compatibility/compatibility-panel.tsx ../../src/ui/status/status-bar.tsx ../../src/ui/WordReviewEditor.tsx ../../test/io/package-reader.test.ts ../../test/io/text-roundtrip.test.ts ../../test/ui/word-review-editor.test.tsx ../../test/ui/core-text-editor.test.tsx`
-- `node --test .tmp/wave-3-core-text/build-runtime/test/io/package-reader.test.js .tmp/wave-3-core-text/build-runtime/test/io/text-roundtrip.test.js`
-- `NODE_PATH=/home/coder/docx-react-component/services/react-word-editor/node_modules node --test .tmp/wave-3-core-text/build-runtime/test/ui/word-review-editor.test.js .tmp/wave-3-core-text/build-runtime/test/ui/core-text-editor.test.js`
-- `dotnet run --project services/openxml-validator/OpenXmlValidator.Api.csproj --urls http://127.0.0.1:5080`
-- `curl -fsS http://127.0.0.1:5080/health`
-- node-based `POST /validate` checks against source and edited F01/F02/F08 fixtures
-
-Gate judgment:
-
-- Architecture: pass. The Wave 3 text substrate survives preserved `opaque_block` content, and F08 relationship preservation is repaired.
-- Integration: pass. The shipped shell now composes the Wave 3 chrome surfaces and the named-fixture proof artifacts match the source.
-- Durability: pass. The proof bundle is machine-readable and covers compile, IO, UI, real edited exports, and SDK validation.
-- Live: pass. The local validator service remains healthy and returns clean results for the Wave 3 fixtures.
-- Docs: pass. Shared-plan docs and review artifacts now match the landed Wave 3 surface instead of the older blocker history.
-
-Residual later-scope work:
-
-- interactive document-surface text editing is still deferred
-- lists, tables, inline media, comments, and tracked changes remain outside Wave 3 scope
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave-3 manually closed after named-fixture F01/F02/F08 export validation passed and the shell now composes the landed chrome surfaces
-Verdict: PASS

package/docs/plans/waves/reviews/wave-3-core-proof.md

@@ -1,77 +0,0 @@
-# Wave 3 Core Proof
-
-## 2026-03-26T10:42:45Z Authoritative Named-Fixture Proof Refresh
-
-Owned deliverables verified:
-
-- `docs/plans/waves/reviews/wave-3-core-proof.md`
-- `test/fixtures/docx/F01-basic-contract.docx`
-- `test/fixtures/docx/F02-headings-styles.docx`
-- `test/fixtures/docx/F08-hyperlinks.docx`
-- `.tmp/wave-3-core-text/text-roundtrip-report.json`
-- `.tmp/wave-3-core-text/sdk-validation-report.json`
-- `.tmp/wave-3-core-text/ui-smoke-report.json`
-- `.tmp/wave-3-core-text/f08-relationship-audit.json`
-
-Proof commands executed:
-
-- `cd services/react-word-editor && ./node_modules/.bin/tsc --ignoreConfig --pretty false --target ES2022 --module nodenext --moduleResolution nodenext --lib ES2022,DOM --types node,react,react-dom --typeRoots ./node_modules/@types --esModuleInterop --strict --ignoreDeprecations 6.0 --allowImportingTsExtensions --rewriteRelativeImportExtensions --jsx react-jsx --outDir ../../.tmp/wave-3-core-text/build-refresh ../../test/io/package-reader.test.ts ../../test/io/text-roundtrip.test.ts ../../test/core/text-commands.test.ts ../../test/ui/word-review-editor.test.tsx ../../test/ui/core-text-editor.test.tsx`
-- `cd services/react-word-editor && ./node_modules/.bin/tsc --noCheck --ignoreConfig --pretty false --target ES2022 --module nodenext --moduleResolution nodenext --lib ES2022,DOM --types node,react,react-dom --typeRoots ./node_modules/@types --esModuleInterop --strict --ignoreDeprecations 6.0 --allowImportingTsExtensions --rewriteRelativeImportExtensions --jsx react-jsx --outDir ../../.tmp/wave-3-core-text/build-runtime ../../src/api/public-types.ts ../../src/core/selection/mapping.ts ../../src/core/state/editor-state.ts ../../src/core/schema/text-schema.ts ../../src/core/state/text-transaction.ts ../../src/core/commands/text-commands.ts ../../src/io/ooxml/part-manifest.ts ../../src/io/opc/package-reader.ts ../../src/io/opc/package-writer.ts ../../src/io/opc/docx-package.ts ../../src/io/export/export-session.ts ../../src/io/export/minimal-docx.ts ../../src/io/export/serialize-main-document.ts ../../src/io/normalize/normalize-text.ts ../../src/io/ooxml/parse-main-document.ts ../../test/io/package-reader.test.ts ../../test/io/text-roundtrip.test.ts ../../test/core/text-commands.test.ts ../../test/ui/word-review-editor.test.tsx ../../test/ui/core-text-editor.test.tsx`
-- `node --test .tmp/wave-3-core-text/build-runtime/test/io/package-reader.test.js .tmp/wave-3-core-text/build-runtime/test/io/text-roundtrip.test.js .tmp/wave-3-core-text/build-runtime/test/core/text-commands.test.js`
-- `NODE_PATH=/home/coder/docx-react-component/services/react-word-editor/node_modules node --test --test-reporter=tap .tmp/wave-3-core-text/build-runtime/test/ui/word-review-editor.test.js .tmp/wave-3-core-text/build-runtime/test/ui/core-text-editor.test.js > .tmp/wave-3-core-text/ui-smoke.tap`
-- `dotnet build services/openxml-validator/OpenXmlValidator.Api.csproj -nologo`
-- `curl -fsS http://127.0.0.1:5080/health`
-- repo-root node scripts using `.tmp/wave-3-core-text/build-runtime/src/...` imports to:
-- load the real Wave 3 fixtures `F01`, `F02`, and `F08`
-- run `insertText` at the start of each imported story
-- export edited `.docx` variants into `.tmp/wave-3-core-text/exports/`
-- re-import the edited packages for roundtrip summaries
-- post both source and edited variants to `http://127.0.0.1:5080/validate`
-- write `.tmp/wave-3-core-text/text-roundtrip-report.json`
-- write `.tmp/wave-3-core-text/sdk-validation-report.json`
-- write `.tmp/wave-3-core-text/ui-smoke-report.json`
-- write `.tmp/wave-3-core-text/f08-relationship-audit.json`
-
-Durable proof outcome:
-
-- The strict build-refresh compile passed.
-- The runtime proof bundle compile passed.
-- Focused runtime tests passed `11/11`:
-- `package-reader.test`
-- `text-roundtrip.test`
-- `text-commands.test`
-- The previously failing F08 assertion now passes: `F08 export preserves relationships referenced by opaque OOXML`.
-- `.tmp/wave-3-core-text/text-roundtrip-report.json` is now the authoritative named-fixture report again, not the synthetic unit-test report:
-- `state: "pass"`
-- fixtures covered: `F01`, `F02`, `F08`
-- every fixture passed import -> command-backed `insertText` -> export -> re-import
-- every fixture preserved text/story shape, preserve-only opaque payloads, style references, and hyperlink targets after the edit
-- `.tmp/wave-3-core-text/sdk-validation-report.json` is `state: "pass"`:
-- validator health is `ok`
-- all three source fixtures are SDK-clean
-- all three edited exports are SDK-clean
-- `.tmp/wave-3-core-text/ui-smoke-report.json` is `state: "pass"` with `6/6` passing tests covering:
-- server-rendered `WordReviewEditor` shell render
-- imperative ref bridge
-- uncontrolled source resolution
-- `CoreToolbar` (standalone test variant; production functionality is inline in `PrototypeReviewWorkspace`)
-- `CompatibilityPanel`
-- `StatusBar` (standalone test variant; production functionality is inline in `PrototypeReviewWorkspace`)
-- `.tmp/wave-3-core-text/f08-relationship-audit.json` now shows:
-- `missingReferencedRelationships: []`
-- the preserved table hyperlink reference `rIdLink2` remains present in edited `word/document.xml`
-- the matching `rIdLink2` relationship also remains present in edited `word/_rels/document.xml.rels`
-
-Important artifact note:
-
-- `test/io/text-roundtrip.test.ts` still writes a synthetic regression report as part of its unit proof.
-- A4 therefore regenerates `.tmp/wave-3-core-text/text-roundtrip-report.json` from the real named fixtures after the Node test pass.
-- The final file state in `.tmp/wave-3-core-text/` is the authoritative A4 proof bundle.
-
-A4 scope result:
-
-- The prior named-fixture command-edit blocker is resolved.
-- The prior F08 export relationship blocker is resolved.
-- A4's authoritative proof bundle now satisfies the requested exit contract at `completion=authoritative`, `durability=durable`, and `proof=integration`.
-- This refresh does not claim wave-wide closure.
-- The separate wave-level UI integration blocker tracked against `src/ui/WordReviewEditor.tsx` remains outside A4-owned scope and still belongs to A3, A8, and A0 until they refresh integration and QA posture.

package/docs/plans/waves/reviews/wave-3-validator-proof.md

@@ -1,73 +0,0 @@
-# Wave 3 Validator Proof
-
-## Scope
-
-Agent A5 owns the Wave 3 baseline proof for `openxml-sdk-validator-service`.
-
-Owned deliverables:
-
-- `services/openxml-validator/Program.cs`
-- `services/openxml-validator/README.md`
-- `services/openxml-validator/OpenXmlValidator.Api.csproj`
-- `.tmp/wave-3-validator/health.json`
-- `.tmp/wave-3-validator/validate-smoke.json`
-
-## Service Contract Landed
-
-The validator remains validation-only.
-
-`POST /validate` now returns a stable machine-readable payload with:
-
-- `document`
-- `summary`
-- `package`
-- `sdk`
-
-The `package.findings` and `sdk.findings` collections are distinct arrays so callers can gate on summary counts and then inspect each validation surface independently.
-
-Bad requests return a stable error payload with:
-
-- `service`
-- `error`
-- `detail`
-
-## Commands
-
-```bash
-dotnet build services/openxml-validator/OpenXmlValidator.Api.csproj
-dotnet run --project services/openxml-validator/OpenXmlValidator.Api.csproj --urls http://127.0.0.1:5080
-curl -s http://127.0.0.1:5080/health > .tmp/wave-3-validator/health.json
-curl -s -F "file=@/home/coder/docx-react-component/.tmp/wave-3-validator/smoke-valid.docx;type=application/vnd.openxmlformats-officedocument.wordprocessingml.document" http://127.0.0.1:5080/validate > .tmp/wave-3-validator/validate-smoke.json
-```
-
-## Durable Proof
-
-Build proof:
-
-- `dotnet build services/openxml-validator/OpenXmlValidator.Api.csproj`
-- Result: succeeded with `0 Warning(s)` and `0 Error(s)`
-
-Live smoke artifacts:
-
-- `.tmp/wave-3-validator/health.json`
-- `.tmp/wave-3-validator/validate-smoke.json`
-
-Observed results from `validate-smoke.json`:
-
-- `validatedAtUtc`: `2026-03-26T08:45:49.2687715+00:00`
-- `document.fileName`: `smoke-valid.docx`
-- `document.fileSizeBytes`: `1026`
-- `summary.isValid`: `true`
-- `summary.packageFindingCount`: `0`
-- `summary.sdkFindingCount`: `0`
-- `package.entryCount`: `3`
-
-## Result
-
-The Wave 3 baseline proof requirement for `openxml-sdk-validator-service` is met at the local integration level:
-
-- service starts locally on `.NET 8`
-- `GET /health` responds with the validator identity and endpoint list
-- `POST /validate` accepts multipart `.docx` upload input
-- package checks and Open XML SDK findings are returned as separate structured collections
-- a smoke `.docx` validates with zero package findings and zero SDK findings

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

@@ -1,43 +0,0 @@
-# Wave 32 cont-QA
-
-## 2026-04-05 Attempt 2
-
-- Reviewed `docs/plans/waves/wave-32.md`, `.tmp/main-wave-launcher/integration/wave-32.md`, `.tmp/main-wave-launcher/integration/wave-32.json`, `.tmp/main-wave-launcher/coordination/wave-32.jsonl`, `.tmp/main-wave-launcher/control-plane/wave-32.jsonl`, `.tmp/main-wave-launcher/results/wave-32/attempt-1/A1.json`, and the current Wave 32 worktree diffs.
-- Local validation passed:
-  - `pnpm exec tsx --test test/io/paragraph-properties-roundtrip.test.ts test/io/table-properties-roundtrip.test.ts` -> 14 pass, 0 fail
-  - `pnpm test:repo` -> 379 pass, 0 fail
-- Functional regressions were not reproduced in the current worktree, but Wave 32 still fails closed on durable proof and role-owned closure artifacts.
-
-### Exit contract review
-
-- A1: not closed. The required proof artifact `.tmp/wave-32-props-proof/all-props.json` is absent in canonical state, and the declared deliverable `test/io/property-completeness.test.ts` does not exist. The landed tests are `test/io/paragraph-properties-roundtrip.test.ts` and `test/io/table-properties-roundtrip.test.ts`; they passed locally, but they do not satisfy the exact machine-checkable deliverable set declared in `docs/plans/waves/wave-32.md`.
-- A8: blocked. `.tmp/main-wave-launcher/integration/wave-32.md` still recommends `needs-more-work`, and there is no role-owned `[wave-integration] state=ready-for-doc-closure` marker in `.tmp/main-wave-launcher/coordination/wave-32.jsonl`, `.tmp/main-wave-launcher/control-plane/wave-32.jsonl`, or `.tmp/main-wave-launcher/results/wave-32/`.
-- A9: blocked. There is no role-owned `[wave-doc-closure] state=closed|no-change` marker in `.tmp/main-wave-launcher/coordination/wave-32.jsonl`, `.tmp/main-wave-launcher/control-plane/wave-32.jsonl`, or `.tmp/main-wave-launcher/results/wave-32/`. The current shared-plan diffs advance Wave 29 `ooxml-parsing-fidelity`; they do not close Wave 32 `ooxml-property-completeness`.
-
-### Component promotion review
-
-- `ooxml-property-completeness -> baseline-proved`: not satisfied.
-- `docs/plans/component-cutover-matrix.json` contains `components["ooxml-property-completeness"].currentLevel = "inventoried"`.
-- `docs/plans/component-cutover-matrix.md` has no Current Levels row for `ooxml-property-completeness` and no Wave 32 promotion entry.
-- The board now shows an A1 decision claiming the proof gap is being closed, but there is still no durable proof artifact or updated attempt result to back that intent.
-
-### Exact remaining closure delta
-
-- A1 must land the required proof artifact `.tmp/wave-32-props-proof/all-props.json` and reconcile the declared test deliverable. Either `test/io/property-completeness.test.ts` must exist, or the authoritative wave contract must be updated so the actual owned test files are the machine-checked deliverables.
-- A8 must publish final integration output with `[wave-integration] state=ready-for-doc-closure`.
-- A9 must publish `[wave-doc-closure]` and reconcile shared-plan truth. Exact Wave 32 doc delta from the current state:
-  - `docs/plans/component-cutover-matrix.json`: set `components["ooxml-property-completeness"].currentLevel` to `baseline-proved` only if A1 proof lands; otherwise leave it at `inventoried` and close as `no-change`.
-  - `docs/plans/component-cutover-matrix.md`: add the matching Current Levels row and Wave 32 promotion note only if A1 proof lands.
-  - `docs/roadmap.md`, `docs/plans/current-state.md`, `docs/plans/master-plan.md`, `docs/plans/migration.md`: A9 must emit an explicit `closed` or `no-change` note for Wave 32. The current worktree does not contain a Wave 32 closure note for these paths.
-
-### Closure judgment
-
-- Security and cont-EVAL are not applicable blockers for Wave 32.
-- Live deployment proof is not required for this repo-local baseline-proved wave.
-- The smallest blocking set is:
-  - missing A1 durable proof artifact and unresolved exact deliverable mismatch
-  - missing A8 integration closure marker
-  - missing A9 documentation closure marker and unresolved component-matrix truth for Wave 32
-
-[wave-gate] architecture=concerns integration=blocked durability=blocked live=pass docs=blocked detail=Tests pass, but Wave 32 still lacks A1 durable proof plus A8 and A9 closure artifacts
-Verdict: BLOCKED