Put new BigCommerce subscribers on a HubSpot list

**Objective:** Put the HubSpot contacts of BigCommerce newsletter subscribers added in the last `{lookback-days}` days (default 30, at most `{max-records}`, default 50) into the manual HubSpot contact list named `{list-name}`, creating the list if it does not exist. Nothing is written until the user confirms.

**Step 1: Read subscribers from BigCommerce**

Call `bigcommerce-get-subscriber` with `date-created.from` set to today minus `{lookback-days}` days (30 if empty) and `max-records` set to `{max-records}` (50 if empty). Keep `id`, `email`, `first-name`, `last-name`, `source` and `date-created`.

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

The join is the BigCommerce subscriber `email` against the HubSpot contact `email`, compared case-insensitively after trimming. For each subscriber, call `hubspot-get-contacts` with `email` set to it and keep `record-id`. If none comes back, list the subscriber as not in HubSpot; if several come back, list them and leave the subscriber out. For each matched contact, call `hubspot-get-contact-subscriptions` with `recipient-email` set to the email and note any subscription whose `status` is not subscribed, so the user sees it.

**Step 3: Find or plan the list in HubSpot**

Call `hubspot-get-lists` with `name` set to `{list-name}` and `object-type` set to 0-1. If one comes back and its `processing-type` is MANUAL, use its `list-id` and call `hubspot-get-contact-list-membership` with `list-id` set to it to drop contacts already in it. If it comes back with any other processing type, say it cannot be changed and stop. If none comes back, plan to create it.

**Step 4: Confirm**

Show the list (existing, with its size, or to be created), the contacts to add (name, email, source, signup date, and a flag where HubSpot shows them unsubscribed), and the subscribers not in HubSpot. Ask for an explicit yes and offer to exclude rows. Do not continue without a yes.

**Step 5: Write and verify**

If the list must be created, call `hubspot-add-list` once with `name` set to `{list-name}`, `object-type` 0-1 and `processing-type` MANUAL, and use the returned `id`. Then call `hubspot-add-list-members` with `list-id` and `record-ids` set to the confirmed contact record-ids, comma-separated, in batches of at most 100. Call `hubspot-get-contact-list-membership` with `list-id` and confirm each contact is now a member. Report added, already present, failed and skipped.

**Rules & Guidelines:**

* `bigcommerce-get-subscriber` is on the bigcommerce server; `hubspot-get-contacts`, `hubspot-get-contact-subscriptions`, `hubspot-get-lists`, `hubspot-get-contact-list-membership`, `hubspot-add-list` and `hubspot-add-list-members` are on the hubspot server.
* The only write tools allowed are `hubspot-add-list`, at most once, and `hubspot-add-list-members`, once per batch, both 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. List membership is not consent: never subscribe or resubscribe anyone from this prompt.
* Never call `bigcommerce-subscriber-add`, `bigcommerce-subscriber-update`, `bigcommerce-subscriber-delete` or any other bigcommerce add, update or delete tool. BigCommerce is only read here.
* Do not create HubSpot contacts for subscribers that are not in HubSpot; report them instead.

**Validation:**

* If `{list-name}` is empty, ask for it and stop.
* If no subscriber matches a HubSpot contact, say so and stop without creating a list.
* If the user declines or does not answer, stop with nothing written.