Update dependency: deps/haskell-backend_release#4935
Merged
ehildenb merged 4 commits intoJun 18, 2026
Conversation
ehildenb
approved these changes
Jun 18, 2026
…-state haskell-backend v0.1.155 replaces the implies `valid :: Bool` field with a `status` tri-state (valid | invalid | indeterminate). Parse `status` in `ImpliesResult.from_dict`, collapsing to `valid = (status == 'valid')`. The kore-rpc proxy escalates `indeterminate` to a decisive kore verdict except in booster-only mode, so the conservative collapse is sound for the binary consumers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
4 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.
Bumps
deps/haskell-backend_releasetov0.1.155. This release replaces theimpliesRPC result'svalid :: Boolfield with astatustri-state (valid|invalid|indeterminate), so pyk's response parsing is updated in lockstep.indeterminateis booster's "could not decide" signal (an indeterminate match or an SMT-unknown obligation). The kore-rpc proxy escalates it to a decisive kore verdict on every path except booster-only mode, so it only reaches a client that explicitly opted out of kore; pyk collapses it to the conservative not-implied answer for its binary consumers.Changes:
deps/haskell-backend_release,flake.{nix,lock}, and thehaskell-backendsubmodule tov0.1.155.statusfield inImpliesResult.from_dict(pyk/src/pyk/kore/rpc.py), derivingvalid = (status == 'valid').impliesmock-response unit fixture fromvalidtostatus.Validation:
make -C pyk checkclean; full pyk unit suite (1769 tests) passes, includingtest_implies.validfield — integration tests drive a live backend and compare against constructedImpliesResultobjects.