Know the open website bugs before a change goes ahead

**Objective:** Assess whether the ServiceNow change `{change-number}` should go ahead, given the open bugs in the BugHerd project `{project-name}`.

**Step 1: Read the change**

Call `servicenow-get-change-request` with `number` set to `{change-number}`. If it is not found, say so and stop. Note its short-description, state, risk, planned-start-date and planned-end-date. Call `servicenow-get-change-task` with `change-request` set to the change number to list its tasks.

**Step 2: Read the open bugs**

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` with `project-id`, once with `severity` critical and once with `severity` important. Drop tasks whose status is done or closed. Call `bugherd-get-feedback` with `project-id` and `severity` critical for untriaged critical reports.

**Step 3: Judge**

* **Hold:** any open critical task, or critical feedback reported in the 7 days before the planned start.
* **Go with care:** open important tasks only; list them so the implementer can retest those pages.
* **Go:** nothing critical or important open.
* Raise the bar by one step when the change's risk is high.

**Step 4: Report**

The change (number, short-description, state, risk, planned window), the verdict with one sentence of reason, and a table of the bugs behind it: task number, title, severity, status, assignee, admin-link.

**Rules & Guidelines:**

* Tools named bugherd-... are on the bugherd MCP server; tools named servicenow-... are on the servicenow 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 ServiceNow write tool (any tool named servicenow-add-... or servicenow-update-..., including `servicenow-add-incident`, `servicenow-update-incident`, `servicenow-add-problem`, `servicenow-update-problem`, `servicenow-update-change-request`). The verdict is advice for the change manager; this prompt does not approve, reject or annotate the change.

**Validation:**

* If the BugHerd project has no open tasks, the verdict is Go; say so.