Check Dynamics GP items against AvaTax tax codes

**Objective:** Check the Dynamics GP items in item class `{item-class-code}` against the Avalara AvaTax item catalog and report items missing from AvaTax or lacking a tax code. If `{max-items}` is empty, check up to 50 items.

**Step 1: List the GP items**

Call `dynamics-gp-get-iv-item` with `item-class-code` set to `{item-class-code}` and `max-records` set to `{max-items}` (50 if empty). If nothing comes back, say so and stop. Keep `item-number`, `item-description` and `item-type`.

**Step 2: Look each item up in Avalara AvaTax**

For each GP item call `avalara-avatax-get-item` with `item-code` set to its `item-number`. Keep `tax-code`, `item-group`, `category` and `modified-date`. If a tax code is present, call `avalara-avatax-get-tax-code` with `tax-code` set to it once per distinct code, and keep `description` and `active`.

**Step 3: Report**

Give counts of items matched, missing from AvaTax, present without a `tax-code`, and mapped to an inactive tax code. List each problem item with its `item-number` and description. Group items sharing the same tax code at the end.
**Rules & Guidelines:**

* Tools whose names start with avalara-avatax- are on the avalara-avatax MCP server; tools whose names start with dynamics-gp- are on the dynamics-gp MCP server. Both servers must be connected.
* This prompt is read-only. Never call any create, update, delete, add, void, commit, adjust, post or other action tool on either server.
* Report what the two systems show. Do not present results as tax advice or as a filed return.

**Validation:**

* If AvaTax returns nothing for every item, say the item codes may use a different scheme than the GP item numbers and show two examples side by side; do not conclude all items are missing.
* Where a GP item description and the AvaTax item description differ, show both and do not choose.