Summary

• Follow-up to improvement(search): lead an overflowing Jira all-terms match with issues whose summary holds every term #9111 and improvement(search): fall back to Jira summaries holding half the terms of a longer query #9115: when a Jira all-terms match overflows its page, issues whose summary holds every term still lead, and issues whose summary holds at least half of three or more terms now follow them (most terms first) instead of being dropped whenever any all-terms summary exists
• Before, one or two all-terms summary hits meant the rest of the page went back to newest-created issues even though the half-terms search had already returned relevant ones
• No extra requests: both summary searches already run in parallel; only how their results combine changes. One pass dedupes the summary tiers and the rest of the all-terms page

Type of Change

• Improvement

Testing

• atlassian.test.ts: new case for every-term summaries followed by half-term summaries; reverting to either-tier selection and removing the dedupe each turn it red; lib/sim-search/live suite passes (334 tests)
• Three-way offline replay on a large production Jira (read-only), 60 distinct plain queries from real client sessions, pooled blind relevance labels per query, two independent judges: against the shipped rule this changes 1 of 23 overflowing queries (relevant in the top 10 0 → 5), 0 worse, 22 identical, under both judges; relevant issues in the top 10 across all 23: today's page 32/35, shipped 77/95, this 82/103 (first/second judge)

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)