Log a Salesforce follow-up on the right record, once

**Objective:** Create one follow-up task `{subject}` against the record `{record-name}`, due `{due-date}` (default: 3 business days from today), assigned to `{assigned-to}` (default: the owner of the record).

**Step 1: Resolve the record**

Look for `{record-name}` in this order and stop at the first single match: `salesforce-get-opportunity` by `name`, `salesforce-get-account` by `name`, `salesforce-get-contact` by `name` or `email`, `salesforce-get-lead` by `name` or `email`. If one lookup returns several, list them and stop.

* An opportunity or account supplies the what-id. A contact or lead supplies the who-id.
* For a contact, also set what-id to its account-id. Leave what-id empty for a lead.

**Step 2: Resolve the assignee**

Call `salesforce-get-user` with `name` set to `{assigned-to}`, or, when blank, to the record's owner. Require exactly one active user; use its user-id as assigned-to-id.

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

Call `salesforce-get-task` with `related-to-id` (or `name-id` for a contact or lead) and `closed` false. If an open task with a very similar subject exists, show it and ask whether to create another.

**Step 4: Confirm and create**

Show the exact values you will send and wait for the user to confirm before any write. If they change anything, show the revised values and confirm again. Then call `salesforce-add-task` once with subject, due-date, who-id and/or what-id, assigned-to-id, priority Normal, status Not Started.

**Step 5: Report**

The new task's ID and the values it was created with.

**Rules & Guidelines:**

* `salesforce-add-task` is the only write tool this prompt may call, and only once.
* Never guess an ID. Every ID must come from a read in this conversation.

**Validation:**

* If the record or user cannot be resolved to exactly one match, stop and say which.
* If `salesforce-add-task` reports success false, show the error and do not retry.