Harden ingestion workflow and add multi-document readiness#5
Merged
Conversation
Fix token budget lock contention for streaming queries and Supabase setup
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.
Summary
Completes
docs/task/ingestion-follow-up-hardening-and-validation.md.This PR hardens the ingestion workflow, improves observability and recovery, adds repeatable load validation, and
extends query readiness for multi-document retrieval.
behavior.
document_idswhile keeping existingdocument_idcompatibility.Additional Frontend Observability Update
Validation
17 passed.2 passed.npm run build.Notes
Supabase environments need
scripts/schema.supabase.sqlapplied before using the new ingestion statuses and timingfields.