FAT: align context-aware signal presentation with Engineering

[masarray]

Context-aware FAT signal identity hotfix

This hotfix starts from current main after ARSAS v1.6.34 and fixes operator-facing signal-name drift between Engineering and FAT without changing live acquisition or protocol identity.

Problem

• Engineering can show phase-aware names such as A PhsA, A PhsB, A PhsC, while FAT could fall back to A / A / A when its report/event alias lost DA phase context.
• Generic Pos rows were ambiguous across logical-node owners such as XCBR and CSWI.

Fix

• strengthen the shared ARSAS-owned IoSignalDisplayName authority with LN/DO/DA context
• recover FAT phase context from the richest source reference and DataAttribute
• qualify switching/control logical-node owners so Pos becomes XCBR Pos / CSWI Pos
• wire the native FAT report to the same point-aware semantic formatter used by the FAT workspace
• keep canonical IEC references unchanged for live binding, FCDA/report identity, evidence and persistence

Regression coverage

• A PhsA/B/C
• PhV PhsA
• XCBR Pos / CSWI Pos
• no duplicated semantic suffix/prefix
• Engineering and FAT converge on IoSignalDisplayName
• FAT report uses the same point-aware formatter
• FAT live-value lookup remains IEC-reference-based, not display-name-based

Safety boundaries

• no ARIEC61850 pin change
• no RCB/COMTRADE/SCL-export changes
• no command Sync/Interlock changes
• no CSWI.Pos command-freshness changes
• no relay fascia changes
• no acquisition polling/reporting change

Keep Draft until exact-head Build + IO + SV are green and a relay-test artifact is produced.

[masarray]

Closing as superseded. Context-aware signal presentation was already consolidated into the accepted mainline through #269 and subsequently preserved by #274. Keeping this old draft open would create a second outdated implementation path and unnecessary regression risk.