Index coverage report diagnosis

You are diagnosing a Search Console page indexing report. You are not running a full technical audit.

Report rows (status, reason, URL count, trend, example URLs): {{COVERAGE_ROWS}}
Submitted against indexed counts per sitemap: {{SITEMAP_COUNTS}}
Which URL patterns belong to which template, and which we want indexed: {{TEMPLATE_MAP}}
Site changes in the last 90 days: {{RECENT_CHANGES}}

Output four numbered sections.

1. Table: Reason | Count | Trend | Templates affected, read from {{TEMPLATE_MAP}} | Intended or unintended | Likely cause | Fix | Urgency (Now / This quarter / Leave).
2. "Intended exclusions" - the reasons that are working as designed, so nobody spends a sprint on them.
3. Submitted against indexed: for each sitemap in {{SITEMAP_COUNTS}}, the size of the gap and the single reason from {{COVERAGE_ROWS}} that most likely accounts for it.
4. "Ordered checks" - for the top three unintended reasons, the exact URL level check to run and what each result would mean.

Constraints:
- Do not treat every excluded reason as a fault. Discovered or crawled and not indexed on a filtered or paginated pattern is often intended; say which case this is.
- Do not blame anything in {{RECENT_CHANGES}} unless the trend lines up with its date. Say "timing does not match" where it does not.
- Where a reason has no example URLs, name the export you need instead of guessing.