[masarray]

Exact ancestry, no promotion

Consumer integration trial stacked on #632 (exact parent 1d2ccfd6d3928d33fba2f68966c0f6eae3410a6c) and original P0-A/B/C lineage. Engine P0-G #182 tested ded5036029706db1a752bb045d1fbc43b67fe9c6 at https://github.com/masarray/ARIEC61850/actions/runs/39368865409 (Windows success). The previous consumer P0-C lock ba21d882f67de22c10d3155b449aac77aa8b4899 remains explicitly embedded as immutable parent trial evidence.

Implementation

• Advance engines/ARIEC61850.lock.json to EXACT engine SHA fix: expose complete static DataSet inventory and diagnostics #182 (code trial only), preserve unchanged field-proven and previous P0-A/B/C trial signatures, no release/mainline switch.
• New scripts/test-p0-g-scl-edition-trial.ps1 requires the historical P0-C lineage to pass recursively at its exact SHA; validates PR fix: expose complete static DataSet inventory and diagnostics #182, exact engine CI run and fail-closed flags (unsupported SCL edition never silently downgraded, edition ordinals unchanged, no vendor branching, writes, polling or physical promotion).
• Extend existing scripts/resolve-ariec-lock.ps1 accepted-trial predicate with explicit P0-G path. Existing historical accepted paths remain unchanged.

What is and isn't supported

The engine recognizes SCL Edition 1, 2, 2.1, 2.2 root markers with synthetic positive/negative tests; this is NOT certification of the full Edition 2.2 SCL schema, MMS behavior, or vendor IED physical interoperability. Original live field capture predates this engine. ARSAS Windows build/regression/R7/installer must pass at this new exact head before calling code green.

No control, RCB reservation/GI, cyclic MMS process polling, simulator traffic or release promotion. Draft only.

[masarray]

D28 archival on maintainer direction: older experimental IEC 61850 branch superseded by the latest successful, operator-accepted baseline. The operator will not recapture evidence for this historical trial. Closing as NOT MERGED, without modifying runtime or stable release. Historical HEAD e3962b6fefbd699c2681c6aff0f2d13dd417dff2 and its distinct code/tests remain preserved in GitHub; those unmerged changes are not falsely claimed as implemented. This retirement removes a stale integration proposal, not an established safety limitation or protocol fact. No follow-up capture required for PR cleanup.