@beyondwork/docx-react-component 1.0.0 → 1.0.1

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

@@ -1,416 +0,0 @@
-# Wave 6 cont-QA Report
-
-## 2026-03-26T14:06:41Z Reconciliation Pass
-
-Wave 6 is clean enough to close under its bounded scope.
-
-Evidence reviewed:
-
-- `docs/reference/repository-guidance.md`
-- `docs/reference/ooxml-compliance.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/roadmap.md`
-- `docs/plans/waves/README.md`
-- `docs/plans/waves/wave-6.md`
-- `docs/plans/waves/reviews/wave-6-redline-proof.md`
-- `src/io/docx-session.ts`
-- `src/review/store/revision-actions.ts`
-- `test/review/revision-actions.test.ts`
-- `test/review/revision-store.test.ts`
-- `test/io/revision-roundtrip.test.ts`
-- `test/io/docx-session.test.ts`
-- `test/preservation/opaque-fragment-store.test.ts`
-
-Validation rerun:
-
-- `pnpm exec tsx --test test/review/revision-actions.test.ts test/review/revision-store.test.ts test/io/revision-roundtrip.test.ts test/io/docx-session.test.ts`
-  - result: `19` pass, `0` fail
-
-Reconciliation:
-
-- Earlier blocked Wave 6 passes are superseded. The runtime/public-shell seam is closed in the shared plan, the package-backed session regression is fixed on the current worktree, and the old `F12` paragraph-mark gap no longer reflects the current proof surface.
-- Wave 6 now closes on a bounded bar: `F11` run-level insertions or deletions are proved, `F12` paragraph-mark accept or reject is proved on the source-backed runtime/export path, `F14` stays preserve-only, and broader imported-redline freeform divergence remains explicit Wave 7 carry-forward work.
-- Preservation maturity is also now coherent across the shared docs: the opaque-fragment and source-backed session substrate is `baseline-proved`, while full preserved-part proof and unknown-part reporting remain Wave 7 work.
-
-Gate judgment:
-
-- Architecture: pass. Package-backed `initialDocx` sessions now materialize supported imported comments and revisions into runtime-owned state, and bounded paragraph-mark review actions resolve through the same reducer and export surface used by the live shell.
-- Integration: pass. The current shared plan, proof note, and source-backed session path all agree on the same bounded Wave 6 claim.
-- Durability: pass. The current review and session test set is green, with explicit preserve-only handling still in place for unsupported structural revisions.
-- Live: pass. Wave 6 is not a live-proof wave, and no deploy or service blocker is open here.
-- Docs: pass. The shared-plan docs and Wave 6 proof note now agree on what closed, what stayed preserve-only, and what moved to Wave 7.
-
-Residual carry-forward:
-
-- `tracked-changes-and-review-actions` remains `repo-landed`, not `baseline-proved`, because broader imported-redline freeform editing can still diverge from source-backed replay and block export.
-- Wave 7 owns preserved-part proof, unknown-part reporting, and the remaining imported-redline divergence export block.
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave 6 closes under its bounded scope: F11 and source-backed F12 are proved, F14 stays preserve-only, and broader imported-redline divergence moves to Wave 7
-Verdict: PASS
-
-## 2026-03-26T14:42:40Z Canonical Closure Recheck
-
-Wave 6 is still blocked in canonical closure state even though the bounded implementation and shared-plan content now line up.
-
-Evidence reviewed:
-
-- `pnpm exec wave control status --lane main --wave 6`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A9.json`
-- `.tmp/main-wave-launcher/inboxes/wave-6/A9.md`
-- `docs/roadmap.md`
-- `docs/plans/master-plan.md`
-- `docs/plans/current-state.md`
-- `docs/plans/migration.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/plans/component-cutover-matrix.json`
-
-Validation rerun:
-
-- `pnpm exec tsx --test test/review/revision-actions.test.ts test/review/revision-store.test.ts test/io/revision-roundtrip.test.ts test/io/docx-session.test.ts test/preservation/opaque-fragment-store.test.ts`
-  - result: `23` pass, `1` fail
-  - bounded interpretation: the only failure is `S02 exports after freeform edits without flattening imported review markup`, which matches the documented Wave 7 carry-forward export block for imported redlined source divergence rather than a bounded Wave 6 regression
-
-Reconciliation:
-
-- The earlier `PASS` section above is superseded by this recheck because it is not backed by the current canonical closure artifacts.
-- The bounded Wave 6 technical claim still holds: `F11` run-level revision proof is present, `F12` paragraph-mark accept or reject is covered on the source-backed runtime/export path, `F14` structural revisions remain preserve-only, and tracked moves plus formatting revisions stay out of the supported action surface.
-- The shared-plan files appear aligned to that bounded claim. `docs/roadmap.md`, `docs/plans/master-plan.md`, `docs/plans/current-state.md`, `docs/plans/component-cutover-matrix.md`, and `docs/plans/component-cutover-matrix.json` all record the same Wave 6 posture; `docs/plans/migration.md` appears to be a valid no-change file for this wave.
-- Canonical closure is still blocked because documentation closure has not been emitted as durable state. `pnpm exec wave control status --lane main --wave 6` still reports A9 blocked, and `.tmp/main-wave-launcher/results/wave-6/attempt-2/A9.json` records only `docDelta.state = "none"` with no explicit documentation-closure result. No current Wave 6 artifact shows the required A9 `closed` or `no-change` closure outcome.
-
-Smallest blocking set:
-
-- A9 must emit an explicit documentation-closure result for the owned shared-plan set: `docs/roadmap.md`, `docs/plans/master-plan.md`, `docs/plans/current-state.md`, `docs/plans/migration.md`, `docs/plans/component-cutover-matrix.md`, and `docs/plans/component-cutover-matrix.json`.
-
-Gate judgment:
-
-- Architecture: pass. The bounded runtime, OOXML, and preserve-only claims remain coherent with the repo contracts.
-- Integration: pass. A8 attempt-2 is `ready-for-doc-closure`, and no newer implementation evidence reopens a Wave 6 scope contradiction.
-- Durability: pass. The focused rerun stays green for the bounded Wave 6 slice; the only red case is the documented `S02` carry-forward export block that Wave 7 already owns.
-- Live: pass. Wave 6 is not a deploy or live-proof wave.
-- Docs: blocked. The content appears aligned, but the required A9 closure signal is still missing from canonical state.
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=blocked detail=Wave 6 shared-plan content aligns, but canonical closure is still missing A9 closed or no-change doc-closure output
-Verdict: BLOCKED
-
-## 2026-03-26T15:01:08Z Final Closure Pass
-
-Wave 6 now clears the docs gate and is coherent enough to close under its bounded maturity claim.
-
-Evidence reviewed:
-
-- `docs/reference/repository-guidance.md`
-- `docs/reference/ooxml-compliance.md`
-- `docs/reference/wave-planning-lessons.md`
-- `docs/plans/current-state.md`
-- `docs/plans/waves/wave-5.md`
-- `docs/plans/waves/wave-6.md`
-- `docs/plans/waves/reviews/wave-6-redline-proof.md`
-- `docs/roadmap.md`
-- `docs/plans/master-plan.md`
-- `docs/plans/migration.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/plans/component-cutover-matrix.json`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json`
-- `.tmp/main-wave-launcher/coordination/wave-6.jsonl`
-- `.tmp/main-wave-launcher/logs/wave-6-6-a9.log`
-- `.tmp/main-wave-launcher/reducer/wave-6.json`
-- `.tmp/main-wave-launcher/ledger/wave-6.json`
-
-Validation rerun:
-
-- `pnpm exec tsx --test test/review/revision-actions.test.ts test/review/revision-store.test.ts test/io/revision-roundtrip.test.ts test/io/docx-session.test.ts test/ui/revision-review-surface.test.tsx test/preservation/opaque-fragment-store.test.ts`
-  - result: `28` pass, `0` fail
-
-Reconciliation:
-
-- The prior blocked section above is superseded by this pass. The missing documentation gate is now satisfied by A9's role-owned marker in `.tmp/main-wave-launcher/logs/wave-6-6-a9.log`: `[wave-doc-closure] state=closed paths=docs/roadmap.md,docs/plans/master-plan.md,docs/plans/current-state.md,docs/plans/migration.md,docs/plans/component-cutover-matrix.md,docs/plans/component-cutover-matrix.json ...`.
-- The raw coordination records also make the closure scope explicit. `coord-evidence-74fef6b4` records all six shared-plan paths, confirms `unsupported-ooxml-preservation=baseline-proved` and `tracked-changes-and-review-actions=repo-landed`, and states `Migration is no-change`. `coord-handoff-e08cdfdd` records that no further doc delta is required beyond the already-landed edits.
-- A8's typed result artifact remains authoritative for integration despite stale projection files: `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json` reports `integration.state = ready-for-doc-closure` with `blockers = 0`, and no later evidence reopens an implementation or proof contradiction.
-- The reducer shows no active rerun hold for Wave 6: `.tmp/main-wave-launcher/reducer/wave-6.json` records `rerunRequestsById = {}` and `rerunRequests = []`.
-- The bounded technical claim remains honest and fully backed by machine-visible proof on the current worktree: `F11` run-level insertion/deletion roundtrip and accept/reject are proved, `F12` paragraph-mark accept/reject is proved on the runtime-owned source-backed export path, `F14` structural revisions remain preserve-only, tracked moves and formatting revisions remain preserve-only, and `S02` now passes on the canonical export path without expanding the component maturity claim beyond `repo-landed`.
-- Some generated projections still lag older blocker residue, but the latest role-owned closure outputs, coordination records, raw logs, and validation rerun all agree on the smaller and now-empty blocker set.
-
-Gate judgment:
-
-- Architecture: pass. Wave 6 preserves the schema-first, runtime-owned review path and keeps preserve-only revision classes explicit instead of flattening them.
-- Integration: pass. The current A8 result, A9 doc-closure marker, and landed shared-plan docs agree on the same bounded Wave 6 claim.
-- Durability: pass. The focused Wave 6 validation rerun is fully green on the current worktree, including `S02` export on the canonical path, with preserve-only structural revision behavior still explicit.
-- Live: pass. Wave 6 is a repo-landed wave with no deployment or infra proof requirement.
-- Docs: pass. `docs/roadmap.md`, `docs/plans/master-plan.md`, `docs/plans/current-state.md`, `docs/plans/migration.md`, `docs/plans/component-cutover-matrix.md`, and `docs/plans/component-cutover-matrix.json` all align with the bounded Wave 6 outcome, and A9 emitted `[wave-doc-closure] state=closed`.
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave 6 closes under its bounded scope: F11 and source-backed F12 are proved, F14 stays preserve-only, docs are closed, and no rerun is pending
-Verdict: PASS
-
-## 2026-03-26T15:12:08Z Canonical Consistency Sweep
-
-Wave 6 PASS still stands after the latest projection reread and bounded validation rerun.
-
-Evidence reviewed:
-
-- `.tmp/main-wave-launcher/inboxes/wave-6/shared-summary.md`
-- `.tmp/main-wave-launcher/inboxes/wave-6/A0.md`
-- `.tmp/main-wave-launcher/messageboards/wave-6.md`
-- `.tmp/main-wave-launcher/coordination/wave-6.jsonl`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A0.json`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A9.json`
-- `.tmp/main-wave-launcher/logs/wave-6-6-a9.log`
-- `docs/plans/waves/reviews/wave-6-redline-proof.md`
-- `docs/plans/current-state.md`
-- `docs/plans/master-plan.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/roadmap.md`
-
-Validation rerun:
-
-- `pnpm exec tsx --test test/review/revision-actions.test.ts test/review/revision-store.test.ts test/io/revision-roundtrip.test.ts test/io/docx-session.test.ts test/ui/revision-review-surface.test.tsx test/preservation/opaque-fragment-store.test.ts`
-  - result: `28` pass, `0` fail
-  - bounded interpretation: `S02` is green on the current canonical export path, while `F14` remains preserve-only by design rather than actionable revision proof
-
-Reconciliation:
-
-- The shared summary, inbox, board, signals, and some synthesized result envelopes still lag older blocker residue. `A0.json` and `A9.json` under `.tmp/main-wave-launcher/results/wave-6/attempt-2/` are `_synthesizedFromLegacy` envelopes from the earlier blocked state and do not override the later role-owned closure outputs.
-- The later closure outputs are consistent with each other. `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json` records `integration.state = ready-for-doc-closure` with `blockers = 0`; `.tmp/main-wave-launcher/logs/wave-6-6-a9.log` emits `[wave-doc-closure] state=closed`; and the coordination log ends with `coord-integration-summary-25c8502c` for the final A0 PASS plus `coord-integration-summary-99264776` for the refreshed A8 zero-blocker state.
-- `pnpm exec wave control rerun get --lane main --wave 6` reports `rerunRequest = null` and `effectiveSelectedAgentIds = []`. The persisted relaunch-plan snapshot is stale compatibility residue from the earlier blocked pass, not an active rerun hold.
-- `pnpm exec wave control proof get --lane main --wave 6` reports an empty registry. No active proof bundle is missing, revoked, or superseded for this wave.
-- The bounded Wave 6 claim remains honest: `unsupported-ooxml-preservation` is `baseline-proved`; `tracked-changes-and-review-actions` stays `repo-landed`; `F11` and source-backed `F12` are proved; tracked moves, formatting revisions, and `F14` structural revisions remain preserve-only; Wave 7 still owns broader preserved-part and package-fidelity proof.
-
-Gate judgment:
-
-- Architecture: pass. Runtime-owned review actions and source-backed export still define the supported revision path, and preserve-only revision classes stay explicit.
-- Integration: pass. Later A8 closure artifacts supersede the stale blocker projections and keep the blocker count at `0`.
-- Durability: pass. The focused Wave 6 rerun is fully green on the current worktree, including the current `S02` canonical export path.
-- Live: pass. Wave 6 remains a repo-landed wave with no deployment or infra proof requirement.
-- Docs: pass. A9 emitted `[wave-doc-closure] state=closed` for the full shared-plan set, and the shared docs still match the bounded claim.
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave 6 PASS remains authoritative after the final consistency sweep: A8 and A9 closure outputs align, rerunRequest is null, and the focused validation rerun is 28/0
-Verdict: PASS
-
-## 2026-03-26T15:29:14Z Canonical Status Reconciliation Sweep
-
-Wave 6 PASS still stands after the latest control-plane reread, documentation re-verification, and bounded rerun on the current worktree.
-
-Evidence reviewed:
-
-- `.tmp/main-wave-launcher/inboxes/wave-6/shared-summary.md`
-- `.tmp/main-wave-launcher/inboxes/wave-6/A0.md`
-- `.tmp/main-wave-launcher/messageboards/wave-6.md`
-- `.tmp/main-wave-launcher/coordination/wave-6.jsonl`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A9.json`
-- `.tmp/main-wave-launcher/logs/wave-6-6-a9.log`
-- `docs/reference/ooxml-compliance.md`
-- `docs/research/docx-react-component/document_compatibility_and_testing_spec.md`
-- `docs/plans/waves/specs/wave-1-ooxml-contracts.md`
-- `docs/roadmap.md`
-- `docs/plans/current-state.md`
-- `docs/plans/master-plan.md`
-- `docs/plans/migration.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/plans/component-cutover-matrix.json`
-- `pnpm exec wave control status --lane main --wave 6`
-- `pnpm exec wave control rerun get --lane main --wave 6`
-- `pnpm exec wave control proof get --lane main --wave 6`
-
-Validation rerun:
-
-- `pnpm exec tsx --test test/review/revision-actions.test.ts test/review/revision-store.test.ts test/io/revision-roundtrip.test.ts test/io/docx-session.test.ts test/ui/revision-review-surface.test.tsx test/preservation/opaque-fragment-store.test.ts`
-  - result: `31` pass, `0` fail
-  - bounded interpretation: the current worktree now keeps the formerly blocked package-backed comment import and `S02` freeform-edit export cases green without expanding the Wave 6 maturity claim past `repo-landed`
-
-Reconciliation:
-
-- `pnpm exec wave control status --lane main --wave 6` is still blocked on the old A8 seam blocker and launcher/A9 residue. That output is not the current closure authority. It conflicts with later canonical artifacts and is therefore treated as stale projection state, not a reopened Wave 6 blocker.
-- The later canonical artifacts agree on the smaller blocker set of zero. `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json` still reports `integration.state = ready-for-doc-closure` with `blockers = 0`, and the coordination tail adds `coord-integration-summary-1fa80e1f` at `2026-03-26T15:23:57Z`, explicitly restating zero unresolved blockers and bounded PASS alignment.
-- Documentation closure is reaffirmed after the prior PASS section, not merely inherited from it. `.tmp/main-wave-launcher/logs/wave-6-6-a9.log` still emits `[wave-doc-closure] state=closed`, and the coordination tail adds `coord-evidence-db0378c0` plus `coord-handoff-f249c13d` at `2026-03-26T15:27Z`, confirming all six shared-plan paths remain aligned and that `docs/plans/migration.md` is valid `no-change` scope for this wave.
-- `pnpm exec wave control rerun get --lane main --wave 6` still reports `rerunRequest = null`, and `pnpm exec wave control proof get --lane main --wave 6` still reports an empty registry. There is no active rerun hold or missing proof-bundle lifecycle state blocking closure.
-- The repo contracts remain consistent with the bounded Wave 6 claim. `docs/reference/ooxml-compliance.md`, the local compatibility testing spec, and `docs/plans/waves/specs/wave-1-ooxml-contracts.md` all still require tracked moves, formatting revisions, and structural list/table revisions to remain `preserve-only`; the current proof and shared-plan docs keep that line intact.
-- The shared-plan docs remain honest about maturity. `unsupported-ooxml-preservation` is `baseline-proved`; `tracked-changes-and-review-actions` remains `repo-landed`; `F11` and source-backed `F12` are proved; `F14`, tracked moves, and formatting revisions stay preserve-only; and `S02` remains bounded scenario evidence rather than zero-delta validator or Word certification proof.
-
-Gate judgment:
-
-- Architecture: pass. The supported revision path still runs through runtime-owned actions and source-backed export, while preserve-only revision classes remain explicitly non-actionable.
-- Integration: pass. The latest A8 result and coordination refresh supersede the stale blocked status output and keep the authoritative blocker count at `0`.
-- Durability: pass. The focused rerun is `31/0` green on the current worktree, including package-backed comment import and `S02` export coverage, while preserving the bounded Wave 6 claim.
-- Live: pass. Wave 6 is still a repo-landed wave with no deploy or infra proof bar.
-- Docs: pass. A9 re-verified all six shared-plan paths after the prior PASS section and reasserted closure with no remaining doc delta.
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave 6 PASS remains authoritative after the canonical status sweep: stale control status output is superseded, A8 and A9 remain closed, rerunRequest is null, and the bounded rerun is 31/0
-Verdict: PASS
-
-## 2026-03-26T15:41:30Z Post-A8 Artifact Reconciliation Sweep
-
-Wave 6 PASS still stands after the latest A8 attempt result, one more control-plane reread, and a fresh bounded validation rerun on the current worktree.
-
-Evidence reviewed:
-
-- `.tmp/main-wave-launcher/inboxes/wave-6/shared-summary.md`
-- `.tmp/main-wave-launcher/inboxes/wave-6/A0.md`
-- `.tmp/main-wave-launcher/messageboards/wave-6.md`
-- `.tmp/main-wave-launcher/coordination/wave-6.jsonl`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A0.json`
-- `.tmp/main-wave-launcher/integration/wave-6.json`
-- `.tmp/main-wave-launcher/logs/wave-6-6-a9.log`
-- `docs/plans/waves/reviews/wave-6-redline-proof.md`
-- `docs/roadmap.md`
-- `docs/plans/current-state.md`
-- `docs/plans/master-plan.md`
-- `docs/plans/migration.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/plans/component-cutover-matrix.json`
-- `docs/research/docx-react-component/Feature Compatibility Matrix for a React Word Compatible Legal Editor v1.md`
-- `pnpm exec wave control status --lane main --wave 6`
-- `pnpm exec wave control rerun get --lane main --wave 6`
-- `pnpm exec wave control proof get --lane main --wave 6`
-
-Validation rerun:
-
-- `pnpm exec tsx --test test/review/revision-actions.test.ts test/review/revision-store.test.ts test/io/revision-roundtrip.test.ts test/io/docx-session.test.ts test/ui/revision-review-surface.test.tsx test/preservation/opaque-fragment-store.test.ts`
-  - result: `31` pass, `0` fail
-  - bounded interpretation: the current worktree keeps `F11`, source-backed `F12`, package-backed comment import, and the current `S02` canonical export path green without raising the component claim above `repo-landed`
-
-Reconciliation:
-
-- `pnpm exec wave control status --lane main --wave 6` still reports the old blocked state with `coord-blocker-03cf9331` and A9 blocked. That output remains a lagging control-plane compatibility surface, not the current closure authority.
-- `pnpm exec wave control rerun get --lane main --wave 6` still reports `rerunRequest = null`, and `pnpm exec wave control proof get --lane main --wave 6` still reports an empty registry. There is no active rerun hold and no missing active proof-bundle lifecycle state.
-- The current attempt-scoped A8 result artifact is authoritative for integration. `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json` completed at `2026-03-26T15:35:18.606Z` and records `integration.state = ready-for-doc-closure` with `claims = 0`, `conflicts = 0`, and `blockers = 0`.
-- `.tmp/main-wave-launcher/integration/wave-6.json` still serializes `unresolvedBlockers = 4`, `proofGaps = 2`, and `docGaps = 17` even though its top-level recommendation/detail text matches the later zero-blocker truth. That file is therefore treated as a lagging synthesized compatibility surface over append-only coordination residue, not as a reopened blocker, because it conflicts with the later attempt-scoped A8 result artifact plus the later A8 coordination outputs `coord-integration-summary-1fa80e1f` and `coord-integration-summary-93eac76b`.
-- A9's role-owned closure output remains intact. `.tmp/main-wave-launcher/logs/wave-6-6-a9.log` still emits `[wave-doc-closure] state=closed` for `docs/roadmap.md`, `docs/plans/current-state.md`, `docs/plans/master-plan.md`, `docs/plans/migration.md`, `docs/plans/component-cutover-matrix.md`, and `docs/plans/component-cutover-matrix.json`.
-- The shared-plan docs still match the bounded Wave 6 claim: `unsupported-ooxml-preservation` is `baseline-proved`; `tracked-changes-and-review-actions` remains `repo-landed`; `F11` and source-backed `F12` are proved; `F14`, tracked moves, and formatting revisions remain preserve-only; and `S02` remains bounded scenario evidence rather than zero-delta validator or Word certification proof.
-- The local compatibility matrix still requires tracked moves, tracked formatting changes, and structural list/table revisions to remain preserve-only. The current docs and green rerun continue to honor that boundary. A5's older `S02` carry-forward wording is more conservative than the current rerun, but later validation and shared-plan docs supersede it without changing maturity.
-
-Gate judgment:
-
-- Architecture: pass. The supported revision path remains runtime-owned and source-backed, while preserve-only revision classes stay explicitly non-actionable.
-- Integration: pass. The authoritative A8 result artifact and latest A8 coordination summaries keep the current blocker count at `0`; stale projection surfaces do not reopen the wave.
-- Durability: pass. The focused rerun is `31/0` green on the current worktree, covering the bounded Wave 6 redline and package-backed session slice.
-- Live: pass. Wave 6 remains a repo-landed wave with no deploy or infra proof requirement.
-- Docs: pass. A9's closed marker still covers the full shared-plan set, and the current plan docs still reflect the bounded outcome honestly.
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave 6 PASS remains authoritative after the latest A8 artifact sweep: rerunRequest is null, proof registry is empty, stale status surfaces remain superseded, and the bounded rerun is 31/0
-Verdict: PASS
-
-## 2026-03-26T15:51:40Z Final Compatibility-Surface Sweep
-
-Wave 6 PASS still stands after one more canonical reread, a fresh bounded rerun, and a direct check of the remaining stale projection surfaces.
-
-Evidence reviewed:
-
-- `.tmp/main-wave-launcher/inboxes/wave-6/shared-summary.md`
-- `.tmp/main-wave-launcher/inboxes/wave-6/A0.md`
-- `.tmp/main-wave-launcher/messageboards/wave-6.md`
-- `.tmp/main-wave-launcher/coordination/wave-6.jsonl`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json`
-- `.tmp/main-wave-launcher/integration/wave-6.json`
-- `.tmp/main-wave-launcher/integration/wave-6.md`
-- `.tmp/main-wave-launcher/logs/wave-6-6-a9.log`
-- `docs/roadmap.md`
-- `docs/plans/master-plan.md`
-- `docs/plans/current-state.md`
-- `docs/plans/migration.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/plans/component-cutover-matrix.json`
-- `docs/plans/waves/reviews/wave-6-redline-proof.md`
-- `docs/research/docx-react-component/Feature Compatibility Matrix for a React Word Compatible Legal Editor v1.md`
-- `docs/research/docx-react-component/document_compatibility_and_testing_spec.md`
-- `pnpm exec wave control status --lane main --wave 6`
-- `pnpm exec wave control rerun get --lane main --wave 6`
-- `pnpm exec wave control proof get --lane main --wave 6`
-
-Validation rerun:
-
-- `pnpm exec tsx --test test/review/revision-actions.test.ts test/review/revision-store.test.ts test/io/revision-roundtrip.test.ts test/io/docx-session.test.ts test/ui/revision-review-surface.test.tsx test/preservation/opaque-fragment-store.test.ts`
-  - result: `31` pass, `0` fail
-  - bounded interpretation: the current worktree keeps `F11`, source-backed `F12`, package-backed session import/export, and the canonical `S02` export path green while leaving tracked moves, tracked formatting changes, and `F14` structural revisions preserve-only
-
-Reconciliation:
-
-- The generated shared summary, inbox, board, and `pnpm exec wave control status --lane main --wave 6` still serialize the old blocked state. They remain stale projection residue and do not override the canonical closure sources.
-- A8's attempt-scoped result artifact remains the authoritative integration result. `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json` records `integration.state = ready-for-doc-closure` with `claims = 0`, `conflicts = 0`, and `blockers = 0`.
-- The latest A8 coordination outputs also remain positive. `coord-integration-summary-0c888961` keeps `[wave-integration] state=ready-for-doc-closure claims=0 conflicts=0 blockers=0`, and `coord-evidence-1827be6a` states that the owned integration artifacts were refreshed.
-- Direct reads of `.tmp/main-wave-launcher/integration/wave-6.json` and `.tmp/main-wave-launcher/integration/wave-6.md` still show stale blocker, proof-gap, and doc-gap counts even though their top-level recommendation/detail text now matches the closed Wave 6 claim. That contradiction is a compatibility-surface defect, but it does not reopen the wave because the wave-core canonical authority set is the coordination log plus attempt-scoped result artifacts, and those later role-owned artifacts remain consistent and positive.
-- A9's role-owned closure output remains unambiguous. `.tmp/main-wave-launcher/logs/wave-6-6-a9.log` still emits `[wave-doc-closure] state=closed`, and the latest A9 coordination records `coord-evidence-d9a4f39a` and `coord-handoff-098f83fb` reaffirm that all six shared-plan docs remain aligned with the bounded Wave 6 proof and that `docs/plans/migration.md` is valid `no-change` scope.
-- `pnpm exec wave control rerun get --lane main --wave 6` still reports `rerunRequest = null`, and `pnpm exec wave control proof get --lane main --wave 6` still reports an empty registry. There is no active rerun hold and no missing active proof bundle.
-- The shared-plan docs remain honest and aligned with the local research contracts. `unsupported-ooxml-preservation` is still `baseline-proved`; `tracked-changes-and-review-actions` remains `repo-landed`; `F11` and source-backed `F12` are proved; tracked moves, tracked formatting changes, and `F14` structural revisions remain preserve-only; and `S02` remains bounded scenario evidence rather than zero-delta validator or Word certification proof.
-
-Gate judgment:
-
-- Architecture: pass. The supported revision path remains runtime-owned, source-backed, and explicitly bounded away from preserve-only revision classes.
-- Integration: pass. The authoritative A8 attempt result and later role-owned `[wave-integration]` output stay at zero blockers; stale generated integration/status surfaces are recorded as superseded compatibility residue, not reopened blockers.
-- Durability: pass. The focused Wave 6 rerun is `31/0` green on the current worktree and still covers the bounded redline and package-backed session slice.
-- Live: pass. Wave 6 remains a repo-landed wave with no deployment or infra proof requirement.
-- Docs: pass. A9's closed marker still covers the full shared-plan set, the latest A9 verification reaffirmed the same six paths, and the docs still match the bounded compatibility story.
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave 6 PASS remains authoritative after the final compatibility-surface sweep: A8 attempt result and A9 doc closure stay canonical, stale status surfaces remain superseded, and the bounded rerun is 31/0
-Verdict: PASS
-
-## 2026-03-26T19:55:47Z Canonical Artifact Refresh Sweep
-
-Wave 6 PASS still stands after rereading the latest generated projections, checking the current canonical artifacts, verifying owned deliverable presence, and rerunning the bounded revision or preservation test bundle on the current worktree.
-
-Evidence reviewed:
-
-- `.tmp/main-wave-launcher/inboxes/wave-6/shared-summary.md`
-- `.tmp/main-wave-launcher/inboxes/wave-6/A0.md`
-- `.tmp/main-wave-launcher/messageboards/wave-6.md`
-- `.tmp/main-wave-launcher/coordination/wave-6.jsonl`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json`
-- `.tmp/main-wave-launcher/results/wave-6/attempt-2/A0.json`
-- `.tmp/main-wave-launcher/logs/wave-6-6-a9.log`
-- `.tmp/main-wave-launcher/integration/wave-6.md`
-- `.tmp/main-wave-launcher/integration/wave-6.json`
-- `.tmp/main-wave-launcher/reducer/wave-6.json`
-- `.tmp/main-wave-launcher/ledger/wave-6.json`
-- `.tmp/main-wave-launcher/signals/wave-6.json`
-- `docs/roadmap.md`
-- `docs/plans/master-plan.md`
-- `docs/plans/current-state.md`
-- `docs/plans/migration.md`
-- `docs/plans/component-cutover-matrix.md`
-- `docs/plans/component-cutover-matrix.json`
-- `docs/plans/waves/wave-6.md`
-- `docs/plans/waves/reviews/wave-6-redline-proof.md`
-- `docs/reference/ooxml-compliance.md`
-- `docs/research/docx-react-component/document_compatibility_and_testing_spec.md`
-- `docs/research/docx-react-component/Feature Compatibility Matrix for a React Word Compatible Legal Editor v1.md`
-
-Owned deliverable presence recheck:
-
-- `src/review/store/revision-actions.ts`, `src/core/commands/review-commands.ts`, `src/runtime/revision-runtime.ts`, and `test/review/revision-actions.test.ts` all exist for A1.
-- `src/io/ooxml/parse-revisions.ts`, `src/io/export/serialize-revisions.ts`, `src/io/ooxml/revision-boundaries.ts`, and `test/io/revision-roundtrip.test.ts` all exist for A2.
-- `src/ui/review/markup-display-switch.tsx`, `src/ui/review/revision-sidebar.tsx`, `src/ui/review/accept-reject-actions.tsx`, and `test/ui/revision-review-surface.test.tsx` all exist for A3.
-- `src/preservation/opaque-fragment-store.ts`, `src/preservation/preserved-part-manifest.ts`, `src/ui/editor-surface/locked-region.tsx`, and `test/preservation/opaque-fragment-store.test.ts` all exist for A4.
-- A5's owned proof note `docs/plans/waves/reviews/wave-6-redline-proof.md` and the `.tmp/wave-6-redlines/` proof artifacts remain present.
-
-Validation rerun:
-
-- `pnpm exec tsx --test test/review/revision-actions.test.ts test/review/revision-store.test.ts test/io/revision-roundtrip.test.ts test/io/docx-session.test.ts test/ui/revision-review-surface.test.tsx test/preservation/opaque-fragment-store.test.ts`
-  - result: `31` pass, `0` fail
-  - bounded interpretation: the current worktree keeps `F11`, source-backed `F12`, package-backed comment/revision session import-export, and the current canonical `S02` export path green while leaving tracked moves, tracked formatting changes, and `F14` structural revisions preserve-only
-
-Reconciliation:
-
-- The generated shared summary, inbox, board, `signals/wave-6.json`, and `pnpm exec wave control status --lane main --wave 6` still lag the older blocked doc-closure state. They remain stale projection surfaces and do not override the later role-owned closure artifacts.
-- The reducer and ledger no longer show an open owned-slice blocker. `.tmp/main-wave-launcher/reducer/wave-6.json` marks the A0, A8, and A9 tasks `status = "proven"` with `closureState = "owned_slice_proven"`, and `.tmp/main-wave-launcher/ledger/wave-6.json` marks `cont-qa:A0` and `integration:A8` as `state = "done"` and `documentation:A9` as `state = "done"` with `docState = "closed"`.
-- The current attempt-scoped A8 result artifact remains authoritative for integration. `.tmp/main-wave-launcher/results/wave-6/attempt-2/A8.json` records `integration.state = ready-for-doc-closure` with `claims = 0`, `conflicts = 0`, and `blockers = 0`.
-- The A8-owned compatibility artifacts still mix current top-level closure text with older proof-gap and doc-gap counts. That inconsistency is stale synthesized residue, not a reopened blocker, because it conflicts with the later A8 attempt result, the later A8 coordination refresh, the reducer or ledger state, and the green bounded rerun.
-- A9's role-owned closure output remains definitive. `.tmp/main-wave-launcher/logs/wave-6-6-a9.log` still emits `[wave-doc-closure] state=closed`, and the latest coordination entries `coord-evidence-a795640f` and `coord-handoff-b4b61757` confirm all six shared-plan paths remain aligned with the bounded Wave 6 claim and that `docs/plans/migration.md` is valid `no-change` scope.
-- `pnpm exec wave control rerun get --lane main --wave 6` still reports `rerunRequest = null`, and `pnpm exec wave control proof get --lane main --wave 6` still reports an empty registry. There is no active rerun hold and no missing active proof bundle.
-- The shared-plan docs remain honest about maturity. `unsupported-ooxml-preservation` stays `baseline-proved`; `tracked-changes-and-review-actions` remains `repo-landed` for Wave 6; `F11` and source-backed `F12` are proved; tracked moves, tracked formatting changes, and `F14` structural revisions stay preserve-only; and `S02` remains bounded scenario evidence rather than zero-delta validator or Word certification proof.
-
-Gate judgment:
-
-- Architecture: pass. The supported revision path remains runtime-owned, source-backed, and bounded away from preserve-only revision classes.
-- Integration: pass. The authoritative A8 attempt result and later coordination refresh keep blockers at `0`; stale projection surfaces do not reopen the wave.
-- Durability: pass. The focused Wave 6 rerun is `31/0` green on the current worktree and still covers the bounded redline, package-backed session, and preserve-only honesty contract.
-- Live: pass. Wave 6 remains a repo-landed wave with no deployment or infra proof requirement.
-- Docs: pass. A9's closed marker still covers the full shared-plan set, the latest A9 verification reaffirmed the same six paths, and the docs still match the bounded compatibility story.
-
-[wave-gate] architecture=pass integration=pass durability=pass live=pass docs=pass detail=Wave 6 PASS remains authoritative after the 19:55 canonical artifact sweep: owned deliverables exist, the bounded rerun is 31/0, A9 doc closure stays closed, and stale status surfaces remain superseded
-Verdict: PASS

package/docs/plans/waves/reviews/wave-6-redline-proof.md

@@ -1,130 +0,0 @@
-# Wave 6 Redline Proof
-
-## Scope
-
-Agent A5 owns the Wave 6 proof bundle for the redline fixture slice:
-
-- `test/fixtures/docx/F11-redlines-basic.docx`
-- `test/fixtures/docx/F12-redlines-paragraph-joins-splits.docx`
-- `test/fixtures/docx/F14-revisions-in-tables-and-lists.docx`
-- `.tmp/wave-6-redlines/redline-roundtrip-report.json`
-- `.tmp/wave-6-redlines/accept-reject-report.json`
-- `.tmp/wave-6-redlines/revision-mapping-report.json`
-
-The proof goal is bounded and honest:
-
-- prove run-level insertion or deletion roundtrip and accept or reject behavior
-- prove paragraph-mark revisions resolve through the runtime-owned review path and source-backed export
-- record structural list and table revisions as preserve-only rather than reporting them as PASS
-- capture `S02` as source-vs-export scenario evidence without treating it as fixture replacement proof
-
-This note supersedes the earlier A5 artifact bundle that still carried the pre-A2 `F12` paragraph-mark gap.
-
-## 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:5082
-curl -fsS http://127.0.0.1:5082/health > .tmp/wave-6-redlines/validator-health.json
-curl -fsS -F "file=@test/fixtures/docx/F11-redlines-basic.docx;type=application/vnd.openxmlformats-officedocument.wordprocessingml.document" http://127.0.0.1:5082/validate > .tmp/wave-6-redlines/validate-F11.json
-curl -fsS -F "file=@test/fixtures/docx/F12-redlines-paragraph-joins-splits.docx;type=application/vnd.openxmlformats-officedocument.wordprocessingml.document" http://127.0.0.1:5082/validate > .tmp/wave-6-redlines/validate-F12.json
-curl -fsS -F "file=@test/fixtures/docx/F14-revisions-in-tables-and-lists.docx;type=application/vnd.openxmlformats-officedocument.wordprocessingml.document" http://127.0.0.1:5082/validate > .tmp/wave-6-redlines/validate-F14.json
-curl -fsS -F "file=@test/fixtures/scenarios/docx/S02-bw-partner-user-licence-agreement-redlines.docx;type=application/vnd.openxmlformats-officedocument.wordprocessingml.document" http://127.0.0.1:5082/validate > .tmp/wave-6-redlines/validate-S02-source.json
-pnpm exec tsx --test test/review/revision-actions.test.ts test/review/revision-store.test.ts
-pnpm exec tsx --test test/io/revision-roundtrip.test.ts test/io/docx-session.test.ts
-pnpm exec tsx --test test/ui/revision-review-surface.test.tsx
-pnpm exec tsx --test test/ui/word-review-editor.test.tsx
-pnpm exec tsx .tmp/wave-6-redlines/generate-proof.ts
-```
-
-Command note:
-
-- `test/io/docx-session.test.ts` currently still includes the broader `S02` freeform-edit export case, which remains outside the bounded Wave 6 proof bar and fails on the current worktree for imported-redline divergence. `F11`, `F12`, and `F14` remain the authoritative fixture proof surface for this note.
-
-## Durable Artifacts
-
-Fixture package outputs:
-
-- `test/fixtures/docx/F11-redlines-basic.docx`
-- `test/fixtures/docx/F12-redlines-paragraph-joins-splits.docx`
-- `test/fixtures/docx/F14-revisions-in-tables-and-lists.docx`
-
-Primary proof reports:
-
-- `.tmp/wave-6-redlines/redline-roundtrip-report.json`
-- `.tmp/wave-6-redlines/accept-reject-report.json`
-- `.tmp/wave-6-redlines/revision-mapping-report.json`
-
-Exported proof packages:
-
-- `.tmp/wave-6-redlines/exports/F11.roundtrip.docx`
-- `.tmp/wave-6-redlines/exports/F11.accepted.docx`
-- `.tmp/wave-6-redlines/exports/F11.rejected.docx`
-- `.tmp/wave-6-redlines/exports/F12.roundtrip.docx`
-- `.tmp/wave-6-redlines/exports/F12.accept-delete.docx`
-- `.tmp/wave-6-redlines/exports/F12.reject-insert.docx`
-- `.tmp/wave-6-redlines/exports/F12.reviewed.docx`
-- `.tmp/wave-6-redlines/exports/F14.roundtrip.docx`
-- `.tmp/wave-6-redlines/exports/S02.roundtrip.docx`
-
-Validator captures:
-
-- `.tmp/wave-6-redlines/validator-health.json`
-- `.tmp/wave-6-redlines/validate-F11.json`
-- `.tmp/wave-6-redlines/validate-F12.json`
-- `.tmp/wave-6-redlines/validate-F14.json`
-- `.tmp/wave-6-redlines/validate-S02-source.json`
-
-## Observed Results
-
-`F11` run-level insertions and deletions are the clean pass case.
-
-- source package validates with `0` package findings and `0` SDK findings
-- roundtrip export validates with `0` package findings and `0` SDK findings
-- accepted export removes `<w:ins>` and `<w:del>` containers and leaves accepted text as plain runs
-- rejected export removes `<w:ins>` and `<w:del>` containers and restores deleted text as plain runs
-
-`F12` paragraph-mark revisions are now proved on the bounded source-backed runtime/export path.
-
-- source package validates with `0` package findings and `0` SDK findings
-- roundtrip export validates with `0` package findings and `0` SDK findings
-- parser emits `revision:del-31` and `revision:ins-32`
-- imported paragraph-mark revisions remain machine-visible as paragraph-boundary anchors with `originalRevisionType` metadata
-- `test/review/revision-actions.test.ts` proves the bounded imported-review shape: `paragraph-del` accept merges adjacent paragraphs, and `paragraph-ins` reject removes the inserted boundary while preserving explicit preserve-only skips for unsupported structural ranges
-- package-backed proof exports now include `F12.accept-delete.docx`, `F12.reject-insert.docx`, and `F12.reviewed.docx`; all three validate with `0` package findings and `0` SDK findings
-- `test/io/docx-session.test.ts` proves the source-backed `F12` session path: accept or reject updates runtime content, reduces paragraph-break count, exports a new package, and the combined reviewed export normalizes back to the updated runtime snapshot
-- this is the authoritative Wave 6 proof bar for `F12`; broader imported-redline freeform editing still remains out of scope
-
-`F14` stays preserve-only and is reported that way.
-
-- source package validates with `0` package findings and `0` SDK findings
-- roundtrip export validates with `0` package findings and `0` SDK findings
-- source OOXML contains moved-list paragraph markers and inserted table-row revision markup
-- current revision parser materializes `0` canonical revisions from this fixture, so the structural revision evidence remains package-level preserve-only proof rather than actionable review-state proof
-
-`S02` is recorded as scenario evidence only.
-
-- source validation: `0` package findings, `48` SDK findings
-- unchanged export validation: `0` package findings, `48` SDK findings
-- source-vs-export delta: `0` package findings, `0` SDK findings
-- the broader `S02` freeform-edit export case in `test/io/docx-session.test.ts` still fails on the current worktree with blocked export for overlapping imported revisions, so it remains an out-of-scope carry-forward rather than fixture proof
-- Word reopen was not executed locally in this environment
-
-## Result
-
-Current A5 conclusion:
-
-- `F11` is proved for run-level insertion and deletion roundtrip plus accept or reject
-- `F12` is proved on the source-backed runtime/export path for paragraph-mark accept or reject
-- `F14` is honestly recorded as preserve-only structural revision evidence
-- the earlier A5 `F12` gap is superseded by the current package-backed proof artifacts under `.tmp/wave-6-redlines/`
-- `tracked-changes-and-review-actions` still remains `repo-landed` overall because broader imported-redline freeform editing can diverge from source-backed replay and block export
-
-Follow-up outside A5-owned paths:
-
-- Wave 7 owns the remaining export block when imported redlined source documents diverge from source-backed replay and also owns broader preserved-part proof beyond the bounded Wave 6 slice.
-
-Shared-plan implication for A9:
-
-- keep `tracked-changes-and-review-actions` at `repo-landed`
-- do not describe general imported-redline freeform editing as baseline-proved from Wave 6