[masarray]

Why

Build directly on merged native naming/FCDA inspector #179 (main ce643e81cd7640ed2b694c0914282177f871a9fa). ARIEC61850 is semantic comparison input; ARSAS Explorer is visual/workflow reference. The implementation stays in the existing C++/Qt/QML Workbench, with no second protocol stack.

Native user workflow delivered

• Select a canonical DA through DataSets' ordered FCDA view; inspect actual current value/read state/q/t/source from MmsLiveTreeModel.
• Use Data Model › to jump to the existing Data Model panel while keeping the canonical DA selected, where the existing explicit bounded MMS Read action already lives.
• Use Watch DA to add only that selected DA to the existing independent per-IED 256-entry Global Data list, not the entire DataSet.
• Discard selected DA and lazy member expansions on source/context replacement, including same-name cross-IED contexts.
• Tight source-level Browser convergence regression enforces parent signal wiring, lifecycle reset, and no implicit Read/polling; unchanged q/t/measurement/report decoding.

Gates

• Exact-head IED Simulator Qt (QML, Browser convergence, large-model, visual evidence), SCL-Assisted Workbench CI, Product Naming Guard, reviews, and post-merge main checks.
• This PR does not claim real physical IED interoperability or full GUI visual parity; those need separate Windows and hardware acceptance.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-15T09:40:11.372627Z	cb7b7fb	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.