Windows parity: Edge creation needs full native controls, rendering and persistence qualification #729

Current reconciliation - 2026-11-09

The 2026-10-13 scope correction below remains authoritative: an accessibility fragment for drawn edges is NOT required by macOS parity. PR #962, merged at 1aa4a225c3082e2d2daf9ea0d0663448def4051a, fixes same-window Wire recapture and the new-edge Create action. Its accepted normal W1 receipt verifies locked native/semantic endpoints, one correlated APPLIED handoff/always edge, preserved cards and removal of unwired state. That native receipt is source-bound to its recorded earlier inputs, not a newly executed merge-head walkthrough. Wire is included in Windows beta31.

Still open / Partial: all kind/condition/transform/cycle states and conditional enablement, current matching macOS/Windows sheet and edge rendering, and the issue's production-daemon save/reload requirement are not fully qualified by W1. An applied edge, observer read, stub integration or headless persistence test is not the complete native creation/persistence path. Connector hover/all-state and W2-W6 obligations remain separate; no whole visual criterion is checked.

The original report, acceptance criteria and historical evidence below are preserved; the dated scope/progress above supersedes obsolete missing-feature claims.

Is your feature request related to a problem?
Parity row Edge creation sheet (Graph overview and project canvas) in investigation/ui-parity-matrix.md is Partial.

macOS: Kind/condition/transform/cycle controls with conditional validation.

Windows today: The creation sheet with conditional validation exists and addresses the captured project.

Gap: The accessibility provider exposes no edge fragment, so rendering is corroborated only indirectly; native macOS parity evidence is absent.

Describe the solution you'd like
Expose edges in the UIA tree (name, kind, endpoints, invoke), then verify a created edge live.

Describe alternatives you've considered
N/A

Additional context
This is an implementation gap: work remains in the product before the row can be validated. Shared with Edge editing. Parity status and the beta25 Dev Box review are recorded in #719.