Make sure every outside BugHerd report hears back from support

**Objective:** For feedback left in the BugHerd project `{project-name}` in the last `{lookback-days}` days (default 7) by people outside the team, open Zendesk tickets so support can reply to them.

**Step 1: Read the feedback**

Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If several match, list their names and project-id values and ask which one; do not guess. Then call `bugherd-get-feedback` with `project-id` and `created.from` set to the start of the period. Call `bugherd-get-users` once: feedback whose requester-email belongs to a BugHerd user is from the team; leave it out. Leave out feedback with no requester-email.

**Step 2: Skip people already being handled**

For each remaining item, call `zendesk-get-ticket` with `requester-email` and `created.from` set to the feedback's created date. If an open ticket clearly covers the same thing, list it under "already in Zendesk".

**Step 3: Confirm, then write**

Show the tickets you will open (requester, subject, first line of the feedback) and wait for an explicit yes; accept removals. For each approved item:

1. Call `zendesk-add-ticket` once with `requester-email`, `subject` "Website feedback: " plus the first 60 characters of the description, `comment` set to the feedback text and the page, `type` question, and `priority` normal (high for critical severity).
2. Call `bugherd-add-comment` once with `project-id`, `task-id` and "Support is following up in Zendesk ticket <id returned by zendesk-add-ticket>."

**Step 4: Report**

Tickets opened (with ids), items already in Zendesk, and anything that failed.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named zendesk-... are on the zendesk MCP server. If either set of tools is missing, say which server is not connected and stop.
* The only write tools this prompt may call are `zendesk-add-ticket` and `bugherd-add-comment`, once per approved item.
* The ticket's first comment is visible to the requester: write it as a courteous acknowledgement followed by their feedback, not as internal notes.

**Validation:**

* If there is no outside feedback in the period, say so and stop.