Record webinar attendance on Salesforce contacts and leads

**Objective:** Record attendance at the GoTo Webinar webinar `{webinar}` in Salesforce by creating one task per attending contact or lead, with status `{task-status}` (default Completed), without creating duplicates.

**Step 1: Find the webinar**

Call `goto-webinar-get-webinar` (GoTo Webinar) with `webinar-name.contains` set to `{webinar}`. If `{webinar}` is all digits, filter by `webinar-key` instead. If more than one webinar matches, list each one's webinar-name, date and webinar-key and stop so the user can choose. If none match, say so and stop. Keep the `webinar-key`, `webinar-name` and `date`.

**Step 2: Read the attendees**

Call `goto-webinar-get-attendee` (GoTo Webinar) with `webinar-key`. Keep email, first-name, last-name, `total-time-attended` and `date-attended`. Drop rows with a blank email and count them.

**Step 3: Match each attendee in Salesforce**

Match each email address to Salesforce in this order, and stop at the first hit:
1. `salesforce-get-contact` (Salesforce) with `email` set to the address. A hit is a contact: keep `contact-id`, `name`, `account-name`, `account-id` and `owner`.
2. `salesforce-get-lead` (Salesforce) with `email` set to the address. A hit is a lead: keep `lead-id`, `name`, `company`, `status`, `converted` and `owner`. Ignore leads where `converted` is true when a contact also matched.
3. No hit on either: the person is unknown to Salesforce.

Compare addresses case-insensitively and trimmed. Never match on name alone. If one address matches more than one contact, or more than one unconverted lead, mark the person "ambiguous" and list every match rather than picking one.

Unknown and ambiguous attendees get no task; list them in the report. For a match, the Salesforce id to log against is the contact-id or lead-id.

**Step 4: Skip anyone already logged**

For each match, call `salesforce-get-task` (Salesforce) with `name-id` set to that id and `subject.contains` set to the webinar-name. If a task comes back, mark the person "already logged" and skip them.

**Step 5: Confirm**

Show a table: name, email, contact or lead, Salesforce id, minutes attended, and whether a task will be created. STOP and ask the user to confirm. Create nothing until they do.

**Step 6: Create the tasks**

After confirmation, call `salesforce-add-task` (Salesforce) once per confirmed row with:
- `who-id`: the contact-id or lead-id
- `subject`: "Attended webinar: " followed by the webinar-name
- `status`: `{task-status}` (default Completed)
- `due-date`: the date-attended
- `comments`: minutes attended and the webinar date
If a call fails, record the error and continue.

**Step 7: Report**

Counts for created, already logged, unknown, ambiguous and failed, then a table of created tasks with their returned ids.

**Rules & Guidelines:**

* Tools starting goto-webinar- are on the GoTo Webinar server; tools starting salesforce- are on the Salesforce server. Both must be connected.
* The only write this prompt may make is `salesforce-add-task`, after the user confirms in Step 5.
* Do NOT call `salesforce-update-task`, `salesforce-add-lead`, `salesforce-add-contact`, `salesforce-update-contact` or `salesforce-update-lead`. Do NOT call `goto-webinar-add-registrant` or `goto-webinar-delete-registrant`.

**Validation:**

* If the webinar has no attendees, say so and stop.
* If the task-status value is rejected by Salesforce, stop after the first failure, report the error, and ask the user for a valid status instead of retrying every row.