Log one Chorus meeting on every donor who attended

**Objective:** Log the Chorus conversation `{conversation-id}` as an interaction in Bloomerang for every external participant who is a Bloomerang constituent, using purpose `{purpose}` (if empty, ask the user for the purpose before writing anything).

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

Call `chorus-get-engagements` with `conversation-id` set to `{conversation-id}`. If it returns nothing, say the conversation was not found and stop. Note `date`, `subject`, `conversation-type`, `user-name` and `meeting-summary`.

Call `chorus-get-conversation-participants` with `conversation-id` set to `{conversation-id}`. Keep only external participants: skip anyone with a `user-id` (a Chorus user on your own team) and anyone whose `type` marks them as internal.

**Step 2: Match each participant to Bloomerang**

For each external participant with an `email`, call `bloomerang-get-email-address` with `value` set to that email and take `account-id`. If nothing comes back, try `bloomerang-get-constituent` with `primary-email`. Participants with no email, or no match, are listed as unmatched and not logged.

**Step 3: Check for an existing entry**

For each matched account id, call `bloomerang-get-interaction` with `account-id` and with `date.from` and `date.to` both set to the conversation's calendar date. If an interaction already exists with a similar subject, mark that constituent as already logged and do not log it again.

**Step 4: Confirm, then write**

Show a table: participant name, email, Bloomerang account id, action (log / already logged / unmatched). Show the interaction that will be written: `date` (calendar day of the conversation), `channel` (Phone for a call, InPerson for an in-person meeting, otherwise ask), `purpose` `{purpose}`, `subject` (the Chorus subject), `is-inbound` false, and `note` (the meeting summary, followed by "Recorded in Chorus, conversation {conversation-id}, led by <user-name>").

Ask the user to confirm. Only after an explicit yes, call `bloomerang-add-interaction` once per constituent marked log. Then 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-interaction`, and only after confirmation. Do not call `bloomerang-add-note`, `bloomerang-add-task`, `bloomerang-add-constituent`, `bloomerang-update-interaction` or any Chorus action such as `chorus-add-moment`.
* Never create a constituent for an unmatched participant here; list them so the user can run a separate prompt.

**Validation:**

* If no external participant matches Bloomerang, report the unmatched list and write nothing.
* If `bloomerang-add-interaction` rejects the channel or purpose value, report the error exactly and ask the user for a valid value rather than trying others.
* Match emails case-insensitively.