Update WooCommerce prices from Dynamics GP list prices

**Objective:** Set the WooCommerce regular price for SKUs {skus} to the Dynamics GP list price in currency {currency-id} (default: the only currency GP returns) for unit of measure {unit-of-measure} (default: the item's selling unit of measure), after the user confirms the changes.

**Step 1: Find each SKU in the store (woocommerce)**

Split {skus} on commas. For each SKU call `woocommerce-get-product` with sku set to it. If nothing comes back, call `woocommerce-get-product-variation` with sku set to it. If neither returns anything, record the SKU as not in the store. Keep the product-id, the product-variation-id for a variation, the name, regular-price and sale-price.

**Step 2: Read the GP list price (dynamics-gp)**

For each SKU call `dynamics-gp-get-iv-item` with item-number set to it to get its selling-u-of-m. Then call `dynamics-gp-get-iv-item-price` with item-number, unit-of-measure set to {unit-of-measure} or the selling-u-of-m, and currency-id set to {currency-id} when it is given. Use list-price only when exactly one row comes back.

**Step 3: Preview and confirm**

Show a table: SKU, name, current regular price, GP list price, change. Leave out SKUs whose price already matches to within 0.01. Flag any SKU where the new regular price would be at or below its current sale-price. List SKUs missing from either system, or with several or no GP price rows, separately. Ask the user to confirm before writing anything.

**Step 4: Write (woocommerce)**

Only after the user confirms, set regular-price, rounded to 2 decimals: for a product call `woocommerce-update-product` with product-id and regular-price; for a variation call `woocommerce-update-product-variation` with variation-id, product-id and regular-price.

**Step 5: Report**

Each SKU with its old and new regular price and whether the write succeeded.

**Rules & Guidelines:**

* Tools whose names start with woocommerce- are on the woocommerce MCP server; tools whose names start with dynamics-gp- are on the dynamics-gp MCP server. If a tool from either server is not available, stop and say which server is not connected.
* If the user names a Dynamics GP company, pass it as company on every dynamics-gp call.
* Match a store SKU to a GP item number exactly, after trimming spaces. If that fails, try the SKU in upper case once. Never match on descriptions or partial codes.
* The only tools that may write are `woocommerce-update-product` and `woocommerce-update-product-variation`, only after the confirmation in step 3, and only to set regular-price.
* Never change sale-price, stock or status in the store.
* Never write to GP. Do not call `dynamics-gp-iv-item-price-update`, `dynamics-gp-iv-item-price-add` or `dynamics-gp-iv-item-update`.

**Validation:**

* If {skus} lists more than 50 SKUs, ask the user to narrow it.
* If GP returns several price rows, show them and skip the SKU unless the user picks one.
* If the GP list price is 0 or empty, skip the SKU. Never set a store price to 0.
* If a write fails, report the error and carry on with the next SKU.