[masarray]

P0 — reconcile the shipped v1.6.42 source into main, without rollback

Status (25 Oct 2026): Public Windows application v1.6.42 is ALREADY STABLE, operator-accepted, and published at https://github.com/masarray/arsas/releases/tag/v1.6.42 . This PR concerns promoting its exact source to main, a separate action still BLOCKED by physical-control/interoperability authority. Do not mistake source qualification for the already published artifact's release label.

Current code and documentation identities

• Exact shipped v1.6.42 source tag: 3db2ca98d144ab4b456e8dc1db9af18ad7a948f2 (successful release workflow https://github.com/masarray/arsas/actions/runs/40151975055).
• RC source and tagged release have identical Git tree bc278a81a96517a979a161d2889493047cf204e0. All latest IED Browser, typed MMS Write/control, Smart IP, GOOSE/SV, FAT, IO and COMTRADE functionality is preserved.
• Documentation/website Public Stable sync landed on main via PR docs(site): reconcile README, downloads and bilingual landing to actual v1.6.42 stable #742, with follow-up screenshot label and CHANGELOG fixes (main baseline 4e6a4c747f57693b02279b349e824c4bfdb6c119).
• PR source integration commit 976d54cb5876a3817de827b768c82b61aa845bd5 has two Git parents: exact integrated RC aa0b3d9dcb611b58738491285d06d7991843adb7 and current stable-documentation main 4e6a4c747f57693b02279b349e824c4bfdb6c119. Source tree is unchanged from shipped v1.6.42 except the 12 documentation/site/updater evidence paths introduced on main.
• Follow-up source commit updates .release/windows.json from 1.6.41 to 1.6.42 to match RC VERSION, Directory.Build.props and ArIED61850Tester.csproj; not a rebuild or republish. .release/published.json correctly describes existing immutable v1.6.42 assets. No release tag mutation, no binary changes.

Operator validation and engineering boundary

• Operator accepted the 5 monitored endpoint, 183 initial value, 14 static RCB path diagnostic plus tested SG7_BCU/GR_X_7SX85 typed ctlModel Read/Write/readback and SBO Enhanced commands. These are scoped acceptance observations, not universal physical device certification. Some endpoints may be same-host simulators.
• Later report capture: 432 frames, 38 continuity observations and 9 IED-reported BufOvfl notices. These do not prove 38 lost events or guarantee lossless buffered SOE.
• ARIEC61850 engine f75e323e9f8443aa20e0a3818a1d5d77255b2c0f remains DRAFT code-trial from engine PR Fix responsive top bar navigation clipping #192, not independently qualified physical R7/R10 authority. Existing SCL R7 and Interoperability Reference Guard checks in pull-request context deliberately FAIL until qualified provenance and device evidence exist; push-context success does not waive this.

Merge decision

• Reconcile current main Public Stable website/README/CHANGELOG/metadata with the exact RC implementation without reverting any code or documentation.
• Align staged Windows version manifest to 1.6.42 with correct source identity, without packaging a new release.
• Demonstrate physical R7/R10 and requisite replay/EntryID/SqNum, reconnect, trusted-SCL and safety evidence on real hardware, and qualify or separately gate trial-engine authority.
• Achieve green pull-request SCL R7 and Interoperability Reference Guard by fixing the real cause (not weakening guards, spoofing evidence or silently repinning engine).
• Re-run full integration/Windows testing and review exact main merge head.

Keep PR DRAFT; do NOT merge to main before meaningful physical gates pass. This policy protects critical field-control semantics while preserving the already-published public application binaries unchanged. Related earlier validation: PR #740, #741 and archived comments in this PR.

[masarray]

D28 owner decision — RETIRE historical main-promotion PR, do not request another field capture

The operator explicitly confirms the newest successful evidence and published v1.6.42 are the accepted working basis. No more device/packet capture is requested or planned to satisfy this historical trial PR. The open PR's old checklist should not be treated as an ongoing user obligation.

Closing #729 as NOT MERGED ends the outdated proposal to promote a trial engine/source to main. There is NO bypass of the recorded SCL R7/interoperability guard failures; no conversion of failed PR gates to PASS, no change to engine provenance, and no false certification of universal devices. No attempt was made to publish or replace the accepted v1.6.42 binary.

Preserved evidence and refs: integrated RC d4598619b1b8fc21487cf5beb83a8a8284d0e9cf, main 14e5dddfbaae012b61a021366c1a864d83d316f2, existing immutable v1.6.42 release/tag and all historical branch/PR records. A future mainline source strategy, if ever authorized separately, must be scoped to actual confirmed requirements using already available evidence and source tests rather than expecting the operator to repeat earlier captures. The present request is PR cleanup and accepted-baseline preservation, not new field qualification.