Repository navigation
Announce explicit rearm while retaining original command evidence - #703
Merged
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
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.
Explicit command rearm currently uses the same status sentence as initial readiness. Native run 38161875084/a1 reached
Rearmedthrough the genuine keyboard action, but Orca did not announce that sentence after the action. The retained evidence establishes the missing announcement; the exact suppression mechanism remains unproven.Give rearm with a retained unknown receipt a distinct status that says commands are rearmed, the original evidence is retained, and new commands use fresh correlations. Keep the exact post-action Orca speech requirement with its existing deadline. Extend the existing browser recovery tests to check that status after reconciliation and abandonment; generation fences and immutable receipt checks remain intact.
Qualification: the bounded Python-only operation passed all 29 navigation controls and the existing diagnostic self-test, with matching original receipts, observed-empty cleanup and unchanged source pins. Exact-head hosted composition checks must qualify the product status and browser assertions before delivery. Native journey acceptance remains pending.