See which test failures are new since the release

**Objective:** Find out whether the deployment of release `{release-name}` in Azure DevOps was followed by Ghost Inspector test failures within `{window-hours}` hours (default 24).

**Step 1: Establish the deployment (azure-devops)**

Call `azure-devops-get-deployment` with `release-name` set to `{release-name}`. Note each deployment's `environment-name`, `deployment-status`, `queued-on` and `completed-on`. If no deployment matches, stop and say so. If the release has several environments, list them and use the earliest completed deployment per environment.

**Step 2: Look at tests after the deployment (ghost-inspector)**

For each deployment with a `completed-on` value, call `ghost-inspector-get-suite-result` with `date-created.from` set to `completed-on`, `date-created.to` set to `completed-on` plus `{window-hours}` hours, and `passing` set to false. Then call `ghost-inspector-get-test-result` with the same window and `passing` false.

**Step 3: Compare with the period before**

Call `ghost-inspector-get-suite-result` for the same length of time ending at `completed-on` so you can tell new failures from long-standing ones. A test is a new failure only if it failed after the deployment and did not fail before.

**Step 4: Report**

A table per environment: deployment status, completed time, number of failing suite runs and test runs after, number before, and the names of new failures. End with one line: no signal, or likely regression.

**Rules & Guidelines:**

* Azure DevOps tools (prefix azure-devops-) come from the azure-devops server; Ghost Inspector tools (prefix ghost-inspector-) come from the ghost-inspector server. Both servers must be connected.
* The two systems share no key. The link is time: match on the deployment's `completed-on` against the test run's `date-created`. Ghost Inspector tests are not tied to a release, so say this is correlation, not proof.
* Compare times in UTC.
* Do not call any write tool: `ghost-inspector-execute-test`, `ghost-inspector-execute-suite`, `ghost-inspector-execute-on-demand-test`, `ghost-inspector-update-test`, `ghost-inspector-update-suite`, `ghost-inspector-add-test-result-comment`, `ghost-inspector-add-suite-result-comment`, `ghost-inspector-accept-screenshot`, or any create, duplicate, cancel or update tool. This prompt only reads.

**Validation:**

* If `deployment-status` is not a success, say so and still report, but flag that nothing may have been deployed.
* If Ghost Inspector returns no runs in the window, report "no test runs in the window" rather than "no failures".