fix(release): lock qualified runtime lineage and public surfaces

[masarray]

Purpose

Integrate the implementation-neutral public surface while preserving the exact field-qualified ARSAS runtime lineage from PR #324.

Qualified authority

• final qualified source head: b0f25569a398c7bbdc3a3a34409dbd74ebf49444
• merged authority: 2b8e8adfd019bd087dc338dcc32bffefec53370f
• identical source tree: cccb50607161f8637e597b43d71038ffd4becfdc
• qualified workflow run: 35412542175
• qualified portable SHA-256: 6805b878f91f3d526cc50f3e81e3eb9a1f72500217dacc8921e50bdc349c5fcc

Corrections

• record the qualified source and artifact in .release/qualified-source.json;
• fail closed when release-sensitive inputs drift from the approved fingerprint;
• prevent an ordinary push to main from automatically publishing or replacing a GitHub Release;
• allow publication only from a tag or an explicit manual publication on main;
• preserve the accepted runtime algorithms while neutralizing public identifiers and wording;
• remove the remaining implementation-specific test identifiers;
• document the durable workstream integration authority.

Safety boundary

No IEC 61850 discovery, SCL projection, reporting, control, COMTRADE, FAT, or UI behavior is intentionally changed. Production-source edits in this PR are naming/comment substitutions; the release gate and evidence are additive.

Merge only after the exact combined head is green, including build, regression, installer, source-cleanliness, convergence, and production-promotion checks.

[masarray]

Integration status — qualified source repair

Corrective head: cb80662a1c7e6065e25c9d00ac46e93f26ffc9ab

Completed locally:

• qualified release source verifier: PASS (506 release-sensitive files);
• fingerprint: b86663f358499f656bcddd52e38dbe08df31b1192fae4136889677572dabada5;
• product-source validation: PASS (62 pages, 21 localized pages, 11 guides);
• workflow YAML parse: PASS;
• implementation-specific identifier scan across tracked text sources: no matches;
• git diff --check: PASS;
• branch is based on current main 5aedbfdfeeeb3c28bc219428c0df4466d9642b47.

GitHub-hosted Windows validation is currently blocked before execution: all exact-head jobs have remained queued/pending since 2026-09-19 09:51 UTC, with no failed job and no runner start. The PR must not merge until the combined-head build, regression, installer, source-cleanliness, interoperability, and production-promotion gates complete successfully.

[masarray]

Continuation audit — exact-head cb80662a1c7e6065e25c9d00ac46e93f26ffc9ab

Verified from the current PR head:

• previous PowerShell parser blocker in scripts/verify-source-clean.ps1 is no longer present;
• convergence regression now asserts the implementation-neutral Current stable baseline wording that exists in docs/INTEROPERABILITY_CONVERGENCE.md;
• README stable version is synchronized to v1.6.38;
• landing release notes are synchronized to 1.6.38;
• legacy implementation-specific convergence document path is removed from the branch;
• qualified-source governance is present and binds the release candidate to the field-qualified PR convergence(discovery/scl): interoperable discovery and usable SCL #324 lineage and artifact fingerprint;
• ordinary pushes to main no longer qualify to publish/replace a GitHub Release automatically.

Current GitHub-hosted exact-head runs are still queued/pending, not failed. Do not merge until the combined-head build, regression, installer, source-cleanliness, SCL interoperability, convergence, mainline-readiness, and production-promotion checks have actually completed successfully.

No runtime/engine baseline change is recommended while those gates are pending.