Find the BugHerd bug behind a Freshdesk ticket

**Objective:** Trace Freshdesk ticket {ticket-id} to the BugHerd task or tasks raised for it in project {project-id}, and show both sides of the story.

**Step 1: Read the ticket (Freshdesk server)**

Call `freshdesk-get-tickets` with `ticket-id` {ticket-id}. If nothing comes back, say the ticket does not exist and stop. Keep `subject`, `status`, `priority`, `requester-email`, `created-at`.

**Step 2: Find the linked tasks (BugHerd server)**

Call `bugherd-get-tasks` with `project-id` {project-id} and `external-id` {ticket-id}. If nothing matches, call it again with `requester-email` set to the ticket's `requester-email` and list those as possible matches, clearly marked as unconfirmed.

**Step 3: Read the discussion (BugHerd server)**

For each confirmed task, call `bugherd-get-comments` with `project-id` {project-id} and `task-id` set to that task's `task-id`. Skip comments where `private` is true unless the person asked for them.

**Step 4: Report**

Ticket summary, then each linked task (task-number, title, status, severity, assignee), then its comments in date order, then one line saying whether the ticket and task statuses agree.

**Rules & Guidelines:**

* `freshdesk-get-tickets` is a Freshdesk tool; `bugherd-get-tasks` and `bugherd-get-comments` are BugHerd tools.
* Do not call any write tool on either server: nothing from the add-, update-, delete-, move-, reply- or note families, including `freshdesk-add-ticket-note`, `freshdesk-reply-to-ticket`, `freshdesk-update-ticket`, `bugherd-add-task`, `bugherd-update-task` and `bugherd-add-comment`.

**Validation:**

* If no task is linked, say the ticket has no bug on record and stop after the possible matches.