[masarray]

Controlled ARIEC61850 consolidation — integration candidate, NOT release

This is the single reviewed consolidation lane for repository audit issue #144. Do not merge merely because the tree is conflict-free or CI green. Preserve ARSAS FAT evidence and immutable engine lock.

Pinned source commits / ancestry

• IEC 61850 Ed2: resolve prefixed LN class for Boolean DPC position controls #189 IEC Ed2 prefixed-LN typed DPC control: 24aae4698026f3a5cf7a35225c5d8000018af3e4 (179 commits ahead of legacy main).
• P0 SIEBCU: negotiated-window RCB enrichment without losing exact MMS evidence #186 negotiated outstanding-window bounded RCB enrichment: d095b3ac9bdf6687f7ab9407f7e28eca9c168c94 (3 distinct source/test files).
• P0 SBO Enhanced: per-invoke TPKT send / confirmed response / decode timing (no safety change) #187 SBOw stage timing: 4ed76ccd11b763dcd847395f6ef45273db3f5c9c (4 distinct source/test files).
• P0-G: standards-gated SCL Edition 2.2 (2007/C/5) identity without silent downgrade #182 Edition 2.2 SCL identity: ded5036029706db1a752bb045d1fbc43b67fe9c6 (3 distinct SCL source/test files; old workflow change intentionally replaced).
• M2.14 COMTRADE: include exact-directory same-basename RIO sidecars in downloads #170 exact-directory COMTRADE RIO sidecar: aecaa3c73519d53e86223c8d1226f3ffd99a6743 (2 unique source/test paths, verified same blobs as Consolidated engine #190: 7 source PRs • 1262 Windows tests green (DRAFT) #190 ancestor).
• Integration HEAD now: 5077d6ac1e8394ec789f90b3b33cad3260ab0241 (inherits verified first integration commit ef17070f3c5aa333c1789ada52296959703d9f5d, source M2.14 COMTRADE: include exact-directory same-basename RIO sidecars in downloads #170 and merged CI infrastructure CI: validate synthetic PR merge on every stacked base (workflow-only) #191 at 3d21238d0b62f24faecd5948a4ee238c82b35966 as explicit parents). No force push; no production code merge.

Why this composition is safe to test, not yet to ship

For each of the 10 source/test paths from the three siblings, compared exact Git blob IDs at its original merge-base to #189: all unchanged on #189 (zero overlapping modifications). Installed sibling file blobs verbatim into #189's base tree. Original eleven-path integration plus two COMTRADE RIO source/test paths (#170); the CI infrastructure workflow has since been squash-merged independently as #191, and this branch now adopts the exact same workflow blob:

• pull_request on any target branch;
• read-only actions/checkout at event SHA, default PR synthetic merge commit, not GITHUB_HEAD_REF/branch checkout;
• existing full Windows source check, restore, Release build, engine tests, NuGet test artifact and logs retained.

Mandatory qualification gates before main merge

• Windows synthetic-merge CI passed for HEAD 5077d6ac, run #39771920122: checked out refs/pull/190/merge (merge tree 506620c over main 3d21238); source/provenance gate, restore, Release build, 1,231/1,231 tests passed, NuGet test build, artifacts and diagnostics upload; 0 build warnings/errors. Historical integration HEAD ef17070f separately passed run #39770688304, 1,227/1,227 tests. Mainline workflow-only CI: validate synthetic PR merge on every stacked base (workflow-only) #191 separately passed run #39771262606, 993/993.
• Review remaining divergent branch content (especially P10: evidence-driven IED/LD identity and lossless SCL normalization #160 identity exporter, Discovery P7.7: bounded DataSet-first type closure beyond GetNameList limit #155 vs Smart Discovery: DataSet-backed LN schema closure #157, P0-A: evidence-ranked generic live IED identity without suffix truncation #175 identity alternative, P3: add sustained Sampled Values stream analysis #130 SV analyzer, fix(reporting): expose source-neutral configured static activation #137/discovery: preserve exact primary type semantics in live SCL #138 reporting, P3 #144: fail-closed configured-static JIT readback proof #146/P4 #144: targeted RCB hot path and association-scoped static DataSet evidence #147/P5 #144: event-driven persistent report receive path #149–P6.1 #144: targeted live RCB reconciliation without full discovery #151 and Bump the test-dependencies group with 3 updates #171 dependencies); none are silently discarded. Explicit accepted/rejected status and evidence required.
• Deterministic tests for no fabricated MMS scalar/q/t, bounded RCB discovery, typed prefixed LN control, protected SBOw ordering, no unsafe retry/overlap, and Ed2.2 version gating.
• Update ARSAS consumer trial only via explicit immutable engine SHA and provenance lock; verify complete combined Windows CI. Preserve ARSAS #679/#671 current 9c7cb40364023a7b217e5ec31ab3105ba90142eb until separately approved. #666 timing trial uses P0 SBO Enhanced: per-invoke TPKT send / confirmed response / decode timing (no safety change) #187 separately; not promoted here.
• Physical IEC 61850 vendor tests / FAT authorization for operational behavior; software CI alone is insufficient. Open engine P0 investigation: consecutive BCUGE Operate stalls and unbounded cancellation cleanup #172, P10.6: complete GE F650 MMS NameList beyond 64-page smart-discovery budget without latency regression #162 and P8 C264: schema-verified structured FCD report projection and rejection evidence #159 remain active.
• Only after acceptance: merge reviewed integration once, retire incorporated ancestors with exact SHA links and close outstanding CI housekeeping. Never bulk merge source branches or delete baseline/checkpoint refs.

Provenance and public API boundaries

No raw customer SCL/captures or private diagnostics added. No engine pin change. main now contains workflow-only infrastructure squash PR #191 at 3d21238d0b62f24faecd5948a4ee238c82b35966; engine source remains at the original mainline baseline. PR is draft intentionally; reviewer should confirm post-merge test and readiness before production.

2026-10-22 consolidation increment — #130 SV + #138 typed semantics

Current integration SHA: 14b19d30466fd296ad1e6d0bddcdd574992bc464, fast-forwarded from 5077d6ac1e8394ec789f90b3b33cad3260ab0241 (no rewrite). Additional preserved source parents:

• P3: add sustained Sampled Values stream analysis #130 66a325c6414ce8c007a0a758ee33e8b2d92e7bb3: 12 original new files (SV sustained stream analysis, engineering-window/SCL-bound measurements, documentation, deterministic tests), no overlapping destination paths.
• discovery: preserve exact primary type semantics in live SCL #138 5d8c9959f638290a7aaf45988ef45ed823639d2a: four source/test blobs exact-copy from a merge-base unchanged destination; the fifth shared Iec61850StandardModelRegistry.cs already had the exact same blob hash. No semantic overwrite.

All original functional changes from #189/#186/#187/#182/#170 remain ancestry. Prior green 1,231/1,231 CI on 5077d6ac does not qualify this new SHA; require a new green exact merged-tree CI. The new SV engine analysis is not itself proof of physical SMV/relay behavior. Remaining divergent #137/#160/#155/#175/old P0–P6 stack and #171 dependency updates have not been silently imported. Engine release and ARSAS lock updates are explicitly blocked pending separate acceptance.

Exact post-consolidation Windows gate — PASS

• Head 14b19d30466fd296ad1e6d0bddcdd574992bc464 checked out as PR Consolidated engine #190: 7 source PRs • 1262 Windows tests green (DRAFT) #190 synthetic merge 49ae033 against main 3d21238d0b62f24faecd5948a4ee238c82b35966.
• CI run #39778971482: SUCCESS, source/provenance, restore, Release build, 1,262/1,262 tests passed, 0 warnings/0 build errors, test build package and diagnostic artifacts uploaded.
• Supersedes the previous 1,231-test CI for commit 5077d6ac. Physical FAT, ARSAS combined immutable-lock build and remaining divergent feature reconciliation not satisfied by software gate. Keep PR DRAFT and main engine source unchanged.

[masarray]

Staging-only acceptance, 2026-10-22. Branch staging was created from main SHA 3d21238d0b62f24faecd5948a4ee238c82b35966. This exact candidate HEAD 14b19d30466fd296ad1e6d0bddcdd574992bc464 passed synthetic-merge CI #39778971482 (1,262/1,262, zero build warning/error). Because staging and tested main base have identical commits, it is eligible for staging integration only. No production/main release approval, ARSAS engine pin change, physical FAT or control field qualification is implied. The subsequent staging -> main PR MUST remain DRAFT until independent review and combined qualification. All original source PRs are preserved in ancestry.

[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-22T12:53:53.848617Z	14b19d3	Draft marked ready

ℹ️ 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.