chore(maintenance): consolidate runtime boundary and deterministic CI

[masarray]

Purpose — consolidated first-pass maintenance candidate

This draft brings the exact file changes from #413, #414, and #415 together on one commit and validates the combined GitHub PR candidate. It is intended to reduce review/integration ambiguity, not create new implementation paths. Do not merge until the contributor's affirmative CLA acceptance is recorded and the final integration state is rechecked. The source PRs remain open as traceability and should only be closed as superseded after the chosen integration is actually merged.

Exact baseline and provenance

• Base: main 9d081f54fc6466d13c099e8a94a020c487a36703; head: f7d1f65163eca3731c33056bcbe6aa8cbff5572b.
• Exactly eight modified files, one integration commit, all eight file blob SHAs identical to their respective source PRs, with no conflict resolution or new changes.
• chore(maintenance): clarify runtime device contract and documentation index #413 (3 files): required-device facade callsite nullability and contributor/docs index corrections.
• ci(maintenance): verify exact source SHA in four discovery guards #414 (4 files): check out immutable CI candidate in Smart Discovery PR workflows and verify HEAD == GITHUB_SHA.
• ci(maintenance): use pinned ARIEC61850 in RCB export guard #415 (1 file): selected-RCB guard uses the exact pinned ARIEC61850 commit, not moving engine main.

Combined-head validation — PASS on signed-off exact head

9/9 GitHub Actions workflows succeeded on f7d1f65163eca3731c33056bcbe6aa8cbff5572b after the contributor's DCO amend. The tree remains identical to the previously validated 8-file candidate.

• Build ARSAS: source revision, solution build, 1,315 tests passed, 0 failed, 0 skipped, portable single-EXE publish and upload succeeded.
• Smart Discovery Merge Execution Guard: 1,315 tests passed, 0 failed, 0 skipped.
• Smart Discovery Field Capture Build: succeeded.
• Legacy SAS RCB export guard: succeeded on the pinned engine.
• Golden Budget Lock, Golden Provenance, Repeat-Run Stability, Mainline Readiness, and Production Promotion Guard: all succeeded.
• The previous pre-amend head c37bec2c20f99077d8b6b4b2d38ebcc55896e2c9 is historical evidence only; the exact-head rerun above is authoritative.

No-regression boundary

No change to the accepted v1.6.40 Discovery/SCL production path, canonical model, static DataSet membership, RCB/GI/report-only authority, dynamic mutation/polling policy, engine or ArdIrec lock, release workflow, tag, or published packages. No physical IED operation was performed for this source-only maintenance change.

Merge requirements — not yet satisfied

• DCO commit trailer is present on the current head: Signed-off-by: ARI SULISTIONO <ari.sulistiono@gmail.com>. This is distinct from a cryptographic Git commit signature, which is not required by DCO.
• Affirmative CLA acceptance has not been observed in the PR comments. The repository's unprotected main has no formal approval-review requirement; technical source/blob and CI review is recorded in the PR discussion. No submitted GitHub approval is implied, and no legal agreement is asserted on the contributor's behalf.
• The current signed-off exact-head rerun completed 9/9 green. After the CLA statement is recorded, recheck latest main, the final head and checks before any deliberate merge; no automatic merge.
• If this consolidated PR becomes the accepted integration vehicle, close chore(maintenance): clarify runtime device contract and documentation index #413–ci(maintenance): use pinned ARIEC61850 in RCB export guard #415 as superseded only after it is merged, not before.

Tracks #380.

Integration result — verified

• Contributor's CLA acceptance is recorded in Conversation comment; DCO trailer retained by GitHub rebase merge.
• Merged to main at e7b43508fb3b2bf5fbda7be8ed8425da74bb9766; verified exact eight-file tree and original parent, no engine/release changes.
• 3/3 post-merge workflows green on exact main SHA: Build ARSAS (1,315 tests, zero failures), Smart Discovery Post-Merge Production Verification (988 engine tests + 1,315 app tests), and Legacy SAS RCB export guard.
• refactor(formatting): avoid second legacy scalar extraction #417 is restacked onto this exact merged main in its own two-file draft PR and requires independent DCO sign-off and final CI. This integration does not claim a new physical IED acceptance or release.

[masarray]

Integration blocker (verified on 2026-09-26): this candidate is 9/9 CI green, but has no review submission and its commit c37bec2c20f99077d8b6b4b2d38ebcc55896e2c9 contains no Signed-off-by trailer. CONTRIBUTING.md requires every contribution commit to satisfy DCO.txt, plus affirmative agreement to CONTRIBUTOR-LICENSE-AGREEMENT.md.

Required authorized contributor/maintainer action before merge:

1. Personally read the DCO/CLA, confirm legal rights and any required employer authorization, and affirm agreement to the CLA in this PR discussion.
2. Create/approve a legitimate signed-off contribution commit using the contributor's own identity (do not substitute an AI-generated signature). Since SHA changes, rerun checks on the exact final combined head.
3. Review the final eight-file diff and approve the integration under the repository's workflow.

I have not signed on anyone's behalf, marked the PR ready, or merged it. The dependent pure-formatter refactoring is in draft #417, explicitly stacked on this branch and not eligible for main integration until this gate is satisfied.

[masarray]

Technical integration audit (2026-09-26) — source and CI ready, CLA statement still outstanding.

• Current signed-off head: f7d1f65163eca3731c33056bcbe6aa8cbff5572b; parent: 9d081f54fc6466d13c099e8a94a020c487a36703. Its tree SHA 767fdd56fb47cb1e0c6e0a6e6f8e14c7252835b7 is exactly the same as the pre-amend candidate; DCO amend did not change file content. DCO trailer present; cryptographic commit signature is not required by DCO.
• Compared actual Git blob SHA for all eight files against source chore(maintenance): clarify runtime device contract and documentation index #413 (3), ci(maintenance): verify exact source SHA in four discovery guards #414 (4), ci(maintenance): use pinned ARIEC61850 in RCB export guard #415 (1): 8/8 byte-identical. No engine lock, release code/tag, discovery/RCB runtime, or new unreviewed file enters the integration.
• Current signed-off exact-head CI 9/9 success: Build ARSAS, 1,315/1,315 tests, portable single-EXE publish; selected-RCB guard, Merge Execution Guard, and other checks.
• Dependent refactor(formatting): avoid second legacy scalar extraction #417 was restacked onto this exact signed-off commit, restoring its intended two-file diff. Its exact-head CI 9/9 success and 1,319/1,319 tests; refactor(formatting): avoid second legacy scalar extraction #417 itself remains separately gated.
• main is currently unprotected and the repository's CONTRIBUTING.md does not mandate a submitted GitHub approval review. This technical audit is not a self-approval or a claim of physical IED validation. Treat the recorded contributor rights/licensing requirements as the real outstanding gate.

Still needed before merge: contributor posts an affirmative CLA acceptance in this PR's Conversation (per CONTRIBUTING.md and CONTRIBUTOR-LICENSE-AGREEMENT.md). Current issue comments contain only the old blocker note; no new acceptance is visible. Do not post the legal declaration on the contributor's behalf. After it appears, recheck main, commit and exact-head CI, choose an intentional merge method, then verify the resulting main before changing #417's base.

[masarray]

Pernyataan pribadi kontributor, diposting melalui ChatGPT berdasarkan izin eksplisit yang diberikan dalam percakapan:

Saya telah membaca dan menyetujui CLA ARSAS untuk kontribusi saya pada PR #416 dan #417. Saya memiliki hak yang diperlukan untuk menyumbangkan kontribusi tersebut, termasuk izin pemberi kerja jika diperlukan. Saya mengizinkan ChatGPT memposting pernyataan ini di kedua PR melalui akun GitHub saya.