[masarray]

Draft / isolated engine trial stacked on the current consumer-pinned engine 51c2eef (engine PR #173). First commit intentionally installs failing behavioral regressions. Next implementation must preserve raw live domains; avoid treating heuristics/operator aliases as wire-verified; promote only uniquely matched SCL topology and endpoint. Synthetic/documentation IP only. No customer IID, raw captures, discovery writes, or comparison-product materials. CODE/CI and physical field acceptance remain separate.

[masarray]

2026-10-22 staging→main audit triage. Keep this PR OPEN (unique/divergent functionality), do not cherry-pick or close as duplicate.

SHA 1ed776a689c8707be5db09a6318c4a7613229f95. Evidence: Has 11 distinct commits; MmsCanonicalStaticRcbCandidatePager.cs and its tests plus GlobalIdentityEvidenceRegressionTests.cs are ABSENT from staging. Existing identity resolver/matcher and live RCB reconciler have different implementations. This is an alternative trial, not a proven safe ancestor/superset; compare semantics and budget limits with newer staging before any source integration.

Current staging SHA 44ac7554f43f2ba06763f3895242cb569b2e6a1c (CI https://github.com/masarray/ARIEC61850/actions/runs/39782663272 = 1,262/1,262 PASS), main promotion DRAFT PR #192. Reconcile on staging only, with new exact SHA and regression proof. No consumer repin or field qualification claimed. Tracking stays in #144 and #192; no duplicate issue.

[masarray]

2026-10-22 final source-level reconciliation of old #175 HEAD 1ed776a689c8707be5db09a6318c4a7613229f95. Do not merge the old branch into current staging: it changes resolver/matcher/reconciliation and introduces an old numeric-offset MmsCanonicalStaticRcbCandidatePager. Staging already implements a more robust MmsCanonicalStaticRcbCatalogPager with association- and catalog-bound continuation tokens, preserving deterministic bounded 66/300-RCB scanning, stale-token/catalog-mutation rejection, FC/DatSet checks and newer CI-proven control/RCB behavior.

Unique regression evidence preserved verbatim: staging-only PR #194, actually merged at 725662b004b74c3743943f83f3bcf93b745f7823, adds exact #175 GlobalIdentityEvidenceRegressionTests.cs blob 139190fc25ea705372042f355b44b49c462911e8 (five cases: shared IED prefix, provisional suffix confidence, operator display-only override, SCL verified topology and wrong endpoint/AP fail-closed). Windows CI #39788026745 tested refs/pull/194/merge and passed 1,269/1,269, zero build warning/error. No operational engine files changed in #194.

Closure classification: functionally superseded/partially adapted, not Git-ancestor incorporation and not claiming all historical commits merged. Original branch/commits preserved. Physical FAT/ARSAS consumer integration and main promotion remain unapproved: draft #192. Reopen if verifiable missing behavior emerges.