Catch days when CI and browser tests disagree

**Objective:** For the last `{lookback-days}` days (default 14), compare pipeline `{pipeline-name}` in Azure DevOps with suite `{suite-name}` in Ghost Inspector and report where one is green and the other is red.

**Step 1: Read the pipeline runs (azure-devops)**

Call `azure-devops-get-pipeline-run` with `name.contains` set to `{pipeline-name}`. If it matches more than one pipeline, list them and stop. Keep runs whose `created-date` is inside the window. Record `created-date`, `finished-date`, `result` and `state`.

**Step 2: Read the suite results (ghost-inspector)**

Call `ghost-inspector-get-suite` with `name.contains` set to `{suite-name}`. If more than one matches, list them and stop. Call `ghost-inspector-get-suite-result` with that `suite-id` and `date-created.from` set to the start of the window. Record `date-created`, `passing`, `count-failing` and `count-passing`.

**Step 3: Pair and compare**

Pair each pipeline run with the first suite result created after its `finished-date`, and before the next pipeline run finishes. Classify each pair: both green, both red, pipeline green with suite red, or pipeline red with suite green. Unpaired items go in their own list.

**Step 4: Report**

Counts per class, then the disagreement rows with both times and the failing count. Finish with one line on which direction the disagreements run, which says whether the pipeline gate is too loose or the suite is flaky.

**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.
* Pairing is by time only; state that assumption.
* 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 either side has no rows in the window, report that and stop.
* A pipeline run with `state` not completed is still running; leave it out and say so.