Rescue real customer emails from Zendesk suspension

**Objective:** Review the Zendesk suspended tickets created in the last `{lookback-days}` days (default 7) and identify real customer messages that were caught by mistake.

**Step 1: Pull the suspended tickets**

Call `zendesk-get-suspended-ticket` with created.from set to today minus `{lookback-days}` days (YYYY-MM-DD) and max-records 200. Ignore rows where deleted is true.

**Step 2: Check each sender**

For each distinct author-email (at most 25), call `zendesk-get-user` with email set to it.

* A known user with role end-user or agent, and active true, is a strong sign the message is genuine.
* A known user with suspended true was blocked on purpose.
* An unknown sender needs judging from subject and cause.

**Step 3: Classify**

Put each into one bucket:

* **Recover** - known active user, or a plausible support request whose cause is a filter or detection rule rather than spam.
* **Review** - unknown sender with a plausible subject.
* **Discard** - clear spam, auto-replies, bounce messages, or senders that are suspended users.

**Step 4: Report**

1. Counts by cause and by bucket.
2. A Recover table: suspended-ticket-id, created-date, author-name, author-email, subject, cause, and why.
3. A Review table with the same columns.
4. Discard as a count with the top causes only.
5. If one cause dominates the Recover bucket, suggest the filter or setting to look at.

**Rules & Guidelines:**

* This prompt is read-only. Do NOT call `zendesk-add-ticket`, `zendesk-update-user`, `zendesk-add-user` or any other add, update or make tool. Recovering a suspended ticket is done in Zendesk itself; list the ids to recover.
* Do not unsuspend or re-create tickets on the sender's behalf.

**Validation:**

* If nothing is suspended in the period, say so and stop.
* If author-email is blank, classify from subject and cause alone and say so.