See which GitHub milestones are at risk, and why

**Objective:** Report the progress of the open milestones in `{repository}`, or only the milestone titled `{milestone-title}` when it is given, and call out the ones at risk of missing their due date.

**Step 1: Load the milestones**

Call `github-get-milestone` with company `{repository}`, state `open`, and title set to `{milestone-title}` when it is given. Record open-issues, closed-issues, due-date and milestone-number for each.

**Step 2: Load the open work for each milestone**

For each milestone call `github-get-issue` with company `{repository}`, milestone-title set to the milestone's title, and status `open`. For each open issue note its assignee, labels and updated-date.

**Step 3: Assess risk**

* Percent complete is closed-issues divided by open-issues plus closed-issues.
* Overdue: due-date is in the past and open-issues is above zero.
* At risk: due in the next 14 days with more than a quarter of issues still open.
* Flag open issues with no assignee, and open issues not updated in the last 14 days.
* A milestone with no due-date cannot be at risk; list it as unscheduled.

**Step 4: Report**

* A table: milestone title, due-date, percent complete, open, closed, and status (on track, at risk, overdue, unscheduled).
* For each at-risk or overdue milestone, the open issues holding it up: issue-number, title, assignee, days since last update.
* A one-paragraph summary of what needs a decision (cut scope, move the date, or add an owner).

**Rules & Guidelines:**

* This prompt is read-only. Do NOT call `github-update-milestone`, `github-add-milestone`, `github-update-issue`, `github-add-issue-assignee` or `github-add-issue-comment`.
* Use today's date to judge overdue and at risk, and state the date you used.

**Validation:**

* If no open milestones are returned, say so and stop.
* If `{milestone-title}` matches more than one milestone, list them and ask which one to report on.