Check Drip lifetime value against booked invoices

**Objective:** For Drip subscribers with a lifetime value of at least `{min-lifetime-value}` (default 1000), compare Drip's `lifetime-value` with the invoices Business Central posted to the same email, and flag differences above `{tolerance-percent}` percent (default 10). Use Business Central company `{bc-company}` if given.

**Step 1: Read Drip's high-value people**

Call `drip-get-subscriber` with `lifetime-value.min` set to `{min-lifetime-value}` (`max-records` 100). Keep `email`, `first-name`, `last-name`, `lifetime-value`.

**Step 2: Read Business Central for each**

Call `business-central-get-customer` with `email` set to the subscriber's email. If found, call `business-central-get-posted-sales-invoice` with `sell-to-customer-number` set to its `customer-number` and sum `total-amount-including-tax` across every invoice returned. If not found, record the subscriber as having no customer.

**Step 3: Compare**

Difference = Drip lifetime value minus Business Central invoiced. Percent = difference divided by the larger of the two. Flag any row above the tolerance.

**Step 4: Report**

A table of flagged rows sorted by absolute difference: email, name, customer number, Drip lifetime value, Business Central invoiced, difference, percent. Then counts: within tolerance, flagged, no customer in Business Central.

**Rules & Guidelines:**

* Tools whose names start with drip are on the drip server; tools whose names start with business-central are on the business-central server. Pass `{bc-company}` only to business-central tools.
* Drip lifetime value usually comes from the store feeding Drip and may include tax, refunds or other currencies. Note the currency of each Business Central invoice and do not convert between currencies; flag mixed currencies instead.
* This prompt is read-only. Do NOT call `drip-update-subscriber` or `business-central-update-customer`.

**Validation:**

* If no subscriber meets the threshold, say so and stop.
* If an invoice list hits the default record limit, raise `max-records` and read again before summing.
* Compare emails case-insensitively and ignoring surrounding spaces.