Log each Chorus call on the right Pipedrive record, never twice

**Objective:** Take the Chorus conversation `{conversation-id}` and, after the user confirms, add its summary to Pipedrive as a note attached to `{attach-to}` (deal, person or organization; default: the matching deal if there is exactly one, otherwise the organization).

**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`, `conversation-type`, `duration`, `account-name`, `opportunity-name`, `user-name` and `meeting-summary`.

Call `chorus-get-conversation-participants` with the same `conversation-id` and keep each participant's `name`, `email`, `company-name` and `type`.

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

* People: for each external participant with an email, call `pipedrive-get-person` with `email`.
* 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. Call `pipedrive-get-organization` with `name` = `account-name`, then `name.contains`.
* Deal: if `opportunity-name` is set, call `pipedrive-get-deal` with `title.contains`. Otherwise call `pipedrive-get-deal` with `organization-id` and `status` = `open`.

If `{attach-to}` names a record type that has no single match, list the candidates and ask the user to choose.

**Step 3: Check it is not already logged**

Call `pipedrive-get-note` on the chosen record (`deal-id`, `person-id` or `organization-id`) with `note.contains` = `{conversation-id}`. If a note exists, show it and stop; do not add a duplicate.

**Step 4: Propose, then wait**

Show the user the target record (type, name, ID) and the full note text:

* first line: `Chorus <conversation-type>: <subject> (<date>, <duration>)`
* participants, by name and company
* the `meeting-summary`, unedited
* last line: `Chorus conversation ID: {conversation-id}`

Ask the user to confirm. Do not write until they say yes. If they change the target or the text, show the revised version and ask again.

**Step 5: Write once**

Call `pipedrive-add-note` exactly once, with `content` and exactly one of `deal-id`, `person-id` or `org-id`.

**Step 6: Confirm**

Call `pipedrive-get-note` again as in Step 3 and report the new `note-id`.

**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-note` and `pipedrive-add-note` are on the pipedrive server.
* The only permitted write is one `pipedrive-add-note` call, after confirmation.
* Do NOT call `pipedrive-add-person`, `pipedrive-add-organization`, `pipedrive-add-deal`, `pipedrive-add-activity`, `pipedrive-update-note` or any other pipedrive update tool.
* 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 conversation has no `meeting-summary`, say so and offer a note with the header and participants only; still wait for confirmation.
* If no Pipedrive organization, person or deal matches, stop and report the account name and participant emails, so the user can create the records first (`add-call-participants-to-pipedrive` covers the people).