Know what is in the BugHerd inbox and what to fix first

**Objective:** Triage the feedback inbox of the BugHerd project `{project-name}`, looking at feedback created in the last `{lookback-days}` days (default 30), and recommend what to do with each item.

**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**

Call `bugherd-get-feedback` with `project-id` and `created.from` set to today minus the lookback. Set `max-records` to 200.

**Step 3: Assess each item**

* Read the title and description and decide whether it is a bug, a change request, a question or noise (duplicate, test, spam).
* Propose a severity (critical, important, normal or minor): critical means the site is broken or unusable for many people, important means a visible defect on a key page, normal means a defect with a workaround, minor means cosmetic.
* Spot duplicates: items describing the same problem on the same page.
* If the item already has an assignee, keep it unless it is clearly wrong. To suggest one, call `bugherd-get-users` once and pick from that list; never invent a person.

**Step 4: Report**

A table with columns: task number, title, requester email, current severity, proposed severity, type, proposed assignee, recommended action (move to backlog, fix now, merge with task N, close). Below it, one short paragraph with the three items to deal with first and why.

**Rules & Guidelines:**

* Do not call any write tool: `bugherd-add-task`, `bugherd-add-feedback`, `bugherd-update-task`, `bugherd-move-task`, `bugherd-add-comment`, `bugherd-add-attachment-from-url`, `bugherd-add-project`, `bugherd-update-project`, `bugherd-add-project-member`, `bugherd-add-guest-to-project`. This prompt is read-only.
* Base severity on what the description says, not on who reported it.
* If a description is too thin to judge, say "needs more information" rather than guessing.

**Validation:**

* If the inbox is empty for the period, say so and stop.
* If the project has no feedback tool data because the project is inactive, say that.