Find public and idle BugHerd projects in one review

**Objective:** Audit BugHerd project visibility and activity, for projects owned by `{owner-name}` when given (all projects when empty), and recommend changes.

**Step 1: Read the projects**

Call `bugherd-get-projects` with `max-records` 500, and `owner-name` when given.

**Step 2: Check each active project**

* **Public:** a public project lets anyone with the link leave feedback. Flag every active project where public is true.
* **Possibly abandoned:** for each active project, call `bugherd-get-tasks` with `project-id`, `created.from` set to 90 days ago and `max-records` 1. No result means no new tasks in 90 days.
* Note projects where tasks-enabled is false.

**Step 3: Report**

Two tables: public projects (name, owner, development-url, created) and possibly abandoned projects (name, owner, created). Then recommendations: make private, deactivate, or leave as is, with one reason each.

**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. To make a project private afterwards, the user can ask for it and `bugherd-update-project` can be used then, in a separate request.
* Inactive projects are out of scope; count them in one line at the end.

**Validation:**

* If there are no projects, say so and stop.