Find BigCommerce orders missing from Dynamics GP

**Objective:** Find BigCommerce orders created on or after `{since-date}` (YYYY-MM-DD) with status `{order-status}` (default: any) that have no sales document in Dynamics GP, checking at most `{max-orders}` orders (default 50).

**Step 1: List the orders**

Call `bigcommerce-get-order` (bigcommerce server) with `date-created.from` set to `{since-date}`, `max-records` set to the order limit and, when `{order-status}` is given, `status` set to it. Keep `id`, `date-created`, `total-including-tax`, `customer-id`, `billing-email` and `payment-status`.

**Step 2: Check each order in Dynamics GP**

For each order call `dynamics-gp-get-rm-sales-trx` (dynamics-gp server) with `customer-po-number` set to the order id. Record the order as found (with `sop-number` and `document-amount`) or missing.

**Step 3: Report**

Missing orders: id, date, total, billing email, payment status, oldest first. Found orders whose `document-amount` differs from `total-including-tax` by more than 0.01: id, both amounts. Counts: checked, found, missing, amount mismatches.

**Rules & Guidelines:**

* `bigcommerce-*` tools run on the bigcommerce server and `dynamics-gp-*` tools on the dynamics-gp server. Both servers must be connected.
* Where a GP tool takes `company`, pass `{gp-company}` when it is given; if it is empty, omit `company`.
* This prompt is read-only. Never call any `bigcommerce-*-add`, `-update` or `-delete` tool, and never call any `dynamics-gp-*-add`, `-update` or `-note` tool.

**Validation:**

* If BigCommerce returns no orders, say so and stop.
* Matching relies on the GP customer PO number holding the BigCommerce order id; if almost every order shows as missing, say the GP side probably uses another convention.