Golden-wire SCL online path on field-proven ARIEC baseline

[masarray]

Canonical purpose

This is the single ARIEC field-trial lane for reproducing the observed trusted-SCL IEC 61850 wire behavior on top of the exact field-proven ARSAS engine baseline.

Base authority: baseline/arsas-field-proven-11ab230 @ 11ab2304482600c19ba979f4fc9021ddb46b9af9.

Do not merge unrelated current-main/canonical-runtime work into this PR. Keep it Draft until exact-head CI and physical IED evidence pass.

Golden wire contract

The acceptance reference is the captured IEDScout Open SCL -> Connect -> Reporting sequence. Manual delays between reporting actions are not protocol-performance evidence.

Trusted-SCL primary path:

1. one TCP/COTP/ACSE/MMS association;
2. capture-aligned calling association identity (TSEL=0000, SSEL=0001, PSEL=00000001, AP-title 1.1.1.999, AE qualifier 23), while called-side identity remains SCL-derived;
3. exactly Domain/VMD GetNameList for online domain reconciliation;
4. bounded FC-root initial Reads derived from trusted SCL, max 10 references per Read, sequential / one outstanding;
5. keep the same association alive;
6. no implicit full discovery before explicit Re-scan.

Forbidden on the trusted-SCL primary connect path before explicit Re-scan:

• GVAA / full NamedVariable discovery;
• DataSet directory browsing / GetNamedVariableListAttributes;
• dynamic DataSet Define/Delete;
• automatic control or arbitrary MMS writes;
• hidden full-discovery fallback.

Static reporting contract

Static DataSet membership and RCB bindings come from trusted SCL authority.

Primary BRCB activation:
Read RCB -> RptEna=true -> Readback -> Readback.

Primary URCB activation:
Read RCB -> Resv=true -> RptEna=true -> Readback -> Readback.

• no proactive BRCB ResvTms on the primary path;
• ResvTms is compatibility fallback only after an explicit direct-enable rejection;
• GI is OFF by default and is never injected implicitly;
• no dynamic DataSet mutation in the trusted static lane.

Preserved field-proven behavior

The baseline retains the exact semantic/static-DataSet report projection and reporting/control ancestry from 11ab230.... The SCL golden-wire work is additive to that baseline; unrelated current-main progress is intentionally excluded.

Current exact identity

• Protocol/test behavior through: ca918f4450b4800ef2346f54a80e4c1865137a1c
• Current PR HEAD: e41def0a2676efb8a143905798155f6bccc6f047
• e41def0... is CI-only: it moves the full-solution convergence build to Windows and guarantees diagnostics are recorded even on an early failure. It does not alter MMS/SCL/report behavior.

The previous CI #7 failed before build/test because Ubuntu restore rejected Windows-targeted projects with NETSDK1100; that was a workflow-platform defect, not a protocol test failure. The current exact-head CI must be green before ARSAS is repinned.

Physical interoperability is not claimed until relay PCAP/value evidence is reviewed.

Merge gate

Remain Draft + unmerged until:

• exact-head ARIEC CI passes;
• ARSAS protocol-only candidate pins this exact engine SHA and passes its exact-head Windows build/tests;
• physical IED PCAP matches the golden sequence with valid values/reporting;
• no hidden discovery or unnecessary association restart is observed.