Repository navigation
fix: route changes-description diffs with whitespace-tolerant matching - #590
Merged
codelion merged 2 commits intoNov 5, 2026
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.
Fixes #589.
In changes-description mode, routing required an exact SEARCH match even though patch application accepts differences in trailing whitespace. Valid code edits could be omitted, or the worker could discard a valid description update as unchanged.
Reuse the existing exact-then-trailing-whitespace matcher for routing. Keep leading indentation significant, and reject ambiguity whenever the same SEARCH block can apply to both code and the description under those matching rules.
Tests cover both directions of trailing-whitespace differences, ambiguity, significant indentation, and complete worker application/rejection paths with mocked LLM and evaluator boundaries.
Validation:
OPENAI_API_KEY=test-key-for-unit-tests python -m unittest discover tests— all 1,074 tests passed in 196.454s.git diff --checkpassed.Assisted by OpenAI Codex for investigation, implementation, and local validation.