Turn overdue Stripe invoices into HubSpot collection tasks

**Objective:** For Stripe invoices that are open and past due, and for charges that failed in the last `{lookback-days}` days (default 7), create one HubSpot collection task per invoice on the customer's contact and company, at most `{max-records}` tasks (default 25). Nothing is written until the user confirms.

**Step 1: Find payment problems in Stripe**

Call `stripe-get-invoice` with `status` set to open, `due-date.to` set to today and `max-records` 200. Keep `invoice-id`, `number`, `customer-email`, `customer-name`, `amount-remaining`, `currency`, `due-date` and `hosted-invoice-url`.

Call `stripe-get-charge` with `status` set to failed, `created.from` set to today minus `{lookback-days}` days (7 if empty) and `max-records` 200. For a failed charge with an `invoice-id` not already kept, call `stripe-get-invoice` with `invoice-id` set to it; if that invoice is now paid, the payment recovered and is left out. Otherwise keep the invoice with the charge's `failure-message`. A failed charge with no invoice is listed for information only.

Amounts are in minor units: divide by 100 (not for zero-decimal currencies such as JPY).

**Step 2: Find the customer in HubSpot**

The join is the Stripe `customer-email` against the HubSpot contact `email`, compared case-insensitively after trimming. Call `hubspot-get-contacts` with `email` set to it and keep `record-id` and `company-id`. If no contact comes back, call `hubspot-get-companies` with `company-domain-name` set to the email's domain (skip free mail domains such as gmail.com, outlook.com, yahoo.com and hotmail.com) and keep its `record-id`. If nothing matches, or several records match, list the invoice as unmatched and do not create a task for it.

**Step 3: Skip invoices that already have a task**

Call `hubspot-get-tasks` with `task-title.contains` set to the invoice `number`. If a task comes back whose `task-status` is not completed, skip the invoice and show that task.

**Step 4: Confirm**

Show a table, largest amount first and at most `{max-records}` rows (25 if empty): customer, email, invoice number, amount remaining and currency, due date, latest failure message, and the HubSpot record it will be linked to. Ask for an explicit yes and offer to exclude rows. Do not continue without a yes.

**Step 5: Write and verify**

For each confirmed invoice, call `hubspot-add-task` once with `subject` set to "Collect Stripe invoice <number>", `body` set to the amount remaining, currency, due date, failure message and hosted invoice link, `due-date` today, `status` NOT_STARTED, `priority` HIGH, `type` TODO, `contact-ids` set to the contact `record-id` when there is one, and `company-ids` set to the company id when there is one. Leave `owner-id` unset unless the user gives a numeric HubSpot owner ID. Then call `hubspot-get-tasks` with `task-title.contains` set to each number and confirm the task exists. Report created, failed and skipped rows.

**Rules & Guidelines:**

* `stripe-get-invoice` and `stripe-get-charge` are on the stripe server; `hubspot-get-contacts`, `hubspot-get-companies`, `hubspot-get-tasks` and `hubspot-add-task` are on the hubspot server.
* The only write tool allowed is `hubspot-add-task`, once per confirmed invoice and only after the confirmation in Step 4. Call no other hubspot-add, hubspot-update, hubspot-rename, hubspot-remove, hubspot-subscribe, hubspot-unsubscribe or hubspot-import tool, and do not use the engagement task tools.
* The stripe server has no write tools; only the stripe read tools named here are used, and nothing is charged, refunded or sent to the customer.
* Never put card numbers or bank details in a task. Keep the subject format exactly as given; the complete-paid-stripe-invoice-tasks prompt finds these tasks by it.

**Validation:**

* If Stripe shows no overdue invoice and no failed charge, say so and stop.
* If the user declines or does not answer, stop with nothing written.
* Never create a second open task for the same invoice number. Never match on a name alone.