Repository navigation
Make genuine Orca speech output visible before terminal sampling - #709
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.
The genuine Orca journey reached rearmed DOM/live events but failed because no qualifying speech-output record was observed. The selected vendor logger buffers its existing stream. Configure complete-line visibility before the genuine startup marker and bind strict boolean stream settings in readiness/3; keep Speak intent distinct from SPEECH OUTPUT and preserve the original speech deadline and custody guards.
Validation: maintained source controls pass 121 contract, 149 browser, 39 INFO and 52 event cases (21 added), plus 25 public-reference compatibility tests. New controls reproduce a buffered terminal record, require visibility before close, reject Speak-only evidence and wrongly typed settings, and preserve configuration/flush errors before readiness. Both failed native runs remain retained and unaccepted; a new native journey requires separate admission. No timeout or cleanup predicate changed.