Repository navigation
Promote proven dev integration to main - #192
Merged
Merged
Conversation
ci(shell): syntax-check Bash client
ci: pin ores-lint workflow actions
…ression style: enforce blocks and non-compressed statements
style: scope no-compression lint to source
…ocks style: finish C++ protocol control-flow blocks
style: finish C++ JSON parser blocks
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.
Promotion PR for the current
devintegration branch.Current exact-head funded proof:
a265c9f0236a06f09752e4230f19fc2d6ae9b150The refreshed proof runs the bounded formal model + deterministic replay, implementation refinement/adversarial tests, starts the exact-head broker, and exercises 9 real client languages (Rust, Python, shell, PowerShell, Go, Dart, Java, C++, Gleam). All steps are green.
The older proof at run
36209120249pinned31af071f...and is retained as historical evidence only;devhad advanced substantially, so it was not used as the merge decision for this promotion.Because
devandmainhave diverged, this PR exists specifically to surface and resolve the real semantic conflict set before promotion. Do not force-updatemain.