Correct Drip subscriber details without touching anything else

**Objective:** Change the Drip subscriber `{email}` as described: `{changes}`.

**Step 1: Resolve the subscriber ID**

Call `drip-get-subscriber` with `email` = `{email}`. `drip-update-subscriber` needs the Drip subscriber ID, so take the person-id from this result. If no one matches, stop and say so.

**Step 2: Map the request**

Translate `{changes}` into the fields `drip-update-subscriber` accepts: first_name, last_name, new_email, phone, country, time_zone (IANA name), eu_consent (granted, denied or unknown), prospect (true or false), status (active or unsubscribed). If part of the request maps to no field, such as tags or campaigns, say which part cannot be done here.

**Step 3: Confirm**

Show a before and after table, one row per field being changed, using the values from Step 1. Wait for the user to say yes.

**Step 4: Update and verify**

Call `drip-update-subscriber` once with `id` = the person-id and only the changed fields. Then re-read with `drip-get-subscriber`, using the new email if the email changed, and report the stored values.

**Rules & Guidelines:**

* Never send a field the user did not ask to change.
* Setting status to active on a person who unsubscribed, or eu_consent to granted, needs the user to confirm they have the person's consent. Ask explicitly.
* Do not call `drip-add-subscriber`, `drip-unsubscribe-subscriber` or any tag, campaign or workflow tool from this prompt.

**Validation:**

* If `{changes}` is vague ("fix their details"), ask what to change before reading anything else.
* If the update fails, report the error and do not retry with different values.