fix: black fascia, FAT progress restore, and persistent multi-RCB selection

[masarray]

Summary

• replace the runtime IED fascia transcription with Assets/black-fascia-ied.svg
• keep three high-visibility runtime LEDs aligned with SVG metadata intent (LED1, LED2, LED3)
• Engineering LEDs follow IsMonitoring: LIVE = bright green, first Stop = red even if MMS association is retained
• FAT cards keep the equivalent IsLiveConnected state
• fix Engineering -> FAT local progress continuation for the same SCL content
• preserve fail-closed evidence restoration using IEC 61850 point configuration matching
• fix Legacy SAS multi-RCB checkbox selection being lost when the WPF DataGrid virtualizes/recycles rows during scrolling

FAT progress restore

• SCL continuation can match by normalized source-content SHA-256 when filename/staged source identity changes
• compatible ARSAS-FAT-SCL-1.x snapshots can restore across non-semantic schema revisions
• exact TestPointId remains first priority
• fallback continuation requires a unique IEC/configuration match
• workbook/package source matching remains strict
• ambiguous candidates are not restored

RCB selection virtualization

• RcbExportRow.IsSelected remains the durable selection authority
• virtualization-generated Checked/Unchecked events are prevented from reaching the stale single-select XAML handlers
• click, checkbox, Space and Shift-range behavior stays on the existing P1 multi-select path
• virtualization remains enabled; no visual checkbox/container state is persisted

Exact combined candidate

Head: 7508d303a96baa947e17a16d2f319414e79e8042

Validation:

• Build ARSAS #2187 — SUCCESS
• full regression suite — SUCCESS
• portable publish — SUCCESS
• portable smoke test — SUCCESS
• Validate IO List Testing #1049 — SUCCESS
• Validate SV evidence bundles #1273 — SUCCESS

Diff audit against main base c424314ab1b1e6c6003a2b4e93a07d78c9d570d0: 10 files only; no ARIEC engine pin, protocol stack, GOOSE/SMV runtime, command/control backend, release metadata, or unrelated UX files changed.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 834419def8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve continuation after repeated source renames

When identical SCL bytes are first opened as file A and then reopened as file B, the cross-identity restore leaves A's snapshot in place while persistence creates a new snapshot for B. Reopening the same bytes under a third filename makes this scan find both snapshots and return null, so FAT opens a fresh workspace and fails to restore the operator's progress. Migrate or retire the consumed snapshot, or recognize snapshots belonging to the same continuation lineage rather than treating the duplicates created by this flow as ambiguous.

Useful? React with 👍 / 👎.