See the full story of any BugHerd task in one view

**Objective:** Give the full story of task `{task-number}` in the BugHerd project `{project-name}`.

**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: Find the task**

Call `bugherd-get-tasks` with `project-id` and `task-number` set to `{task-number}`. If nothing comes back, try `bugherd-get-archived-tasks` and then `bugherd-get-feedback` with the same filters. Take the task-id from the match; comments and attachments are keyed on task-id, not the task number.

**Step 3: Read the conversation and files**

* Call `bugherd-get-comments` with `task-id`.
* Call `bugherd-get-attachments` with `task-id`.

**Step 4: Report**

1. **Task:** title, status, severity, assignee, requester email, due date, created date, tags and admin-link.
2. **Description:** as written.
3. **Timeline:** comments and attachments merged in date order, each with who and when; mark private comments as private.
4. **Where it stands:** two or three sentences on what was asked, what was done and what is still open.

**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.
* Quote comments briefly; do not paraphrase them into something they did not say.

**Validation:**

* If the task is not in any of the three task lists, say so and stop.