Get the people from your Chorus calls into Bloomerang

**Objective:** Find the external people on Chorus conversations in the last `{lookback-days}` days (default 30), optionally only those whose company name contains `{company-name}`, who cannot be matched to a Bloomerang constituent by email, and offer to fix each one.

**Step 1: Collect the external participants in Chorus**

Call `chorus-get-engagements` with `date.from` set to the start of the window and `max-records` 25. For each conversation, call `chorus-get-conversation-participants` with its `conversation-id` (and `company-name.contains` `{company-name}` if given). Keep external participants only (no `user-id`, not typed as internal) and de-duplicate by email.

**Step 2: Match against Bloomerang**

For each participant:

1. Call `bloomerang-get-email-address` with `value` set to their email. A result means they are already known; drop them.
2. Otherwise call `bloomerang-get-constituent` with `full-name.contains` set to their surname. If exactly one constituent comes back whose full name matches the participant's name, mark them **probable match, email missing** with that constituent's `id`.
3. Otherwise mark them **not in Bloomerang**.

**Step 3: Report and propose**

Show two tables: probable matches (participant name, email, company, Bloomerang constituent name and id), and people not in Bloomerang (name, email, title, company, the conversation date and subject they were on).

Propose, per row: for a probable match, add the email with `bloomerang-add-email-address` (`account-id` the constituent id, `email`, `type` Work, `is-primary` false); for someone not in Bloomerang, create them with `bloomerang-add-constituent` (`type` Individual, `first-name`, `last-name`, `email`).

**Step 4: Write only what is approved**

Ask the user to approve rows individually. Only after an explicit yes for a row, make that row's single call. 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 writes this prompt may make are `bloomerang-add-email-address` and `bloomerang-add-constituent`, each only for an approved row. Do not call `bloomerang-update-constituent`, `bloomerang-add-household`, `bloomerang-add-interaction` or any Chorus action.
* Never treat a name match as certain; it is always shown as probable and needs approval.

**Validation:**

* If every participant already matches, say so and write nothing.
* Match emails case-insensitively. Skip participants with no email and count them in the report.
* If a write returns an error, report it for that row and continue with the others.