feat(recall): inspect extraction progress - #1332
Open
wesm wants to merge 3 commits into
Open
Conversation
Aggregate coverage counts do not explain which sessions are blocked or why, forcing operators back to database inspection when extraction stalls. Expose a bounded, generation-scoped progress view so pending, partial, and failed work can be diagnosed from the Recall page without loading transcripts or enabling the extraction manager. The surface is intentionally read-only. Retry and generation lifecycle mutations remain separate follow-ups so this diagnostic contract can land without introducing model-work controls.
roborev: Combined Review (
|
Recall extraction progress depends on archive-owned state that read-only backends do not provide. Advertising the drill-down unconditionally leaves those deployments with a control that can only return HTTP 501.\n\nExpose the capability through the existing status response so clients can omit unsupported controls while preserving progress inspection for local SQLite archives.
roborev: Combined Review (
|
The progress panel owns a request whose cancellation invalidates its completion callback. Leaving its loading flag set keeps the page-level refresh action disabled even though the panel and its work are gone.\n\nReset the loading state alongside cancellation so closing the drill-down immediately restores the rest of the page controls.
roborev: Combined Review (
|
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.
Recall’s aggregate coverage counts do not identify which sessions are blocked or explain extraction failures. This adds a read-only progress drilldown to the Recall page with generation-scoped pending, partial, and failed rows, source-session links, unit progress, error details, retry timing, localized state filters, and bounded cursor pagination.
The endpoint reads directly from persisted extraction state, so existing archives remain inspectable without a configured extraction manager. The surface deliberately excludes retry, run, activation, and retirement actions; those model-work and corpus-lifecycle controls remain separate follow-ups.