Warn deal owners about support problems before close

**Objective:** For open Salesforce opportunities closing in the next {close-within-days} days (default 90), find those whose customer has unsolved `urgent` or `high` Zendesk tickets, or a `bad` satisfaction rating in the last 60 days, and after the user confirms, log one risk task on each such opportunity in Salesforce.

**Step 1: Open opportunities in Salesforce**

Call `salesforce-get-opportunity` with `closed` set to false, `close-date.from` set to today and `close-date.to` set to today plus {close-within-days} days (default 90). Keep `opportunity-id`, `name`, `account-id`, `account-name`, `amount`, `stage`, `close-date` and `owner`. For each distinct `account-id`, call `salesforce-get-account` with `account-id` to get `name` and `website`. If there are no opportunities, say so and stop.

**Step 2: Match each account in Zendesk**

**How to match a Salesforce account to a Zendesk organization (use this order, stop at the first hit):**

1. Call `zendesk-get-organization` with `external-id` set to the Salesforce `account-id`.
2. If nothing comes back, call `zendesk-get-organization` with `name` set to the Salesforce account `name` exactly.
3. If still nothing, take the domain from the account's `website` (strip `http://`, `https://`, `www.` and any path) and call `zendesk-get-organization` with `domain-names.contains` set to it.
4. If more than one organization matches at any step, list them and treat the account as ambiguous rather than guessing.
5. If none match, report the account as "No Zendesk organization found" and continue with the next account.

Once matched, use the Zendesk organization's own `name` (not the Salesforce account name) as `organization-name` on `zendesk-get-ticket`, since the two systems can spell the company differently.

**Step 3: Risk signals in Zendesk**

* Zendesk unsolved tickets are those with status `new`, `open`, `pending` or `hold`. The `status` filter on `zendesk-get-ticket` takes one value, so call it once per status and combine the results. Keep only `urgent` and `high` tickets.
* Call `zendesk-get-ticket` with `organization-name` and `created.from` set to 60 days ago, then call `zendesk-get-satisfaction-rating` with `ticket-id` for each (at most 25) and keep `bad` scores with their `comment`.

An opportunity is at risk when its account has at least one of these signals.

**Step 4: Avoid duplicates**

For each at-risk opportunity, call `salesforce-get-task` with `related-to-id` set to the `opportunity-id`, `closed` set to false and `subject.contains` set to `Support risk`. Skip opportunities that already have one.

**Step 5: Propose, then confirm**

Show one table and STOP for confirmation:

| Opportunity | Account | Amount | Stage | Close date | Urgent/high unsolved | Bad ratings | Proposed subject |

The subject is `Support risk: <N> urgent/high tickets open before close`. Ask the user to confirm all, pick some, or cancel. Do not create anything until they answer.

**Step 6: Create the tasks in Salesforce**

For each confirmed opportunity only, call `salesforce-add-task` exactly once with `subject`, `what-id` set to the `opportunity-id`, `due-date` set to the earlier of today plus 3 days and the opportunity's `close-date`, `priority` set to `High`, and `comments` listing the ticket ids, subjects and any bad-rating comments. Report each returned `id`.

**Rules & Guidelines:**

* Salesforce tools start with "salesforce-" and come from the Salesforce MCP server. Zendesk tools start with "zendesk-" and come from the Zendesk MCP server. Both servers must be connected.
* The only write allowed is `salesforce-add-task`, once per confirmed opportunity, after the user confirms in Step 5.
* Do NOT call `salesforce-update-opportunity`, `salesforce-update-task`, `salesforce-add-case`, `zendesk-update-ticket`, `zendesk-add-ticket-comment` or `zendesk-update-organization`.

**Validation:**

* An account with no Zendesk organization is reported as "No Zendesk organization found" and gets no task.
* If `salesforce-add-task` returns `success` false, report it for that opportunity and continue; do not retry automatically.