Trace a contact across Freshdesk tickets and Chorus calls

**Objective:** Trace the person with email `{email}` across Freshdesk and Chorus and report everything they have raised and discussed, looking back `{lookback-days}` days (default 90).

**Step 1: Identify the contact (Freshdesk)**

Call `freshdesk-get-contacts` with `email` set to `{email}`. Record contact-id, name, company-id, job-title and csat-rating. If no contact matches, note it and continue; use `{email}` directly as the requester email.

**Step 2: Their tickets (Freshdesk)**

Call `freshdesk-get-tickets` with `requester-email` set to `{email}` and `created-at.from` set to the lookback start. List ticket-id, subject, status, priority, created-at.

**Step 3: Their calls and emails (Chorus)**

Call `chorus-get-conversation-participants` with `email` set to `{email}`. For each conversation-id returned, call `chorus-get-engagements` with `conversation-id` to get date, subject and meeting-summary. Also call `chorus-get-emails` with `initiator-email` set to `{email}` and `sent-time.from` set to the lookback start.

**Step 4: Report**

Produce one chronological timeline merging tickets, calls and emails (date, system, what happened), then a two-sentence read on the relationship and any ticket that was open when a call took place.

**Rules & Guidelines:**

* `freshdesk-get-contacts` and `freshdesk-get-tickets` are on the freshdesk server; `chorus-get-conversation-participants`, `chorus-get-engagements` and `chorus-get-emails` are on the chorus server.
* The join is the email address; compare case-insensitively.
* Do not call any create, update, delete, reply or note tool on either server (for example `freshdesk-add-ticket`, `freshdesk-update-ticket`, `freshdesk-add-ticket-note`, `freshdesk-reply-to-ticket`, `chorus-add-moment`, `chorus-update-moment`).

**Validation:**

* If the person appears in only one system, say so and report that side.
* If several contacts share the email, list them and stop.