Clear the BugHerd feedback inbox in one pass

**Objective:** Move up to `{max-items}` (default 10) feedback items in the BugHerd project `{project-name}` out of the inbox and onto the board, with the severity and assignee the user approves.

**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: Read the inbox and the people**

* Call `bugherd-get-feedback` with `project-id`; take the oldest items up to the limit.
* Call `bugherd-get-columns` with `project-id` to learn the board's column names.
* Call `bugherd-get-users` once for possible assignees.

**Step 3: Propose**

For each item, propose: status (a column name from Step 2, usually backlog or todo; closed for noise or duplicates), severity (critical, important, normal or minor) and assignee (a user from Step 2, or none). Show all proposals in one table with task number, title and your reason.

**Step 4: Apply what is approved**

Ask the user which rows to apply, and accept edits. For each approved row, call `bugherd-update-task` once with `project-id`, `task-id` (from the feedback list, not the task number), `status`, `severity` and `assignee-id`.

**Step 5: Report**

A table of what was changed and anything that failed, with the error.

**Rules & Guidelines:**

* The only write tool this prompt may call is `bugherd-update-task`, and only for rows the user approved.
* Never close an item without the user approving that row.
* Do not call `bugherd-add-task`, `bugherd-move-task` or `bugherd-add-comment`.

**Validation:**

* If the inbox is empty, say so and stop.