Turn a Chorus call's next step into a Pipedrive activity

**Objective:** Read the Chorus conversation `{conversation-id}`, pull out the agreed next step, and, after the user confirms, schedule it as one Pipedrive activity due `{due-in-days}` days from today (default 3), linked to the matching deal and contact.

**Step 1: Read the conversation in Chorus**

Call `chorus-get-engagements` with `conversation-id`. If nothing comes back, say so and stop. Keep `subject`, `date`, `account-name`, `opportunity-name` and `meeting-summary`.

From `meeting-summary`, identify the agreed next steps and who owns them. If the summary is empty or names no next step, say so and stop; do not invent one.

**Step 2: Find the records in Pipedrive**

Call `chorus-get-conversation-participants` with `conversation-id`, then `pipedrive-get-person` with `email` for each external participant. Pipedrive organizations and Chorus accounts are matched by company name only; there is no shared ID. Try an exact match first, then a contains match on the most distinctive word of the name (drop suffixes such as Inc, Ltd, LLC, GmbH). Treat a contains match as a probable match and say so in the report. Call `pipedrive-get-organization` with `name` = `account-name`, then `name.contains`. For the deal, call `pipedrive-get-deal` with `title.contains` = `opportunity-name` when set, otherwise with `organization-id` and `status` = `open`. If several deals match, ask which one.

**Step 3: Check for an existing follow-up**

Call `pipedrive-get-activity` with `deal-id` (or `person-id` when there is no deal) and `done` = false. If an open activity already covers this next step, show it and ask whether a second one is still wanted.

**Step 4: Propose, then wait**

Call `pipedrive-get-activity-type` with `active` = true and pick the type key that fits the next step (call, meeting, email or task). Show the user the proposed activity:

* subject, a short imperative such as "Send revised proposal to Acme"
* type key
* due date: today plus the number of days (as an ISO date)
* linked deal, person and organization, by name and ID
* note: the next steps quoted from the summary, then `From Chorus conversation {conversation-id} on <date>`

Say that the activity will be assigned to the user whose credentials the Pipedrive connector uses, since the tool has no owner field. Ask the user to confirm. Do not write until they say yes.

**Step 5: Write once**

Call `pipedrive-add-activity` exactly once with `subject`, `type`, `due-date`, `note` and whichever of `deal-id`, `person-id` and `org-id` were matched.

**Step 6: Confirm**

Call `pipedrive-get-activity` with the same `deal-id` or `person-id` and `subject.contains` to confirm the activity exists, and report its `activity-id` and due date.

**Rules & Guidelines:**

* `chorus-get-engagements` and `chorus-get-conversation-participants` are on the chorus server. `pipedrive-get-person`, `pipedrive-get-organization`, `pipedrive-get-deal`, `pipedrive-get-activity`, `pipedrive-get-activity-type` and `pipedrive-add-activity` are on the pipedrive server.
* The only permitted write is one `pipedrive-add-activity` call, after confirmation.
* Do NOT call `pipedrive-update-activity`, `pipedrive-update-deal`, `pipedrive-add-note`, `pipedrive-add-deal` or `pipedrive-add-person`.
* Never call any write tool on the chorus server (`chorus-add-moment`, `chorus-add-playlist-moment`, `chorus-create-playlist`, `chorus-update-moment`, `chorus-update-playlist`, `chorus-update-playlist-moment`, `chorus-export-recordings`, `chorus-export-scorecards`).

**Validation:**

* If the summary lists several next steps, propose one activity for the most important customer-facing step and list the rest in the note; do not create several activities.
* If no Pipedrive deal, person or organization matches, stop and report what was searched for.
* If `{due-in-days}` is empty or not a whole number, use 3.