Find the Bugsnag error behind a BugHerd bug report

**Objective:** Find the Bugsnag errors behind task `{task-number}` in the BugHerd project `{project-name}`, searching `{window-hours}` hours (default 2) either side of when it was reported.

**Step 1: Read the task**

Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If several match, list their names and project-id values and ask which one; do not guess. Then call `bugherd-get-tasks` with `project-id` and `task-number` (then `bugherd-get-feedback`). If it is not found, stop. Note the page, created date and requester-email.

**Step 2: Search the events**

Call `bugsnag-get-event` with `received.from` and `received.to` set to the window around the created date and `max-records` 500. Keep events whose request-url matches the task's page. Match pages by URL: compare host and path, ignoring the scheme, a leading "www.", a trailing slash, the query string and the fragment. If none match, widen to events on the same host and say so.

**Step 3: Read the errors**

Group the kept events by error-id. For each, call `bugsnag-get-error` with `error-id`: message, error-class, severity, status, events, users, first-seen-date and error-url.

**Step 4: Report**

* **Most likely cause:** the error with events closest in time to the report on the same page, and why.
* **All candidates:** a table with error-class, message, events in the window, total users, status, error-url.
* **Fit:** say whether the error plausibly explains what the task describes, or whether it is only nearby noise.
* Suggest `log-bugsnag-error-in-bugherd` if a strong candidate has no BugHerd task yet.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named bugsnag-... are on the bugsnag MCP server. If either set of tools is missing, say which server is not connected and stop.
* This prompt is read-only. Do not call any BugHerd write tool (`bugherd-add-task`, `bugherd-add-feedback`, `bugherd-update-task`, `bugherd-move-task`, `bugherd-add-comment`, `bugherd-add-attachment-from-url`, `bugherd-add-project`, `bugherd-update-project`, `bugherd-add-project-member`, `bugherd-add-guest-to-project`) or any Bugsnag write tool (`bugsnag-link-error-issue`, `bugsnag-create-error-issue`, `bugsnag-fix-error`, `bugsnag-open-error`, `bugsnag-ignore-error`, `bugsnag-discard-error`, `bugsnag-assign-error`, `bugsnag-update-error-severity`, `bugsnag-update-project`, `bugsnag-add-project`, `bugsnag-add-project-collaborator`).

**Validation:**

* If the task has no page, search the whole window and say the match is by time only.
* If no events fall in the window, say so: the bug is likely visual or behavioural rather than a code exception.