Repository navigation
Conversation
D9 source/test unique-delta audit — KEEP OPEN pending SG/SE presentation authorityHistoric HEAD All original four paths inspected: Semantic delta not presumed equivalent: original edit-only SGCB explicitly displays "No active-group [SG]", whereas current RC test expects "No model-proven SG or SCL SE" and presentation includes provenance-qualified SCL SE fallback; source/read-plan have evolved. Need actual accepted GUI owner decision on distinction between verified active SG, SCL static SE, and live MMS read authority, plus regression parity. No forced old behavior/revert, no closure, no branch deletion; do not treat SCL SE as an observed active group or authorize Write. |
|
D27 PR consolidation — closed as already included in integrated RC, not recorded as a direct PR merge. Exact ancestry proof: PR HEAD Closing this historical integration lane reduces duplicate open PRs without merging its old base into current RC. Physical IEC 61850 R7/R10 testing, open field issues, trial engine qualification, protected main and stable release retain their independent acceptance gates. |
M2.14 — fix real SG parameter values, not a cosmetic placeholder
Stack #560 → #563 (Thread A) → #567 (A/B validated) → #568 (read-only SGCB/GoCB validated) → this PR. Owns Browser presentation and explicit SG read plan only.
Root cause
The SGCB detail pane grouped all SG + SE leaves into a synthetic DO root and set its ValueReference only for a single-attribute DO. On a real relay with multiple SG/SE attribute declarations this results in an unbound Not read root even when exact SG leaf observations exist. It also reads SE edit-group fields unnecessarily when choosing active SG inspection.
Fix
ATCC1.BndWid.setMag [SG]linked to...$SG$BndWid$setMag$f, andf [SG]on expansion.Acceptance
Require exact-SHA Windows compile, full ARSAS regression, pinned engine/native CTest, artifact verification. A screenshot from a physically connected ZIV AVR is still required to prove what SG attributes the device actually permits read-only access to. Other CF unit issues will be handled under Thread A's authority rather than a competing unit decoder.