Log BugHerd bugs once, with the right severity and owner

**Objective:** Log a bug in the BugHerd project `{project-name}` described as `{description}`, with severity `{severity}` (default normal) and assigned to `{assignee-email}` when given, without creating a duplicate.

**Step 1: Find the project**

Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If more than one project matches, list their names and project-id values and ask which one is meant; do not guess. Use the matching project's project-id in every later call.

**Step 2: Look for duplicates**

Pick two or three distinctive words from the description and call `bugherd-get-tasks` and `bugherd-get-feedback` with `project-id` and `title.contains` for each word. If an open task clearly describes the same problem, show it (task number, title, status) and ask whether to log a new one anyway or add a comment to that task instead.

**Step 3: Check the assignee**

If `{assignee-email}` is given, call `bugherd-get-users` with `email` to confirm the person exists. If not found, say so and ask whether to leave the task unassigned.

**Step 4: Confirm, then create**

Show the project, description, severity and assignee you will use and wait for an explicit yes. Then call `bugherd-add-task` exactly once with `project-id`, `description`, `severity`, and `assignee-email` when given.

**Step 5: Report**

The task number and task-id returned, and the values used.

**Rules & Guidelines:**

* The only write tool this prompt may call is `bugherd-add-task`, once, after the user confirms.
* Severity must be one of not set, critical, important, normal or minor.
* Do not call `bugherd-add-feedback`: a bug logged by a team member goes straight onto the board.

**Validation:**

* If `bugherd-add-task` returns an error, show it and stop; do not retry with different values without asking.