Find Freshdesk tickets that have no BugHerd bug

**Objective:** Find Freshdesk tickets created in the last {lookback-days} days (default 14) that have no matching BugHerd task, and BugHerd tasks that point at a ticket which cannot be found, for BugHerd project {project-id}.

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

Call `freshdesk-get-tickets` with `created-at.from` set to today minus the lookback, and `type` set to {ticket-type} if given (default: do not filter by type). Keep `ticket-id`, `subject`, `status`, `priority`, `requester-email`.

**Step 2: Read the tasks (BugHerd server)**

Call `bugherd-get-tasks` with `project-id` {project-id} and no other filter. Keep `task-id`, `task-number`, `title`, `status`, `severity`, `external-id`.

**Step 3: Join**

Match each ticket to a task where the task `external-id` equals the ticket `ticket-id` (compare as text, ignore a leading "#"). A task whose `external-id` is empty cannot be matched this way: list those separately.

**Step 4: Report**

Three tables: tickets with no task (ticket-id, subject, status, priority); tasks whose `external-id` is not in the ticket list (task-number, title, external-id, note that the ticket may simply be older than the lookback); matched pairs (ticket-id, task-number, ticket status, task status). End with counts.

**Rules & Guidelines:**

* `freshdesk-get-tickets` is on the Freshdesk server; `bugherd-get-tasks` is on the BugHerd server.
* 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 either server returns nothing, say so and report only the other side.
* If a call fails because a server is not connected or the tool is inactive, say which and stop.