Find the customers a Bugsnag error has reached

**Objective:** Find the Zendesk tickets raised by customers hit by Bugsnag error `{error-id}`, using search text `{search-term}` (default: taken from the error's message).

**Step 1: Read the error**

Call `bugsnag-get-error` with error-id `{error-id}`. If nothing comes back, report that the error does not exist and stop. Note the message, error-class, context, project-name, status, users, first-seen-date and last-seen-date.

**Step 2: Choose the search text**

If `{search-term}` was given, use it. Otherwise pick 1 to 3 short fragments a customer would plausibly write in a ticket subject: the visible part of the message, the screen or feature named in context, or the wording the app shows the user. Customers do not write class names, so do not search Zendesk for the error-class unless nothing else is available.

**Step 3: Search Zendesk**

For each fragment, call `zendesk-get-ticket` with `subject.contains` set to the fragment, `created.from` set to the error's first-seen-date and `created.to` set to 2 days after its last-seen-date.

For each ticket returned, call `zendesk-get-ticket-comment` with its ticket-id and confirm the conversation actually describes this failure. Discard tickets where it does not.

**Step 4: Report**

* One line on the error: error-id, error-class, message (trimmed), project-name, status, users affected, first and last seen.
* A table of confirmed tickets: ticket-id, subject, requester-email, organization-name, status, priority, assignee-name, created-date, and one line of evidence from the comments.
* A count of distinct organizations and requesters affected.
* Any tickets you discarded, with the reason, in one line each.
* If no ticket matches, say the error has not reached support in that window and list the fragments you searched.

**Rules & Guidelines:**

* `bugsnag-get-error` is on the bugsnag server. `zendesk-get-ticket` and `zendesk-get-ticket-comment` are on the zendesk server.
* This prompt is read-only. Do NOT call `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `zendesk-add-ticket`, `bugsnag-update-error-severity`, `bugsnag-assign-error` or any other write tool on either server.
* Bugsnag's users count is how many end users saw the error. It is not a count of tickets; report both separately.

**Validation:**

* If the error's users count is high but no tickets match, say that directly. It usually means customers describe it in words the fragments missed, so suggest two alternative fragments.
* If a fragment returns more than 30 tickets, it is too generic. Replace it with a more specific one.
* Pass dates as YYYY-MM-DD.