Conversation
- Validate rollback boundaries before interrupting provider turns - Silently restore optimistic composer state when boundaries are unavailable
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.
What Changed
Why
A stale Esc retraction could target provider history that was no longer available, causing unnecessary interruption and surfacing an error even though the retraction could be safely discarded. Preflight validation now detects this case before mutating provider state, and the clients silently reconcile the optimistic UI back to its prior composer state.
UI Changes
Behavior-only UI change. No visual layout or styling changes; stale retraction errors are no longer surfaced, and the composer is restored silently.
Checklist