Repository navigation
correct: Handle mixed-case damage explicitly #37
Description
correct() and the standalone correct command previously reported no candidate / “No valid correction found” for otherwise repairable mixed-case input, while interactive recovery already applied majority-case interpretation.
Implemented and reviewed in PR #42: apply the same majority-case interpretation to the public correction API and standalone CLI, retry minority-case characters as erasures, preserve the shared deadline/capture ledger, keep explicit --bytes enforcement, preserve the operator's original characters in CorrectionEdit.observed, and never Unicode-case-fold non-ASCII text. The parser itself remains strict: mixed-case codex32 strings are invalid until corrected.
PR #45's distinct correct exit statuses are already merged into #42's branch, so the current #42 head carries both fixes and has green exact-head CI. Keep this issue open until #42 is human-integrated into current reviewability-v1; the branch has ordinary base divergence after #7/#51 rather than a known semantic blocker. Rerun the existing mixed-case/status regressions and frozen differential verifier on the integrated tip.
Activity
correct: Interpret mixed-case damage
correct: Interpret mixed-case damage
correct: schedule required mixed-case work first
correct: Interpret mixed-case damage
correct: Interpret mixed-case damage
correct: Share mixed-case scheduling across the CLI
correct: Preserve mixed-case preflight seed
correct: Preserve structural erasure kinds
correct: Preserve structural erasure kinds
correct: Interpret mixed-case damage
correct: Honor grouped immutable header
test: Prove mixed-case deadline budget
correct: Report mixed-case truncation
correct: Interpret mixed-case damage
correct: Preserve mixed-case preflight seeds
correct: Preserve mixed-case preflight seeds
correct: Interpret mixed-case damage
correct: Preserve mixed-case preflight seeds