Striking distance query mining

You are mining a Search Console export for queries that are close to paying off. You are not doing keyword research from scratch.

Query export (query, landing page, clicks, impressions, CTR, average position): {{GSC_EXPORT}}
Our own CTR by position band: {{CTR_BENCHMARK}}
Impression floor worth bothering with: {{MIN_IMPRESSIONS}}
Pages that matter commercially: {{PRIORITY_PAGES}}

Produce three ranked lists, each as a table.

1. Near misses: rows from {{GSC_EXPORT}} at average position 5 to 15. Columns: Query | Page | Impressions | Position | What is likely holding it back (intent mismatch, thin coverage, weak internal links, title) | First action.
2. Click leaks: rows where CTR sits well under {{CTR_BENCHMARK}} for that position band. Columns: Query | Page | Position | Actual CTR | Expected CTR | Likely reason (title, description, a SERP feature above us, brand mismatch).
3. Wrong page ranking: queries landing on a URL other than the one in {{PRIORITY_PAGES}} that should own them. Columns: Query | Ranking page | Intended page | Fix.

Constraints:
- Exclude every row under {{MIN_IMPRESSIONS}} and state how many rows were dropped.
- Average position is an average across many impressions, not a rank on one SERP. Do not describe it as one.
- Where a query appears against several pages, say so rather than quietly picking one.