Fix OCR compatibility status and numeric limits for 0.8.3 - #141
Merged
Conversation
8 tasks
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.
Outcome
Toolkit 0.8.3 feature implementation is merged. This PR closes the repository feature gate for #139, #140, #142, and #143; stable publication and issue/milestone closure remain owned by the protected release workflow and independent external readback.
Delivered
0, plus behavioral numeric boundary qualification.Evidence
6520a53db6b4f9d907735456be43e0b17ec296af6ab22194ecb44329a7b89be918c4c5afb8f8daf774b3f46f72f1d6231c44cc39ca12f732a46da706mainruleset readback retained ten required non-macOS contexts and removed only the two macOS contexts.No real LLM/model/provider request was run or claimed. Deterministic installed OCR 1.10.0 no-model boundary evidence remains the exact qualification boundary.