Release ARSAS 1.6.32 — field-proven Smart Control baseline

[masarray]

ARSAS 1.6.32 release consolidation

Release-only PR based on the consolidated G1.1 field-proven main baseline.

Runtime/protocol scope

No IEC 61850 runtime, reporting, reconnect, control, quality, Event Log, GOOSE, SV, website release evidence, or engine-lock behavior is changed by this PR.

Exact baseline entering this release

• ARSAS G1.1 field-proven head is already merged into main through merge commit 43832ed1e981ee9580e5d0902a64b186ed50a372.
• ARIEC61850 G1.1 is already merged into engine main through merge commit 813b3dd4b5f7cbbeb7fd60fc0c33e82ab140bafa.
• ARSAS remains immutably pinned to engine commit a18e550d07f7bbe4ff7753c180b02615075f6292, the exact engine head used by the successful physical Open/Close field test.

Release-only changes

• bump canonical app/project/VERSION metadata from 1.6.31 to 1.6.32;
• update .release/windows.json to request a fresh 1.6.32 stable Windows build;
• keep currently published website release evidence at 1.6.31 until 1.6.32 publication succeeds;
• do not reuse 1.6.31 artifacts.

Verified PR gate

Exact release head d28ff4beebc1c31bc430ad117ce550f86aee370a passed:

• Build ARSAS #1318: source/license/invariant checks, exact engine-lock resolution/API checks, restore/build, full application regression tests, portable single-EXE publish and smoke test;
• Windows installer #302: exact engine checkout, restore/build/test, installer publish/compile, silent install/uninstall smoke and checksum artifact.

Publication gate

Merging this PR changes .release/windows.json on main, triggering release-windows.yml. That workflow must rebuild exact main source against the immutable engine lock, rerun regression tests, portable smoke and installer install/uninstall smoke, then generate checksums, SPDX SBOM, provenance and GitHub artifact attestations before creating/updating stable GitHub release v1.6.32.

Known product limitation remains unchanged: automatic full dynamic DataSet/RCB activation is quarantined pending G2 qualification, and repeated network-outage reconnect acceptance remains a field-validation item.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.