Know whether a release is healthy from errors and bug reports

**Objective:** Report the impact of release `{app-version}` (default the latest) of the Bugsnag project `{bugsnag-project}`, using Bugsnag errors and the bugs reported in the BugHerd project `{project-name}` since it shipped.

**Step 1: Find the release**

Call `bugsnag-get-release` with `project-name` set to `{bugsnag-project}`, plus `app-version` when given, else `max-records` 5 and take the newest. Note release-date, errors-introduced-count, errors-seen-count, unhandled-sessions-count and total-sessions-count. Find the release before it for comparison.

**Step 2: Bugsnag errors since the release**

Call `bugsnag-get-error` with `project-name` and `last-seen.from` set to the release-date. Keep errors whose first-seen-date is on or after the release-date: these are new.

**Step 3: BugHerd reports since the release**

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. Then call `bugherd-get-tasks` and `bugherd-get-feedback` with `project-id` and `created.from` set to the release-date.

**Step 4: Report**

1. **Release:** version, date, source-control-revision, stability (unhandled sessions as a share of total sessions) against the previous release.
2. **New errors:** error-class, message, users, events, error-url.
3. **Reported by people:** BugHerd tasks and feedback since the release, by severity, with page.
4. **Overlap:** new errors whose pages match BugHerd reports, matched by URL through `bugsnag-get-event` request-url. Match pages by URL: compare host and path, ignoring the scheme, a leading "www.", a trailing slash, the query string and the fragment.
5. **Verdict:** healthy, watch, or roll-back candidate, with one sentence why.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named bugsnag-... are on the bugsnag 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 Bugsnag write tool (`bugsnag-link-error-issue`, `bugsnag-create-error-issue`, `bugsnag-fix-error`, `bugsnag-open-error`, `bugsnag-ignore-error`, `bugsnag-discard-error`, `bugsnag-assign-error`, `bugsnag-update-error-severity`, `bugsnag-update-project`, `bugsnag-add-project`, `bugsnag-add-project-collaborator`).

**Validation:**

* If the release is not found, list the five newest releases and stop.