See how many customers a Jira bug really affects

**Objective:** Estimate the customer impact of Jira issue {issue-key} by finding Zendesk tickets about the same problem created in the last {lookback-days} days (default 30).

**Step 1: Read the issue (Jira)**

Call `jira-get-issue` with issue-key {issue-key}. If it does not exist, stop and say so. Note its summary, status, assignee and created date. If the summary starts with `[ZD-<id>]`, that ticket is the origin.

**Step 2: Find related tickets (Zendesk)**

* If there is an origin ticket, call `zendesk-get-ticket` with its ticket-id.
* Pick 2 or 3 distinctive terms from the issue summary (product area, error text, feature name; never generic words like error or issue). For each, call `zendesk-get-ticket` with subject.contains set to the term and created.from set to today minus {lookback-days} days (30 if empty).
* Merge the results and drop duplicates. Read each candidate's subject and keep only those plausibly about the same problem. List the ones you rejected with a one-word reason.

**Step 3: Enrich (Zendesk)**

For the kept tickets, call `zendesk-get-satisfaction-rating` with ticket-id to find bad ratings, and group the tickets by organization-name.

**Step 4: Report**

* The issue: key, summary, status.
* Totals: matching tickets, open versus solved, distinct organizations, bad satisfaction ratings.
* A table by organization: ticket count, highest priority, oldest open ticket.
* The ticket list: id, subject, status, priority, organization.
* A one-sentence impact rating (low, medium or high) with the reason.

**Rules & Guidelines:**

* `jira-get-issue` is on the jira server. `zendesk-get-ticket` and `zendesk-get-satisfaction-rating` are on the zendesk server.
* Read-only. Do not call `jira-update-issue`, `jira-add-issue-comment`, `zendesk-add-ticket-comment` or `zendesk-update-ticket`. Suggest link-ticket-to-issue for tickets the user wants linked.
* Subject matching is a heuristic. Say so in the report and never present the count as exact.

**Validation:**

* If no ticket matches any term, report zero impact found and list the terms searched, so the user can suggest better ones.