Fix RCB DataSet evidence merge and logical-scope display

[masarray]

Problem

The RCB Export Filter could show No DataSet when the DataSet binding was actually unresolved or when a newer live availability snapshot had stronger evidence than the stale discovery model. Duplicate short RCB names across Logical Devices also made different RCB instances look identical.

Fix

• Add a central RCB export evidence policy: unknown evidence stays unknown.
• Make a successful live DatSet read authoritative including an explicitly empty binding, so stale discovery cannot resurrect an old DataSet reference.
• Use live availability DataSet references ahead of stale discovery references when live evidence is positive.
• Distinguish source SCL datSet absent, broken/unresolved reference, empty DataSet, and populated DataSet.
• Detect source-SCL vs live-IED binding conflicts in all directions (different refs, source bound/live none, source none/live bound) and block export on verified conflict.
• Do not create a false conflict when the live DatSet read failed or was not attempted.
• Show logical scope below the short RCB name so duplicate urcbA01 / brcbA01 instances across Logical Devices are unambiguous.
• Add E016-style synthetic regression tests without publishing the real CID/ICD fixture.

Engine dependency

masarray/ARIEC61850#53 is merged. This branch is pinned to engine main commit 239019e9a66513807d88354f5959ff7dbf280868, which requires positive live evidence before classifying NoDataSet and hardens dynamic RCB slot selection.

Validation

• ARIEC61850 CI passed before engine merge.
• ARSAS Build #918 passed: source/invariant checks, restore, build, regression tests, portable publish, portable smoke test and artifact upload.
• Legacy SAS RCB export guard Make GOOSE values readable and keep the workspace lightweight #41 passed.
• Windows installer validation Turn MMS Client and Smart Reporting into bilingual practical tutorials #118 passed.
• IO List validation Add adoption onboarding and field-proof evidence #104 passed.
• SV evidence validation Fix IO FAT live binding and relay fascia #137 passed.
• Automated review P1 about the stale engine lock was addressed by pinning merged engine PR Showcase Smart Reporting as a core ARSAS capability #53; the review thread is resolved.

Safety invariant

Missing/unreadable evidence must never be presented as positive proof that a DataSet does not exist.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 12063be1fd

ℹ️ 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".