Fix Core 0.7 input boundaries before acceptance (0.8.5) - #15
Merged
Merged
Conversation
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.
Changes
Evidence
Local targeted API tests: 31 passed. Cross-repository test against actual Core/API/Agent code: 25 cases, previously 14 inconsistent cases, now 0; full hosted checks must pass before merge. Existing acceptance state is not reset or migrated.
The patch was applied against source 0ed259f and the resulting tree was checked against 0fd679048c093bbcc985b0e5692d7e8050257352. The temporary patch-application files are not included in this PR.
No frozen draft, historical signature, credential configuration, or Prooftask change.