Add Chorus call people to Pipedrive without touching existing ones

**Objective:** Find the external participants in the Chorus conversation `{conversation-id}` who are not yet Pipedrive contacts, and, after the user confirms, create them as Pipedrive people linked to their organization.

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

Call `chorus-get-engagements` with `conversation-id` to confirm the conversation exists and keep its `subject`, `date` and `account-name`. If nothing comes back, say so and stop.

Call `chorus-get-conversation-participants` with `conversation-id`. Keep participants whose `type` marks them as external. If `type` is blank, treat a participant as internal when `chorus-get-users` with their `email` returns a user.

**Step 2: Check each one in Pipedrive**

For each external participant with an email, call `pipedrive-get-person` with `email`. Found means they already exist; record their `person-id` and leave them alone. Participants with no email are skipped and listed as such.

**Step 3: Find their organization**

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. For each missing participant, call `pipedrive-get-organization` with `name` = their `company-name` (or the conversation's `account-name` when that is blank), then `name.contains`. Keep the `organization-id` when there is exactly one match. When there is none or several, leave the organization empty and say so. Never create an organization.

**Step 4: Propose, then wait**

Show a table of the people you intend to create: name, work email, organization (name and ID, or "none"). Below it, list the participants who already exist and the ones skipped for having no email.

Ask the user to confirm. They may remove rows or correct names. Do not write until they say yes.

**Step 5: Write**

For each confirmed row, call `pipedrive-add-person` once with `name`, `work-email` and `org-id` when known. Stop at the first failure and report which rows were created and which were not.

**Step 6: Confirm**

Call `pipedrive-get-person` with `email` for each created person and report the new `person-id` values.

**Rules & Guidelines:**

* `chorus-get-engagements`, `chorus-get-conversation-participants` and `chorus-get-users` are on the chorus server. `pipedrive-get-person`, `pipedrive-get-organization` and `pipedrive-add-person` are on the pipedrive server.
* The only permitted write is `pipedrive-add-person`, once per confirmed row.
* Do NOT call `pipedrive-update-person`: passing any email to it replaces all of that person's email addresses.
* Do NOT call `pipedrive-add-organization`, `pipedrive-add-deal`, `pipedrive-add-lead` or `pipedrive-add-note`.
* 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:**

* Never add an internal participant (one of our own users).
* Match on email only. A Pipedrive person with the same name but a different email is a different person; mention the near-match in the table so the user can decide.
* If every external participant already exists, say so and stop without writing.