Add Copilot suggestions

Author: Lorna-Kelly

adr/v1.0-adr-shared-workflow-editor.md

@@ -9,7 +9,7 @@ Proposed
 There is a need for a shared editor for the CNCF Workflow Specification that
 can be used consistently by multiple implementations (e.g. Quarkus Flow,
 SonataFlow, ZigFlow, Synapse, Lemline), as different tools provide inconsistent
-authoring and visualisation experiences, leading to duplicated effort and fragmented tooling.
+authoring and visualization experiences, leading to duplicated effort and fragmented tooling.
 
 Today we have:
 
@@ -58,7 +58,7 @@ vendor.
    - Initial maintainers: representatives from at least:
      - CNCF Workflow Spec maintainers
      - Quarkus Flow / SonataFlow
-     - Other interested engine maintainers (e.g. Zigflow / Synapse / Lemline etc.).
+     - Other interested engine maintainers (e.g. ZigFlow / Synapse / Lemline etc.).
 
 - Decision process
 
@@ -90,8 +90,8 @@ vendor.
 ### 1. In Scope
 
 - Read-only visual representation of YAML / JSON workflow definitions
-- Visualise all task types and transitions
-- Fully expanded nested task visualisation
+- Visualize all task types and transitions
+- Fully expanded nested task visualization
 - Indication of basic validation issues
 - Editor available via NPM package
 - A simple demo app showing how to embed the editor as a component
@@ -113,10 +113,11 @@ vendor.
 
 ### 4. Validation
 
-- The editor assumes workflows provided by the backend are valid.
-   - Edge cases to handle: validation discrepancies between the TypeScript SDK and the backend (runtime implementation).
-- If rendering is possible, display warnings as needed.
-- If rendering is not possible, provide clear error feedback to user.
+- The editor performs lightweight client-side schema/structural validation to determine whether the workflow can be rendered.
+- The backend (runtime implementation) remains the source of truth for full specification conformance and advanced validation rules.
+  - Edge cases to handle: validation discrepancies between the TypeScript SDK and the backend (runtime implementation).
+- If structural validation passes and rendering is possible, render the workflow.
+- If structural validation fails and rendering is not possible, do not attempt to render a partial/invalid diagram; provide clear, actionable error feedback to the user instead.
 
 ### 5. Nested Tasks & Layout Strategy