Log Chorus calls on Dynamics 365 Sales with a follow-up task

**Objective:** Take the Chorus conversation `{conversation-id}`, record its summary as a note on the Dynamics 365 Sales record `{record-id}`, and create one follow-up task due in `{follow-up-days}` working days (default 2).

**Step 1: Read the conversation (Chorus)**

Call `chorus-get-engagements` with `conversation-id` = `{conversation-id}`. If nothing comes back, say so and stop. Keep `subject`, `date`, `duration`, `account-name`, `opportunity-name`, `user-name` and `meeting-summary`. Call `chorus-get-conversation-participants` with the same `conversation-id` for the attendee list.

**Step 2: Find the CRM record (Dynamics 365 Sales)**

If `opportunity-name` is set, call `dynamics-365-sales-get-opportunities` with `topic` = that name; otherwise call `dynamics-365-sales-get-accounts` with `account-name` = the conversation's `account-name`. Show the match so the user can confirm it is the record `{record-id}` belongs to.

Then call `dynamics-365-sales-get-annotations` with `regarding` = that record's name and `created-on.from` = the conversation date, and check that no note already covers this conversation. If one does, show it and stop unless the user says to continue.

**Step 3: Draft and confirm**

Draft:

* the note: title "Chorus: <subject> (<date>)"; text with the attendees, the decisions and next steps from `meeting-summary` as short bullets, and the Chorus conversation id
* the task: a subject naming the single most important next step, due in `{follow-up-days}` working days

Show both and ask for one confirmation.

**Step 4: Write (Dynamics 365 Sales)**

1. `dynamics-365-sales-create-note` with `regarding-id` = `{record-id}`, `title` and `text`.
2. `dynamics-365-sales-create-task` with `subject`, `due-date`, `description`, and `regarding-id` = `{record-id}`.

Report what was created.

**Rules & Guidelines:**

* `chorus-get-engagements` and `chorus-get-conversation-participants` are on the Chorus server. `dynamics-365-sales-get-opportunities`, `dynamics-365-sales-get-accounts`, `dynamics-365-sales-get-annotations`, `dynamics-365-sales-create-note` and `dynamics-365-sales-create-task` are on the Dynamics 365 Sales server.
* No Dynamics 365 read tool returns a record's GUID. `{record-id}` must come from the user: it is the `id=` value in the browser address bar when the record is open in Dynamics 365. Never invent, reuse or guess one.
* If `{record-id}` is blank, skip the note (a note must belong to a record), create the task without `regarding-id`, and tell the user it is not linked.
* The only write tools this prompt may call are `dynamics-365-sales-create-note` and `dynamics-365-sales-create-task`, each once, after the confirmation. Do not call any Chorus action tool.
* Put nothing in the note that is not in the Chorus summary.

**Validation:**

* If `meeting-summary` is empty, say the conversation has no summary in Chorus and ask the user for the key points instead of inventing them.