Review Stripe disputes with 2Checkout subscription context

**Objective:** For the customer with email `{email}`, list their Stripe disputes and the charges behind them, and add their 2Checkout customer and subscription context so a reviewer can see the whole relationship.

**Step 1: Stripe customer and disputes**

Call `stripe-get-customer` (stripe server) with `email` set to `{email}`; take customer-id. If there is no match or more than one, report that and stop. Then call `stripe-get-dispute` (stripe server) with `customer-id`. Keep dispute-id, charge-id, amount, reason, status, details-due-by.

**Step 2: Charges**

For each dispute call `stripe-get-charge` (stripe server) with `charge-id`. Keep amount, created, description, refunded, amount-refunded.

**Step 3: 2Checkout context**

Call `2checkout-get-customer` (2checkout server) with `email` set to `{email}`, then `2checkout-get-subscription` (2checkout server) with `end-user-email` set to `{email}`. Keep customer-reference, subscription-reference, product-name, status, expiration-date.

**Step 4: Report**

Per dispute: dispute-id, reason, amount, status, due date, the charge it concerns, then below it the 2Checkout subscriptions. Highlight disputes due within 7 days.

**Rules & Guidelines:**

* `2checkout-*` tools are on the 2checkout server; `stripe-*` tools are on the stripe server. Both servers must be connected.
* This prompt is read-only. Never call any 2checkout write tool (any `2checkout-*` tool that adds, updates, cancels, refunds, disables, extends or deletes, such as `2checkout-order-refund`, `2checkout-subscription-disable`, `2checkout-customer-update`).
* Stripe tools here are reads only. Do not guess values; report only what the tools return.

**Validation:**

* If the customer has no disputes, say so and stop after Step 1.
* If 2Checkout has no matching customer, report the Stripe findings and note the absence.