See your site's health from tests and bug reports together

**Objective:** Report the health of the website tracked by the BugHerd project `{project-name}` over the last `{lookback-days}` days (default 14), using Ghost Inspector results and BugHerd bugs together.

**Step 1: Match the project to its suites**

Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If several match, list their names and project-id values and ask which one; do not guess. Note its development-url and sites. Call `ghost-inspector-get-suite` with `max-records` 500 and keep suites whose start-url matches. Match pages by URL: compare host and path, ignoring the scheme, a leading "www.", a trailing slash, the query string and the fragment. A BugHerd project matches a Ghost Inspector suite when the suite start-url is on the project development-url host or one of its sites. If none match, say the site has no automated tests and report BugHerd alone.

**Step 2: Test results**

For each matched suite, call `ghost-inspector-get-suite-result` with `suite-id` and `date-created.from` set to the start of the period. Work out the pass rate, the latest result and the tests that failed most often (`ghost-inspector-get-test-result` with `suite-id`, `passing` false and the same date).

**Step 3: Bugs**

Call `bugherd-get-tasks` with `project-id` (open tasks) and `bugherd-get-feedback` with `project-id` and `created.from` set to the start of the period.

**Step 4: Report**

1. **Headline:** healthy, at risk or unhealthy, with one sentence why.
2. **Automated tests:** per suite, runs, pass rate and latest result.
3. **Open bugs:** counts by severity, and the oldest critical or important ones.
4. **Hot pages:** pages that have both failing tests and open bugs (match by URL); these come first.
5. **Gaps:** pages with open bugs but no test, and failing tests with no bug logged.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named ghost-inspector-... are on the ghost-inspector MCP server. If either set of tools is missing, say which server is not connected and stop.
* This prompt is read-only. Do not call any BugHerd 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`) or any Ghost Inspector tool that runs, changes or comments (`ghost-inspector-execute-test`, `ghost-inspector-execute-suite`, `ghost-inspector-execute-on-demand-test`, `ghost-inspector-add-test-result-comment`, `ghost-inspector-add-suite-result-comment`, `ghost-inspector-update-test`, `ghost-inspector-update-suite`, `ghost-inspector-duplicate-test`, `ghost-inspector-duplicate-suite`, `ghost-inspector-accept-screenshot`, `ghost-inspector-cancel-test-run`, `ghost-inspector-cancel-suite-run`, `ghost-inspector-create-suite`, `ghost-inspector-create-folder`, `ghost-inspector-update-folder`, `ghost-inspector-create-data-source`, `ghost-inspector-update-data-source`).

**Validation:**

* If there are no results and no bugs, say so and stop.