Find the Jira issue behind a Freshdesk ticket

**Objective:** Find the Jira issue(s) that track Freshdesk ticket `{ticket-id}` and report where each one stands.

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

Call `freshdesk-get-tickets` with `ticket-id` = `{ticket-id}`. If nothing comes back, report that the ticket does not exist and stop. Note `subject`, `status`, `priority`, `requester-name` and `company-id`.

**Step 2: Search Jira for matching issues (jira server)**

Call `jira-get-issue` with `summary.contains` = `{ticket-id}`. If `{jira-project-key}` is not empty, also pass `project-key` = `{jira-project-key}`. Then call `jira-get-issue` again with `summary.contains` set to the most distinctive words of the ticket `subject` (same project filter). Merge the two result sets and remove duplicates by `issue-key`.

Also call `jira-get-issue-remote-link` with `application-name` = `Freshdesk` and keep any link whose `link-url`, `link-title` or `link-summary` mentions `{ticket-id}`.

**Step 3: Report**

A table of ticket id, ticket subject and status, then one row per candidate Jira issue: `issue-key`, `summary`, `status`, `assignee`, `due-date`, and how it matched (ticket id in summary, subject words, remote link). Mark remote link and ticket id matches as strong, subject-only matches as weak. If nothing matched, say so plainly: the ticket has no linked Jira issue.

**Rules & Guidelines:**

* `freshdesk-get-tickets` is on the freshdesk server; `jira-get-issue` and `jira-get-issue-remote-link` are on the jira server.
* Read only. Do not call any add, update, delete, assign, reply or note tool on either server, including `freshdesk-add-ticket-note`, `freshdesk-update-ticket`, `jira-add-issue` or `jira-add-issue-remote-link`.

**Validation:**

* If the jira search returns nothing, report the ticket as having no Jira issue and continue to the report.
* If more than 10 candidates return, show the 10 strongest and say how many were dropped.