Give the Bugsnag error to the person fixing the BugHerd task

**Objective:** Assign the Bugsnag error linked to task `{task-number}` in the BugHerd project `{project-name}` to the task's assignee.

How the two systems are linked: a BugHerd task created from a Bugsnag error carries "bugsnag:<error id>" in its external-id, and the Bugsnag error is linked to the task's admin-link with `bugsnag-link-error-issue`.

**Step 1: Read the task and its owner**

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`. If the external-id does not start with "bugsnag:", say the task is not linked to a Bugsnag error and stop. If the task has no assignee, say so and stop. Call `bugherd-get-users` to find the assignee's email.

**Step 2: Find the same person in Bugsnag**

Call `bugsnag-get-error` with `error-id` from the external-id, then `bugsnag-get-project` with `name` set to its project-name to get the Bugsnag project-id. Call `bugsnag-get-project-collaborator` with `project-id` and `collaborator-email` set to the assignee's email. If there is no match, say the person is not a collaborator on that Bugsnag project and stop.

**Step 3: Confirm, then write**

Show the error, the person and both projects, and wait for an explicit yes. Then call `bugsnag-assign-error` once with `project-id`, `error-id` and `assigned-collaborator-id`.

**Step 4: Report**

Confirm the assignment and give the error-url.

**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.
* The only write tool this prompt may call is `bugsnag-assign-error`, once, after the user confirms. Never add collaborators to a project here.

**Validation:**

* If the assignment fails, show the error.