Decide if a GitHub milestone is ready to release

**Objective:** Decide whether GitHub milestone `{milestone-title}` is ready to release, using its open issues and the latest Ghost Inspector results for suites whose name contains `{suite-filter}` (all suites if blank).

**Step 1: Read the milestone (GitHub)**

Call `github-get-milestone` with `title` set to `{milestone-title}`. If it is not found, stop. Call `github-get-issue` with `milestone-title` set to `{milestone-title}` and `status` open to list what is left.

**Step 2: Read test health (Ghost Inspector)**

Call `ghost-inspector-get-suite`, with `name.contains` set to `{suite-filter}` if given. For each suite, call `ghost-inspector-get-suite-result` with `suite-id` and take the most recent result.

**Step 3: Cross-check**

Flag any open milestone issue whose title contains `[Ghost Inspector]` or names one of the suites, and say whether that suite is currently passing. An open test-failure issue on a suite that now passes is a close candidate, not a blocker.

**Step 4: Report**

* Milestone: title, due date, open and closed issue counts, url.
* Open issues: number, title, assignee, labels.
* Suites: name, latest result pass or fail, counts, time. Mark any suite whose latest result is older than the milestone's most recently closed issue as stale.
* Verdict: Ready, Ready with risks, or Not ready, and the two or three reasons that decide it.

**Rules & Guidelines:**

* `github-get-milestone` and `github-get-issue` are on the github server; the ghost-inspector tools are on the ghost-inspector server.
* This prompt is read-only. Do NOT call `github-update-milestone`, `github-update-issue`, `ghost-inspector-execute-suite` or `ghost-inspector-execute-test`.

**Validation:**

* If no suites match, report the milestone alone and say test health could not be assessed.
* If a suite has no results at all, count it as a risk, not a pass.