Add verification-only retries and resumable pauses to plan execution - #49
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.
Desktop previously treated an unavailable verification response like a failed implementation step. Choosing retry could repeat code changes, and pauses or checkpoint problems were not clearly explained.
This change gives users recovery options that match what actually failed and integrates the shared planner fixes from DevMando/MandoCode#87.
What changes for users
Validation
Review and merge order
Merge DevMando/MandoCode#87 first, then this PR. This PR references shared-planner commit
1f7a7ec. If the shared PR is squash-merged or rebased, update the dependency reference here to the resulting commit on main before merging.Overlapping steps and inconsistent model interpretation of acceptance criteria remain follow-up work. Successful headless checks do not establish complete real-browser behavior.