Skip to content

groomer freshness: capture repository-context empty searches in the baseline #1115

Closed

Description

@joryirving

Follow-up from #1091 (PR #1114).

Problem

#1091 saves empty search_code queries from exploration tool calls only. The repository-context pass (src/lib/groomer/repository-context.ts) also runs keyword searches before analysis; when one returns nothing and the tool loop is disabled, the run has repo-wide negative evidence with no saved query. The freshness baseline therefore records scope global with no queries, and every default-branch commit stales the result (global_evidence_commit) — the exact churn #1091 removed for exploration searches.

Scope

  • Capture repository-context queries that returned zero results into the same bounded groomedSearchCodeQueries baseline field (or a parallel one), with the same bounds (dedupe, trim, max count/length).
  • Keep the conservative behaviour when it cannot be determined whether a query was empty.
  • Extend freshness tests to cover a dispatcher-only run whose only negative evidence is a repository-context search.

Expected files

src/lib/groomer/repository-context.ts
src/lib/groomer/freshness.ts

Out of scope: any change to staleness reasons or the recheck mechanics from #1091.

Activity

  1. added
    type/choreRoutine tasks and maintenance
    status/readyReady for Dispatch worker pickup.
    status/in-reviewPull request or human review is in progress.
    and removed
    status/readyReady for Dispatch worker pickup.
    on Sep 27, 2026
  2. added and removed
    status/in-reviewPull request or human review is in progress.
    on Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions