See every Chorus conversation with a Pipedrive contact in one timeline

**Objective:** Build one timeline for the contact `{contact}` (an email address or a name), merging what Pipedrive has logged with what Chorus recorded, over the last `{lookback-days}` days (default 90), and point out conversations that were never logged in Pipedrive.

**Step 1: Find the person in Pipedrive**

If `{contact}` contains `@`, call `pipedrive-get-person` with `email`. Otherwise call it with `name`, then with `name.contains` if that returns nothing. If several people match, list them (name, organization, email) and stop. Keep `person-id`, `name`, `email` and `organization-name`.

If the person is not in Pipedrive but `{contact}` is an email address, continue with Chorus only and say the contact is missing from Pipedrive.

**Step 2: Find their Chorus conversations**

Call `chorus-get-conversation-participants` with `email` set to the person's email. For each distinct `conversation-id`, call `chorus-get-engagements` with `conversation-id`, and keep only the conversations whose `date` falls in the period.

**Step 3: Find their Chorus emails**

Call `chorus-get-emails` with `initiator-email` set to the person's email and `sent-time.from` = today minus the lookback.

**Step 4: Read what Pipedrive logged**

Call `pipedrive-get-call-log` with `person-id` and `start-time.from`, and `pipedrive-get-activity` with `person-id` and `due-date.from`, both set to the start of the period.

**Step 5: Report**

* A contact header: name, email, organization, Pipedrive person ID.
* One timeline, newest first, each row marked with its source (Pipedrive call, Pipedrive activity, Chorus conversation, Chorus email): date, subject, who on our side, and for Chorus conversations a one-line digest of `meeting-summary`.
* A list of Chorus conversations with no Pipedrive call log or activity on the same date. These are the unlogged ones; suggest running `log-conversation-to-pipedrive` for each, quoting its `conversation-id`.

**Rules & Guidelines:**

* `pipedrive-get-person`, `pipedrive-get-call-log` and `pipedrive-get-activity` are on the pipedrive server. `chorus-get-conversation-participants`, `chorus-get-engagements` and `chorus-get-emails` are on the chorus server.
* Match on email address only. Two people with the same name are not the same contact.
* This prompt is read-only. Do NOT call `pipedrive-add-deal`, `pipedrive-add-lead`, `pipedrive-add-person`, `pipedrive-add-organization`, `pipedrive-add-activity`, `pipedrive-add-note`, `pipedrive-update-deal`, `pipedrive-update-lead`, `pipedrive-update-person`, `pipedrive-update-organization`, `pipedrive-update-activity` or `pipedrive-update-note` on the pipedrive server.
* Do NOT call `chorus-add-moment`, `chorus-add-playlist-moment`, `chorus-create-playlist`, `chorus-update-moment`, `chorus-update-playlist`, `chorus-update-playlist-moment`, `chorus-export-recordings` or `chorus-export-scorecards` on the chorus server.

**Validation:**

* If the Pipedrive person has no email, say that Chorus cannot be searched reliably and stop after reporting the Pipedrive side.
* Compare dates by calendar day only; Pipedrive and Chorus may record times in different time zones.
* If neither system returns anything in the period, say so plainly.