See how app defects are hitting a key Zendesk customer

**Objective:** For Zendesk organization `{organization-name}`, find which of its tickets from the last `{lookback-days}` days (default 30) trace to Bugsnag errors, and summarize the customer's exposure to application defects.

**Step 1: Confirm the organization**

Call `zendesk-get-organization` with `name` set to `{organization-name}`. If nothing comes back, call it again with `domain-names.contains` using the most likely domain, and if more than one organization matches, list them and stop. If none match, report that and stop.

**Step 2: List its tickets**

Call `zendesk-get-ticket` with `organization-name` set to the organization's exact name and `created.from` set to `{lookback-days}` days ago. Set aside tickets whose subject is clearly non-technical (billing, access requests, how-to questions); keep the ones that describe something failing.

**Step 3: Match each technical ticket to Bugsnag**

For each kept ticket, read it with `zendesk-get-ticket-comment`, pull the error text or failing feature, and call `bugsnag-get-error` with `message.contains` set to a short fragment and `last-seen.from` set to 7 days before the ticket's created-date. Rate the best match High, Medium or Low as you would for a single ticket.

**Step 4: Report**

* The organization: name, organization-id, ticket count in the window, and how many were technical.
* A table: ticket-id, subject, status, created-date, matched error-id, error status in Bugsnag, match rating.
* A second table grouping by error: error-id, error-class, Bugsnag status, how many of this customer's tickets it caused.
* Call out any error that is fixed or ignored in Bugsnag while this customer's ticket about it is still open. Those are the tickets an agent can close the loop on.

**Rules & Guidelines:**

* `zendesk-get-organization`, `zendesk-get-ticket` and `zendesk-get-ticket-comment` are on the zendesk server. `bugsnag-get-error` is on the bugsnag server.
* This prompt is read-only. Do NOT call `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `zendesk-update-organization`, `bugsnag-open-error`, `bugsnag-update-error-severity` or any other write tool on either server.
* Bugsnag does not record which customer saw an error. The link is through the ticket's wording and timing only; do not claim the customer caused the error's full event count.

**Validation:**

* If the organization has more than 40 technical tickets in the window, process the 40 most recent and say how many were skipped.
* If no ticket matches any error, report that the customer's issues do not trace to Bugsnag errors in this window.
* Pass dates as YYYY-MM-DD.