Find the Bugsnag error behind a customer's Zendesk ticket

**Objective:** Find the Bugsnag errors most likely behind Zendesk ticket `{ticket-id}`, searching Bugsnag project `{project-name}` (default: all projects).

**Step 1: Read the ticket**

Call `zendesk-get-ticket` with ticket-id `{ticket-id}`. If nothing comes back, report that the ticket does not exist and stop. Note the subject, requester, organization and created-date.

Then call `zendesk-get-ticket-comment` with ticket-id `{ticket-id}` and read every comment. Pull out the evidence a Bugsnag search can use: quoted error messages, exception or class names (for example NullReferenceException, TypeError), page or screen names, URLs, app versions, and when the customer says it happened.

If the ticket carries no technical evidence at all (no message, no page, no version), say so, list what the agent should ask the customer for, and stop.

**Step 2: Search Bugsnag with that evidence**

For each distinct message or class you found, call `bugsnag-get-error` with `message.contains` or `error-class.contains` set to the shortest distinctive fragment (a few words, not the full sentence), `last-seen.from` set to 7 days before the ticket's created-date, and `project-name` set to `{project-name}` when it was given.

If the ticket names a page or URL but no message, call `bugsnag-get-event` with `received.from` and `received.to` spanning 2 days either side of when the customer says it happened (or the ticket's created-date), and look for events whose request-url or context matches that page. Use `app-version` too when the ticket gives one.

**Step 3: Rank the candidates**

For each candidate error, judge the match on: wording overlap with the ticket, timing (was the error seen around when the customer reported it), page or context match, and version match. Rate each High, Medium or Low. Drop Low matches unless nothing better exists.

**Step 4: Report**

* One line summarizing the ticket: id, subject, requester, organization, created-date.
* A table of candidate errors: error-id, error-class, message (trimmed), project-name, status, severity, events, last-seen-date, match rating, and why it matches.
* The error-url of the best match, written as plain text.
* If no candidate rated Medium or better, say plainly that no Bugsnag error matches this ticket and list the search terms you tried.

**Rules & Guidelines:**

* `zendesk-get-ticket` and `zendesk-get-ticket-comment` are on the zendesk server. `bugsnag-get-error` and `bugsnag-get-event` are on the bugsnag server.
* This prompt is read-only. Do NOT call `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `bugsnag-link-error-issue`, `bugsnag-assign-error`, `bugsnag-open-error`, `bugsnag-fix-error` or any other write tool on either server.
* Search with short fragments. Customers paraphrase error text, so a full-sentence match will usually miss.

**Validation:**

* If Bugsnag returns more than 20 errors for a fragment, it is too generic. Narrow it with `error-class.contains` or a tighter date window rather than reporting all of them.
* Dates: pass dates to both servers as YYYY-MM-DD.
* Never present a Low match as the cause. Say it is a possibility.