Expose UnivMon standard update compatibility - #139
Merged
Merged
Conversation
This was referenced Sep 11, 2026
Merged
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
2 participants
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.
UnivMon consumers need to reject incompatible persisted states before calling the standard update or merge APIs, which assert when given terminal-mode state.
Add
accepts_standard_updates()to expose this compatibility check without exposing mutable mode metadata or duplicating wire decoding in the backend.Before this PR: a backend could decode a valid terminal-mode state but could not check whether standard ingestion would accept it.
After this PR: it can reject that state before installation or merge; empty and standard states remain accepted. Serialization and estimator behavior are unchanged.
Verification: the focused Rust test passes for empty, standard, terminal, serialized/restored, and reset states. Performance measurements are not applicable to this metadata accessor.