Smart Discovery: DataSet-backed LN schema closure

[masarray]

Engine workstream for ARSAS #495. Keep frozen GetNameList budget; select additional ST/MX LN type probes from wire-confirmed DataSet directory members, deduplicate attempted roots, and permit typed hierarchy to materialize LN members not present before the name-list page cap. Same association and bounded invoke window, no cyclic process polling. Draft: CI and parity test gate before pin/merge.

[masarray]

P10 integration / locked lineage

Engine PR #161 exact head 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1 is now integrated by verified non-force fast-forward into this branch feat/495-dataset-type-closure from 8b0c0f7e695b016834e40a6f068994dcc945cb1a. No main merge. No 97-commit regression/rebase onto old main. Historical checkpoints:

• checkpoint/p10-premerge-engine-discovery-8b0c0f7e
• checkpoint/p10-verified-engine-00ad2819
  Consumer ARSAS PR #513 was likewise fast-forwarded to its PR #512 staging parent. ARSAS exact engine pin is 00ad2819.... Consumer exact-head Windows CI #38097883009 passed engine P10 identity/canonical exporter tests, ARSAS regression and portable smoke; engine PR P10: evidence-driven IED/LD identity and lossless SCL normalization #160 remains a distinct main-based candidate not to be swapped in. Physical GE BCU Edition1 round-trip remains unverified; R10 mainline guard intentionally still blocks release. No network/control/RCB path changed by this integration.

[masarray]

Engine P10 read-only cross-repo audit — 2026-10-11

Confirmed engine staging head 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1, both checkpoint/p10-* refs at documented pre/post SHAs, and direct consumer pin to this exact commit on ARSAS 424a108d654a389429151a925ce6105c40bfa3cc. Engine main e5deed1d8aa11d97991695c6e390baafea7ab797 is an ancestor (staging ahead 100, behind 0). PR #160 main-based alternate remains unmerged and must not replace PR #161 lineage. Reviewed trusted domain matcher + GE F650 canonical exporter tests; they support exact domain-to-LDevice mapping with fail-closed ambiguity, but are synthetic, not physical GE round-trip proof.

Cross-repo CI audit: P10 consumer Build ARSAS #38097883009 SUCCESS. Post-FF consumer mainline readiness fails due to stale allowed-code-trial list (P6.1/P6.2 only), whereas interoperability guard already recognizes P10. Maintain fail-closed mainline R10 physical gate while correcting staged CI allowlist in an isolated reconciliation branch; do not run redundant builds. No physical BCU_GE.iid endpoint check done here, no engine code changes, no main merges or releases. Full detailed audit recorded in ARSAS PR #512.

[masarray]

Engine pin unchanged during ARSAS P10.1/P10.2 reconciliation

ARSAS draft PR #514 on integration head 2369c286da6d14dda2470a2854daf2d46d588dfe reconciles 37 ARSAS main-only commits into the exact staged P10 ancestry (true two-parent merge; no force/reset). ARIEC engine remains exactly pinned to 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1, with no engine source mutation or mainline engine merge; ARIEC #160 remains unauthorized as a substitute. ARSAS CI resolver accepts this pin only through exact guarded P10 code-trial ancestry, retaining historical physical SCL evidence separately; unqualified main/release remains blocked. Full canonical Windows CI is still validating this draft candidate, and GE physical test is not done.

[masarray]

P10.1/P10.2 consumer staging reconciliation done (engine unchanged)

ARSAS PR #514 merged by verified non-force fast-forward into ARSAS PR #512 staging at 2369c286da6d14dda2470a2854daf2d46d588dfe. Exact head passed 16/16 integration workflows before promotion, including engine P10 identity/canonical SCL regression and Windows portable single EXE. Checkpoint checkpoint/p10-2-reconciled-ci-2369c286 in ARSAS. Engine pin remains 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1; this engine staging PR #157 and engine main unchanged. ARSAS main unchanged, no physical GE P10 acceptance or release. Final CI and portable artifact.

[masarray]

Engine pin audited after consumer P10.4 field evidence tooling

ARSAS staging PR #512 advanced via non-force FF to 280f294c5809954636cad593e8a84d60110ad197; PR #515 merged; checkpoint checkpoint/p10-4-ge-structural-evidence-280f294c. Consumer's immutable engine lock remains exactly 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1; engine staging and main unchanged. This addition is offline SCL field evidence tooling only, not a live MMS/engine change, and P10.4 real GE physical qualification stays PENDING. P10.4 candidate PR CI 12/12 green.

[masarray]

P10.5 consumer correction / physical report evidence — engine pinned unchanged

Consumer ARSAS PR #516 merged via 11/11 exact-head CI success and non-force fast-forward staging at 6f717890849e3e33c7e107440c60dbb351f55fc2; new checkpoint checkpoint/p10-5-unique-static-coverage-6f717890. Field diagnostic on GE F650 same-PC simulator shows 6/6 RCB traffic and 67 unique points but 166 planned binding incidences across overlapping BRCB+URCB. Consumer P10.5 corrects unique coverage and GUI exact LN display without changing IEC runtime or this engine lock 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1. Separate ARIEC Issue #162 tracks bounded semantic completion beyond 64 NamedVariable pages; original IID + physical BRCB continuity remain pending. No main merge, R10 physical approval, or public release.

[masarray]

P10.6 consumer-only trusted IID identity fix has landed on ARSAS staging, not main. See ARSAS PR #517 and portable Windows build #38111200018. Root capture demonstrates exact 7-row Discovery/Open SCL semantic fingerprints differ only in provisional IED_192_16_1_33 versus original engineering BCUGE; all six DataSet rows exactly identical; normalized fingerprint 439d4dc0507019533b154ed68f7f4007f39f6be92b5cd3f413ff3b84f619727e. ARSAS now rechecks SHA256-pinned prior successfully connected BCU_GE.iid and full MMS topology on standalone IP Discovery. 12/12 exact-head CI success; guarded FF consumer staging a883510218c62ac02096de37e831feede389f4a1, checkpoint checkpoint/p10-6-trusted-identity-a8835102. ARIEC engine SHA remains exactly 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1, untouched; no main merge, public release, or new physical R10 qualification. Engine NameList bounded completeness remains Issue #162; BRCB BufOvfl findings remain unsuppressed.

[masarray]

P10.6 simulator milestone is now permanently pinned on ARSAS as checkpoint/p10-6-field-verified-bcuge-parity-a8835102, with milestone evidence #518. 2 independent user reports: BCUGE engineering-SCL identity matches IP Discovery, 7/7 exact static semantic fingerprint 439d4dc0..., 8 datasets / 124 members, 67 points, 6 RCBs report traffic, no cyclic polling. ARIEC pin remains exact 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1 and engine main unchanged. ARSAS draft PR #519 improves observational BRCB SqNum/EntryID/GI/BufOvfl evidence only; no ARIEC code or wire behavior changes. Engine bounded NameList issue #162, BRCB event continuity and physical R10 qualification remain open; release/main blocked.

[masarray]

Consumer P10.6 milestone & P10.7 observed BRCB triage checkpoint

ARSAS field milestone #518 locks exact consumer P10.6 baseline a883510218c62ac02096de37e831feede389f4a1 with checkpoint/p10-6-field-verified-bcuge-parity-a8835102. Both independent GE simulator ingresses yield BCUGE, high-confidence IID match, fingerprint 439d4dc0..., 67 unique static values, six 6/6 report streams, no cyclic MMS. Separate ARSAS PR #519 P10.7 merged to staging 415d1db74c0f69637063601da037edf78142cb89 after 10/10 exact-head CI; checkpoint checkpoint/p10-7-brcb-observability-415d1db7. Only consumer read-only diagnostic/10 tests changed: fail-closed same-frame SqNum, GI, BufOvfl and verified opaque EntryID correlation, no suppression or wire behavior change. Engine SHA and lock 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1 unchanged; ARIEC main unchanged; physical R10 and full MMS 64-page closure still pending.

[masarray]

P10.8A ARSAS-only bounded BRCB follow-up observation milestone completed in ARSAS PR #521 and Issue #520: stage SHA a7f4edbf5cb972eacb9baaf0c25e4475ee5f10c9 (10/10 exact-head CI green, portable Windows build #38118437424), permanent checkpoint checkpoint/p10-8a-post-anomaly-followup-a7f4edbf. Operator same-slot GE F650 GW BRCB report shows 13 findings/10 SqNum discontinuities/3 BufOvfl across Open SCL vs IP Discovery; new per-RCB O(1) post-anomaly frame/time evidence does NOT suppress warnings or qualify SOE event losslessness. No ARIEC engine code or lock changes: pinned engine still 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1. No ARIEC/ARSAS main, R10 physical approval or public release. Maintain #162 incomplete GetNameList and P10.6 milestone #518 unchanged.

[masarray]

ARSAS P10.8B PR #522 MERGED to consumer staging only after exact-head 10/10 green Windows CI; head 3c58a476e25289a1a59f55992dbf70c81f73fffd, checkpoint checkpoint/p10-8b-bounded-brcb-chronology-3c58a476. Consumer-only BRCB diagnostic fixed ring first32/last8 frame metadata (GI, SqNum, BufOvfl, EntryID equality relation—no raw cursor/payload; missing middle count); immutable snapshots, nine regression tests, no wire/control changes. Portable #11695130540. Original simulator identity/static parity milestone #518 preserved. ARIEC engine SHA remains 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1 exactly, no engine/main release/physical R10 qualification. Real BRCB continuity fault requires packet-order evidence per ARSAS Issue #520; NameList cap engine #162 remains.

[masarray]

Canonical handoff for the next ARSAS/ARIEC61850 thread is now ARSAS Issue #525, verified against the latest staged P10.8D exact SHA ce73df3a47e163416c232b083eba1e4915f33e17 (16/16 post-FF staging CI SUCCESS), not the older P10.8A/P10.6 branch head. ARSAS staging PR #512 remains draft and ARSAS main untouched. Exact consumer lock and this engine staged HEAD both remain 00ad2819b99ffe6b3f885e59aa24a6afb2b4d8e1, engine main untouched; PR #157 remains draft. P10.8D is diagnostic-only exact BRCB-slot offline comparison; no engine source, report activation, control, polling, GOOSE or R10 physical qualification changes. Milestone #518 BCUGE identity/static parity, BRCB issue #520, and MMS NameList #162 remain relevant. Follow #525 before coding, no old-base regression or public release.