Turn promises on a Chorus donor call into Bloomerang tasks

**Objective:** Read the Chorus conversation `{conversation-id}`, pull out the follow-ups promised to the donor, and create them as Bloomerang tasks assigned to Bloomerang user `{assign-to-user-id}`, due `{due-in-days}` days after the conversation (default 7) unless the summary names a date.

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

Call `chorus-get-engagements` with `conversation-id` set to `{conversation-id}`. If it returns nothing, or `meeting-summary` is empty, say there is nothing to work from and stop. Note `date`, `subject`, `user-name` and `meeting-summary`.

**Step 2: Identify the donor**

Call `chorus-get-conversation-participants` with `conversation-id`. Keep external participants (no `user-id`, not typed as internal). Match each one's `email` with `bloomerang-get-email-address` (`value`) and take `account-id`. If more than one constituent matches, ask the user which one the tasks belong to. If none match, list the participants and stop.

**Step 3: Draft the tasks**

From `meeting-summary`, list each concrete commitment made to the donor (send a report, schedule a visit, share a proposal). Ignore general discussion. For each, draft: `subject` (under 60 characters), `note` (the commitment in the summary's own words, followed by "From Chorus conversation {conversation-id}"), `due-date`, and `channel` where the commitment implies one.

**Step 4: Skip duplicates**

Call `bloomerang-get-task` with `account-id` and `status` Open. Drop any drafted task whose subject already matches an open task, and say which were dropped.

**Step 5: Confirm, then write**

Show the drafted tasks as a table and ask the user to confirm, edit or drop each. Only after an explicit yes, call `bloomerang-add-task` for each approved task with `account-id`, `user-id` `{assign-to-user-id}` and the drafted fields. Report each returned `id`.

**Rules & Guidelines:**

* Tools whose names start with chorus are on the chorus server; tools whose names start with bloomerang are on the bloomerang server.
* The only write this prompt may make is `bloomerang-add-task`, and only after confirmation. Do not call `bloomerang-add-interaction`, `bloomerang-add-note`, `bloomerang-update-task` or any Chorus action such as `chorus-add-moment`.
* Do not invent commitments the summary does not state.

**Validation:**

* If the summary contains no commitments, say so and write nothing.
* `due-date` is an ISO date (for example 2026-03-01). Chorus dates carry a time; use the calendar day.
* If `bloomerang-add-task` rejects `{assign-to-user-id}`, report the error and stop; do not try other user ids.