Repository navigation
fix: make the planner agree with the specification - #3
Merged
Merged
Conversation
The model-based test found three disagreements. The planner fell back to the YX path without checking that it was clear, it built descending walks in the wrong order, and it kept the previous obstacle when reset without one. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
conjikidow
added a commit
that referenced
this pull request
Aug 17, 2026
The model-based test found three disagreements. The planner fell back to the YX path without checking that it was clear, it built descending walks in the wrong order, and it kept the previous obstacle when reset without one. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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 the three disagreements the model-based test reported, which is what step 2 of the tutorial asks
participants to do.
The planner fell back to the YX path without checking that it was clear, so it never returned
NoPlanandhappily planned through the obstacle.
It built descending walks in the wrong order, so paths moving towards a smaller coordinate came out reversed.
And
resetkept the previous obstacle when given none, so a planner reused across traces carried state itshould have dropped.
Every test passes now, including the model-based one.