feat(obscura-web): deep-research auto_continue, auto-consolidate, grouped run-report findings - #110
Merged
Merged
Conversation
…uped run-report findings - auto_continue (opt-in, default off): when a job would stop at budget_exhausted with leads still queued, extend the SAME job's budgetMs once, straight to max_total_minutes (default 60, cap 180), instead of spawning a new job. New stoppedReason "max_total_time_exhausted" when that ceiling is hit with work left; frontier_empty and max_rounds (40) still apply as backstops. - auto_consolidate (default on): best-effort consolidateTopic() call in runJob's finally, after the run report is durably written, so a failure (no Ollama, no sources, already-consolidated summary) never affects job.state. obscura_research_status.next reflects whether it actually ran. - renderRunReport groups "Top findings" by originating query instead of one flat relevance-sorted list; retention cap raised 15->40 (TOP_FINDINGS_CAP) so a grouped report has enough per topic to be worth grouping. - 8 new/updated tests across deep-research.test.mjs and deep-research-mcp.test.mjs; full obscura-web suite 450/461 (11 pre-existing robots.mjs skips, untouched); lint + typecheck clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
CI's lint job runs prettier --check separately from eslint; two lines in the new auto_continue/auto_consolidate tests exceeded print width. No semantic change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
auto_continue(opt-in, default off): when a deep-research job would stop atbudget_exhaustedwith leads still queued, extend the SAME job'sbudgetMsonce, straight tomax_total_minutes(default 60, cap 180), instead of spawning a new job. NewstoppedReason: "max_total_time_exhausted";frontier_emptyandmax_rounds(40) still apply as backstops.auto_consolidate(default on): best-effortconsolidateTopic()call inrunJob'sfinally, after the run report is durably written — a failure (no Ollama, no sources, already-consolidated summary) never affectsjob.state.obscura_research_status.nextnow reflects whether it actually ran.renderRunReportgroups "Top findings" by originating query instead of one flat relevance-sorted list; retention cap raised 15->40 (TOP_FINDINGS_CAP).Test plan
deep-research.test.mjs+deep-research-mcp.test.mjsobscura-websuite: 450/461 (11 pre-existingrobots.mjsskips, untouched)npm run lint— cleannpm run typecheck— cleangatos-especies-habitos, 138 sources persisted) — confirmed the existing engine-rate-limit resilience survives, and the new fields (originalBudgetMs,consolidateResult/consolidateError) shape correctly on the snapshot