Log Chorus calls in Salesforce as tasks with a follow-up

**Objective:** Log the Chorus conversation {conversation-id} in Salesforce as a completed task on the right opportunity or account, with the call summary in the comments. If {follow-up-days} is given, also draft an open follow-up task due that many days after the call for the next steps the summary names.

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

Call `chorus-get-engagements` with conversation-id = {conversation-id}. If nothing comes back, say so and stop. Then call `chorus-get-conversation-participants` with the same conversation-id.

**Step 2: Resolve the Salesforce records**

* **Account:** call `salesforce-get-account` with name = the conversation's account-name, falling back to name.contains. If it matches more than one account, list them and stop.
* **Opportunity:** call `salesforce-get-opportunity` with the account-id and closed = false. Use the one whose name matches the conversation's opportunity-name. If none matches, attach the task to the account instead.
* **Contact:** for each participant whose email domain differs from the rep's, call `salesforce-get-contact` with email. Use the first match as the task's contact and list the rest in the comments.
* **Rep:** call `salesforce-get-user` with email = the conversation's user-email. If there is no match, leave assigned-to-id empty.

**Step 3: Check for a duplicate**

Call `salesforce-get-task` with related-to-id = the opportunity or account id and subject.contains = the conversation's subject. If a matching task already exists, show it and ask whether to continue.

**Step 4: Show the draft and ask**

Show the task that will be created: subject "Chorus call: <conversation subject> (<date>)", status Completed, due-date = the conversation date, what-id, who-id, assigned-to-id, and comments made of the meeting-summary, the participant list and the line "Chorus conversation <conversation-id>". Show the follow-up task too, if one was asked for. Ask the user to confirm.

**Step 5: Write and confirm**

Only after the user says yes, call `salesforce-add-task` once for the logged call and once for the follow-up, if one was asked for. Then call `salesforce-get-task` with related-to-id to show the stored tasks.

**Rules & Guidelines:**

* `chorus-get-engagements` and `chorus-get-conversation-participants` are on the Chorus server. `salesforce-get-account`, `salesforce-get-opportunity`, `salesforce-get-contact`, `salesforce-get-user`, `salesforce-get-task` and `salesforce-add-task` are on the Salesforce server.
* `salesforce-add-task` is the only tool that may write, at most twice, and only after the user confirms the draft.
* Do not call `salesforce-update-opportunity`, `salesforce-add-contact`, `salesforce-update-task` or any Chorus write tool.

**Validation:**

* If the conversation has no meeting-summary, write the comments from its subject and participants, and say the summary was missing.
* If no external participant matches a Salesforce contact, leave who-id empty and say so in the draft.
* If `salesforce-add-task` does not return success, report the error and do not retry.