Skip to content

CI ONLY — verify exact #187 SBOw send/response timing HEAD (DO NOT MERGE) - #188

Closed
masarray wants to merge 176 commits into
mainfrom
fix/p0-sbo-enhanced-confirmed-wire-stage-timing-20261021
Closed

masarray wants to merge 176 commits into
mainfrom
fix/p0-sbo-enhanced-confirmed-wire-stage-timing-20261021

Conversation

@masarray

Copy link
Copy Markdown
Owner

CI qualification only for feature draft #187 (stacked on engine #184). GitHub's current .NET CI workflow does not trigger for #187's correct stacked base branch. This separate draft must not be merged to main and must not be treated as feature review. It is solely to exercise the Windows build/test on the exact #187 source HEAD, including existing positive/negative SBO enhanced service tests. No ARSAS engine pin modification or public release. Audit comparison and exact SHA before using resulting CI evidence.

…ait and decode without altering command semantics
…ait and decode without altering command semantics
…ait and decode without altering command semantics

Copy link
Copy Markdown
Owner Author

CI-only PR cleanup audit (2026-10-22). This PR explicitly says DO NOT MERGE and is not an independent feature. Its test-lane purpose is complete: the exact source HEAD 4ed76ccd11b763d passed Windows .NET CI: https://github.com/masarray/ARIEC61850/actions/runs/39593661449 . Functional source of truth: #187. SBOw physical timing/behavior not field-qualified by CI.

Closing this CI-only PR without merging. This does not change main, delete branches, close the functional feature PR, approve ARSAS engine pin updates, or constitute physical/FAT qualification. Evidence remains linked here for the consolidated merge audit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant