Repository navigation
Conversation
Owner
Author
M2.1 first-code checkpoint — verified Windows CI
No public stable or engine-lock change. No physical device acceptance claimed. Current scope is the typed Quality/Dbpos-safe MMS Read presentation slice of M2.1; typed report ingress, timestamp evidence propagation and unified live state are the next work, not yet complete. Existing warnings in older tests remain non-blocking. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Baseline and safety
Built on existing ARSAS Browser M1.5/M2 draft branch at 0a663ec; pinned engine 036e2c00d83a0815b6160147b14ea05975057965 unchanged. Never merged to stable main. No RCB/GI, report planning, dynamic polling, commands, SCL export, or release modifications.
Implemented — first incremental M2.1 slice
Gates
Requires CI Windows regression at exact SHA; no physical ZIV AVR/BCUGE claim. Follow-up is engine-side typed observation ingress, shared per-IED live store, hierarchical details, Quick Start and COMTRADE workflow. Keep draft; no merge to main or public release without explicit operator approval.