@beyondwork/docx-react-component 1.0.0 → 1.0.2

package/docs/plans/waves/completed/wave-11.md

@@ -1,335 +0,0 @@
-# Wave 11 - Bounded-v1 Fleet Readiness On The Shared Workspace
-
-**Commit message**: `Build: fleet-ready bounded v1 on the shared workspace`
-
-## Component promotions
-
-- canonical-document-model: fleet-ready
-- command-and-transaction-runtime: fleet-ready
-- comments-and-anchor-mapping: fleet-ready
-- tracked-changes-and-review-actions: fleet-ready
-- docx-import-and-normalization: fleet-ready
-- docx-export-and-serialization: fleet-ready
-- unsupported-ooxml-preservation: fleet-ready
-- compatibility-and-word-validation: fleet-ready
-- react-editor-ui: fleet-ready
-- railway-test-harness: fleet-ready
-- openxml-sdk-validator-service: fleet-ready
-
-## Scope note
-
-Wave 11 is still the release-oriented closure wave for the bounded v1 surface.
-It does not widen support into tables, compare, legal semantics, or other
-post-v1 checklist work.
-
-Its job is to take the already-landed shared workspace and mounted session path
-and make that bounded v1 slice fleet-ready:
-
-- package and distribution readiness for `WordReviewEditor`
-- host-integration smoke and browser-support proof
-- CI and release gates tied to the current QA bundle
-- Railway demo posture built on the same runtime and shell already used by the
-  harness
-- final docs that stay honest about preserve-only and deferred areas
-
-Wave 11 should extend the current `HarnessWorkspacePage` /
-`HarnessEditorSessionClient` shell and the shipped `src/ui-tailwind/` renderer.
-It must not revive removed inline-CSS prototype surfaces as a parallel release
-path.
-
-## Entry criteria
-
-- Wave 10 remains the controlling bounded-v1 QA gate and must be either closed
-  or explicitly frozen as the proof base for release-readiness work.
-- Shared docs must already describe the mounted workspace truthfully.
-- Release-channel and package-distribution assumptions must be explicit before
-  any demo or browser-support claim is made.
-
-## Promotion conditions
-
-- every promoted component has fresh Wave 11 release-readiness evidence, not
-  only the earlier QA bundle
-- package, install, host-integration, and demo claims are backed by current
-  smoke artifacts
-- CI or release gates reproduce the same regression, validator, and artifact
-  linkage expectations that bounded v1 already requires
-- final docs stay explicit about preserve-only behavior, deferred capability
-  work, and the post-v1 Waves 12 through 18 docx roadmap
-
-## Deliverables
-
-- refreshed Wave 11 plan docs and release-operations notes
-- package and host-integration smoke proof
-- Railway demo smoke tied to the shared workspace
-- browser-support matrix for the bounded v1 slice
-- release-doc audit covering README, public API, compliance, and operations
-  docs
-
-## Deploy environments
-
-- staging: railway-cli (internal Railway validation environment)
-
-## Context7 defaults
-
-- bundle: word-editor-testing
-- query: "fleet-ready packaging, browser support, host integration, Railway demo posture, and release-doc closure for a Word-compatible editor"
-
-## Agent A0: cont-QA
-
-### Role prompts
-
-- docs/agents/wave-cont-qa-role.md
-
-### Executor
-
-- profile: deep-review
-
-### Context7
-
-- bundle: word-editor-testing
-- query: "release-readiness closure, browser support proof, package smoke, and bounded-v1 support-boundary enforcement"
-
-### Prompt
-
-```text
-Primary goal:
-- Refuse closure unless the repo has a fresh, machine-visible fleet-readiness bundle for the bounded v1 surface.
-
-Required context before coding:
-- Read docs/reference/repository-guidance.md.
-- Read docs/research/agent-context-sources.md.
-- Read docs/reference/live-proof-waves.md.
-- Read docs/plans/current-state.md and docs/plans/waves/wave-10.md.
-
-Specific expectations:
-- block closure if release-readiness claims depend only on the earlier qa-proved bundle
-- block closure if browser support, demo posture, or install guidance still overclaim beyond the bounded v1 contract
-- keep Waves 12 through 18 clearly separated as post-v1 docx capability work
-
-File ownership (only touch these paths):
-- docs/plans/waves/reviews/wave-11-cont-qa.md
-```
-
-## Agent A8: Integration Steward
-
-### Role prompts
-
-- docs/agents/wave-integration-role.md
-
-### Executor
-
-- profile: deep-review
-
-### Context7
-
-- bundle: railway-harness
-- query: "reconciling package smoke, demo smoke, release gates, browser matrix, and bounded-v1 support claims"
-
-### Prompt
-
-```text
-Primary goal:
-- Decide whether the bounded v1 editor is honestly fleet-ready without widening the product contract.
-
-Required context before coding:
-- Read docs/reference/repository-guidance.md.
-- Read docs/research/agent-context-sources.md.
-- Read docs/reference/live-proof-waves.md.
-- Read docs/plans/master-plan.md, docs/plans/current-state.md, and docs/plans/waves/wave-11.md.
-
-Specific expectations:
-- block closure if release gates, package smoke, or demo posture are missing a machine-visible proof artifact
-- block closure if the shared workspace and host-integration story diverge
-- block closure if docs still blur bounded v1 versus post-v1 legal-fidelity work
-
-File ownership (only touch these paths):
-- .tmp/main-wave-launcher/integration/wave-11.md
-- .tmp/main-wave-launcher/integration/wave-11.json
-```
-
-## Agent A9: Documentation Steward
-
-### Role prompts
-
-- docs/agents/wave-documentation-role.md
-
-### Executor
-
-- profile: docs-pass
-
-### Context7
-
-- bundle: word-editor-testing
-- query: "release docs, install guidance, browser matrix wording, and bounded-v1 versus post-v1 roadmap framing"
-
-### Prompt
-
-```text
-Primary goal:
-- Close the shared-plan and operator docs around the fleet-ready bounded v1 definition without smuggling in Wave 12+ claims.
-
-Required context before coding:
-- Read docs/reference/repository-guidance.md.
-- Read docs/research/agent-context-sources.md.
-- Read docs/legal-feedback-architecture.md.
-- Read docs/reference/legal-checklist.md.
-- Read docs/plans/master-plan.md, docs/plans/current-state.md, docs/plans/migration.md, and docs/plans/component-cutover-matrix.md.
-- Read the Wave 11 proof notes.
-
-File ownership (only touch these paths):
-- README.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
-- docs/reference/public-api.md
-- docs/reference/ooxml-compliance.md
-- docs/reference/legal-checklist.md
-```
-
-## Agent A1: Packaging And Host Integration
-
-### Executor
-
-- profile: proof-owner
-- retry-policy: sticky
-
-### Context7
-
-- bundle: word-editor-contracts
-- query: "package surface, host integration, install guidance, and component-level smoke for a Word-compatible editor"
-
-### Skills
-
-- role-implementation
-- domain-editor-architecture
-- domain-docx-compatibility
-
-### Components
-
-- canonical-document-model
-- command-and-transaction-runtime
-- docx-import-and-normalization
-- docx-export-and-serialization
-- react-editor-ui
-
-### Exit contract
-
-- completion: authoritative
-- durability: durable
-- proof: integration
-- doc-impact: owned
-
-### Deliverables
-
-- src/api/public-types.ts
-- src/ui/WordReviewEditor.tsx
-- services/react-word-editor/lib/host-integration-smoke.ts
-- docs/plans/waves/reviews/wave-11-package-proof.md
-
-### Proof artifacts
-
-- path: .tmp/wave-11-fleet-ready/package-smoke-report.json | kind: integration-report | required-for: fleet-ready
-- path: .tmp/wave-11-fleet-ready/host-integration-smoke.json | kind: integration-report | required-for: fleet-ready
-
-### Prompt
-
-```text
-Primary goal:
-- Make package and host-integration claims machine-visible for the shared bounded-v1 workspace.
-
-Required context before coding:
-- Read docs/reference/repository-guidance.md.
-- Read docs/research/agent-context-sources.md.
-- Read docs/reference/public-api.md.
-- Read services/react-word-editor/README.md.
-
-Specific expectations:
-- package and host smoke must use the shipped shared workspace, not an older prototype path
-- keep Word-compatibility and preserve-only boundaries explicit in any install or embed guidance
-- do not widen the public component contract beyond the bounded v1 surface
-
-File ownership (only touch these paths):
-- src/api/public-types.ts
-- src/ui/WordReviewEditor.tsx
-- services/react-word-editor/lib/host-integration-smoke.ts
-- docs/plans/waves/reviews/wave-11-package-proof.md
-- .tmp/wave-11-fleet-ready/
-```
-
-## Agent A2: Demo, Browser Support, And Release Gates
-
-### Executor
-
-- profile: implement-fast
-- budget.minutes: 45
-
-### Context7
-
-- bundle: railway-harness
-- query: "Railway demo posture, browser support matrices, release checklists, and shared workspace smoke"
-
-### Skills
-
-- role-implementation
-- role-deploy
-- provider-railway
-
-### Components
-
-- comments-and-anchor-mapping
-- tracked-changes-and-review-actions
-- unsupported-ooxml-preservation
-- railway-test-harness
-- compatibility-and-word-validation
-- react-editor-ui
-- openxml-sdk-validator-service
-
-### Exit contract
-
-- completion: authoritative
-- durability: durable
-- proof: integration
-- doc-impact: owned
-
-### Deliverables
-
-- services/react-word-editor/app/demo/page.tsx
-- services/react-word-editor/components/harness-workspace-page.tsx
-- services/react-word-editor/components/harness-editor-session-client.tsx
-- docs/plans/operations/wave-11-release-checklist.md
-- docs/plans/waves/reviews/wave-11-demo-proof.md
-
-### Proof artifacts
-
-- path: .tmp/wave-11-fleet-ready/demo-route-smoke.json | kind: integration-report | required-for: fleet-ready
-- path: .tmp/wave-11-fleet-ready/browser-support-matrix.json | kind: manifest | required-for: fleet-ready
-- path: .tmp/wave-11-fleet-ready/release-doc-audit.md | kind: proof-note | required-for: fleet-ready
-
-### Prompt
-
-```text
-Primary goal:
-- Turn the shared workspace into an honest fleet-ready demo and release surface for the bounded v1 contract.
-
-Required context before coding:
-- Read docs/reference/repository-guidance.md.
-- Read docs/research/agent-context-sources.md.
-- Read DESIGN.md.
-- Read services/react-word-editor/README.md.
-
-Specific expectations:
-- demo posture must stay explicitly non-production where proof remains bounded
-- browser support claims must be artifact-backed and limited to the real shared workspace
-- release gates should reproduce the same regression and validator expectations as Wave 10
-
-File ownership (only touch these paths):
-- services/react-word-editor/app/demo/page.tsx
-- services/react-word-editor/components/harness-workspace-page.tsx
-- services/react-word-editor/components/harness-editor-session-client.tsx
-- docs/plans/operations/wave-11-release-checklist.md
-- docs/plans/waves/reviews/wave-11-demo-proof.md
-- .tmp/wave-11-fleet-ready/
-```