Keep the HubSpot product library in step with 2Checkout

**Objective:** Make the HubSpot product library match up to `{max-records}` enabled 2Checkout products (default 25, optionally only names containing `{product-name}`), using each product's default price in currency `{currency}` (default USD). Nothing is written until the user confirms.

**Step 1: Read products from 2Checkout**

Call `2checkout-get-product` with `name.contains` set to `{product-name}` if given and `max-records` set to `{max-records}` (25 if empty). Keep `product-code`, `name`, `type` and `enabled`. Set aside products whose `enabled` is false and count them.

**Step 2: Find each product's default price in 2Checkout**

For each product, call `2checkout-get-pricingconfiguration` with `product-code` set to it and keep the configuration whose `default` is true. Then call `2checkout-get-pricingconfigurationprice` with `product-code` set to the product code, `pricing-configuration-code` set to that configuration's `code` and `currency` set to `{currency}` (USD if empty). Use the `amount` of the row with the lowest `minimum-quantity` and no `option-codes`. If no row qualifies, or several qualifying rows disagree on `amount`, mark the price as unknown and do not guess one.

**Step 3: Compare with the HubSpot product library**

The join is the 2Checkout `product-code` against the HubSpot `sku`. For each product, call `hubspot-get-products` with `sku` set to the `product-code`.

* No match: call `hubspot-get-products` with `name` set to the 2Checkout `name`. If that finds a product, list it as a possible match with a different SKU and leave it alone. Otherwise the product goes on the create list.
* One match: compare `name` and `unit-price`. If either differs, the product goes on the update list with the before and after values. If both match, it is in sync.
* More than one match: list the duplicates and leave them alone.

**Step 4: Confirm**

Show three tables: products to create (name, SKU, price), products to update (record-id, field, current value, new value) and products skipped (with the reason). Ask for an explicit yes and offer to exclude rows. Do not continue without a yes.

**Step 5: Write and verify**

For each confirmed new product, call `hubspot-add-product` once with `name`, `sku` set to the `product-code`, `price` set to the amount when it is known, and `description` set to "Synced from 2Checkout product <product-code>". For each confirmed change, call `hubspot-update-product` once with `id` set to the HubSpot `record-id` and only the fields that differ. Then call `hubspot-get-products` with `sku` set to each code and confirm the values. Report created, updated, failed and skipped rows.

**Rules & Guidelines:**

* Tools whose names start with 2checkout belong to the 2checkout server and tools whose names start with hubspot belong to the HubSpot server. Both servers must be connected.
* The only write tools allowed are `hubspot-add-product`, once per confirmed new product, and `hubspot-update-product`, once per confirmed change, 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.
* Never call `2checkout-product-add`, `2checkout-product-update`, `2checkout-product-enable`, `2checkout-product-disable`, `2checkout-pricingconfiguration-update`, `2checkout-pricingconfiguration-updateprices` or any other 2checkout tool that adds, updates, enables, disables or deletes. 2Checkout is only read here.
* Do not set `cost`, `product-type`, `billing-frequency` or `owner-id`: 2Checkout does not give a reliable value for them here.
* Never convert a price between currencies. A product with no price in `{currency}` is created without a price and flagged.

**Validation:**

* If `2checkout-get-product` returns nothing, say so and stop.
* If the user declines or does not answer, stop with nothing written.
* If a product does not show the new values on re-read, say so and do not retry blindly.