[SUPERSEDED] Mixed SCL/onboarding trial — replaced by protocol-only PR #310

[masarray]

Superseded by Draft PR #310 (trial/scl-golden-wire-v1636).

This PR mixed trusted-SCL protocol work with Smart IED onboarding/UI changes. It is closed without merge and retained only as migration history.

Protocol authority now lives in PR #310 from exact ARSAS 1.6.36 staging baseline 384e2fe67b871a329b07ce5db2aa2916cca5c054, pinned to exact green ARIEC e41def0a2676efb8a143905798155f6bccc6f047.

[masarray]

Field regression found and fixed — worker-thread WPF access

Physical field report on AA1E1F06R4 proved TCP/COTP/ACSE/MMS association was healthy (MmsInitiated, TransportReady=True, MmsReady=True, BalancedApTitle accepted), but the runtime then reported The calling thread cannot access this object because a different thread owns it.

Root cause was introduced by the new smart onboarding behavior: Device_PropertyChanged can be raised from the MMS/runtime worker after ConfigureAwait(false), and it directly called RefreshConnectAll(), which mutates WPF Button.Visibility, ToolTip, and TextBlock.Text. The exception propagated through device.IsConnected = true, causing the successful MMS association to be misclassified as a connection failure.

Fix:

• all collection/model-driven smart onboarding refreshes now marshal through MainWindow.Dispatcher;
• visual refresh methods assert dispatcher ownership;
• regression guard locks Device_PropertyChanged -> DispatchUi(RefreshConnectAll) and dispatcher use.

Fix commits: 2ac9f58892a30bfdae5949b606bebafed9633d98, regression guard head b226b95e4d42a83a47c656b7b098333f63d5dedc.

Important additional field finding: the normal Open-SCL/Play flow in this report still logged Fast reconnect using saved model, so it did not yet exercise the SCL-assisted Step 5 online path. That routing remains a separate integration item after this crash regression is requalified.