Fix session history retrieval and incomplete final answers - #59
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Conversation-history requests could leave direct finalization for an irrelevant video lookup, and schema-valid non-answers such as "The" or a promise to look up history were accepted as completed. This change gathers session context before a separate structured-answer call, prevents history-only requests from escalating to video inspection, and verifies exact-first-message answers against the original stored text.
Known fragment-only and promise-only answers get one repair before failure. These are narrow checks, not a general guarantee of semantic completeness. Saved-frame follow-ups now identify reused images in the activity trace while still allowing analysis for a new visual question.
Context gathering is capped at four model steps, followed by an answer call and at most one repair under the existing deadline and cost limit. Separating the calls can add inference latency. Existing persisted routes and traces remain readable. No new bindings or migrations.
Validation: