Turn Chorus call commitments into Teamwork.com tasks

**Objective:** Turn the action items from the Chorus conversation `{conversation-id}` into tasks in the client's Teamwork project, in the task list `{tasklist-name}` if given, after the user confirms.

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

Call `chorus-get-engagements` with `conversation-id` set to `{conversation-id}`. Keep `subject`, `date`, `account-name`, `opportunity-name` and `meeting-summary`. Call `chorus-get-conversation-participants` with the same `conversation-id` to know who was on the call. If the engagement has no `meeting-summary`, stop and say there is nothing to extract.

**Step 2: Extract the actions**

From `meeting-summary`, list each concrete commitment: what must be done, who said they would do it, and any date mentioned. Leave out discussion points that are not commitments.

**Step 3: Find the project and task list in Teamwork**

Call `teamwork-get-projects` with `company-name.contains` set to the distinctive part of `account-name`, keeping projects that are not completed. If several match, list them and ask. Then call `teamwork-get-tasklists` with that `project-id`. Use the list whose name matches `{tasklist-name}`; if none was given, propose the most relevant open list by name and say which. If no list fits, stop and ask.

**Step 4: Avoid duplicates**

Call `teamwork-get-tasks` with `task-list-id` and `name.contains` set to a key word from each action. Drop any action that already has an open task.

**Step 5: Confirm**

Show the proposed tasks: name, description (ending "From Chorus call <subject> on <date>"), due date if one was stated, and priority. Name the person each action belongs to in the description, because tasks cannot be assigned from here. Ask the user to confirm, edit or drop. Do not write until they confirm.

**Step 6: Write and confirm**

For each confirmed task call `teamwork-create-task` once with `tasklist-id`, `name`, `description`, `due-date` and `priority`. Report each returned `id`.

**Rules & Guidelines:**

* `chorus-get-engagements` and `chorus-get-conversation-participants` are on the chorus server. `teamwork-get-projects`, `teamwork-get-tasklists`, `teamwork-get-tasks` and `teamwork-create-task` are on the teamwork server.
* `teamwork-create-task` is the only tool that may write, and only after confirmation. Do not call `teamwork-create-tasklist`, `teamwork-update-task`, `teamwork-create-message` or any chorus write tool.
* Do not invent actions the summary does not contain.

**Validation:**

* If the call has no `account-name`, ask which Teamwork project to use instead of guessing.
* If every action already has a task, say so and stop without writing.