-
Notifications
You must be signed in to change notification settings - Fork 2
correct: Handle mixed-case damage explicitly #37
Copy link
Copy link
Open
Labels
area: cliCommand-line interface behavior.Command-line interface behavior.area: correctionCorrection engine and correction UX.Correction engine and correction UX.bugSomething isn't workingSomething isn't workinggate: adversarial reviewResolve, merge, or explicitly defer before the next full adversarial review.Resolve, merge, or explicitly defer before the next full adversarial review.
Description
Activity
Metadata
Metadata
Assignees
Labels
area: cliCommand-line interface behavior.Command-line interface behavior.area: correctionCorrection engine and correction UX.Correction engine and correction UX.bugSomething isn't workingSomething isn't workinggate: adversarial reviewResolve, merge, or explicitly defer before the next full adversarial review.Resolve, merge, or explicitly defer before the next full adversarial review.
correct()andcodex32 correctcurrently return no candidate / “No valid correction found” for otherwise repairable mixed-case input because_correct_fixed()convertsInvalidCaseinto no result. Interactive recovery already applies majority-case interpretation.Choose and test one consistent standalone behavior: apply case interpretation before correction, or diagnose mixed case specifically instead of reporting a failed search. This concerns the API and CLI only; the reviewed commit had no GUI.