feat: propose safe rules from corrections - #44
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.
What changed
Product impact
Correcting a file no longer risks silently teaching the hat. The correction completes first. A reusable rule is then an optional, inspectable proposal that can be edited, previewed, explicitly added, or discarded without affecting the already-filed item.
File content used for the proposal stays in the on-device Foundation Models path. No correction, excerpt, or teaching history is uploaded solely to learn a rule.
Validation
TextRecognition.CRImageReaderError error 1, while all 94 passed on the fresh GitHub runnerCloses #39