Repository navigation
Repair contextual dictation and mobile speech flow - #601
Merged
Merged
Conversation
This was referenced Sep 10, 2026
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.
Merge decision: ready — recorded dictation now supplies conversation vocabulary, preserves drafts through retry/cancellation, and avoids mobile recognition accumulation and playback workarounds.
User outcome
Repairs the repeated progressively longer prefixes and replayed previous dictation observed in the DGX “Von Task Smoke Test”. A microphone recording produces an editable transcript; Send finishes transcription first, failures retain retryable audio, and late results cannot alter another conversation.
Material changes
Evidence
VON_USE_MOCK_DB=1: actual upload handler, normal server session binding, model denial, MP4/WebM/context/language transport, safe errors, and three chat-model candidate boundaries.Ship boundary
Minimum ship criteria are met for this bounded transport/lifecycle repair. Lost or duplicated draft, stuck microphone, cross-actor context access, or audio-only models entering chat fallback would block delivery. Physical iOS/Android, acoustic accuracy and runtime deployment are separate receipts, not established by browser emulation. Raw DGX microphone audio and recognition events were not retained; the stored transcript and code establish the accumulation failure class.
Streaming hands-free conversation, server TTS, wake words, paired devices and persistent raw-audio retention are outside this PR. Existing primary models and credentials are preserved; a transcription model must be added as an additional authorised model before runtime use.