See everything you owe in ServiceNow, ranked for today

**Objective:** Give `{user-name}` one prioritized view of everything waiting on them in ServiceNow.

**Step 1: Confirm the person**

Call `servicenow-get-user` with name `{user-name}`. If there are several matches, list them with email and department and stop. If the user is inactive, say so but continue.

**Step 2: Gather the work**

* `servicenow-get-incident` with assigned-to `{user-name}`, once each for states New, In Progress and On Hold.
* `servicenow-get-problem-task` with assigned-to `{user-name}`; keep tasks not in a closed state.
* `servicenow-get-change-task` with assigned-to `{user-name}`; keep tasks not in a closed state.
* `servicenow-get-knowledge-feedback-task` with assigned-to `{user-name}`; keep Open and Work in Progress.
* `servicenow-get-approval` with approver `{user-name}` and state Requested.
* `servicenow-get-problem` and `servicenow-get-change-request` with assigned-to `{user-name}`, open states only.

**Step 3: Add urgency**

For each incident call `servicenow-get-task-sla` with task set to its number and active true. For change tasks, note planned-start-date. For approvals, note due-date.

**Step 4: Report**

* "Do today": breached or at-risk SLAs, approvals due within 2 days, change tasks starting within 2 days, any priority 1 item.
* Then one short table per record type: number, short-description (or approval-for), state, priority, the relevant date.
* A closing count line: N incidents, N problem tasks, N change tasks, N feedback tasks, N approvals.

**Rules & Guidelines:**

* Read-only. Do not call `servicenow-update-incident`, `servicenow-update-approval`, `servicenow-update-change-task`, `servicenow-update-problem-task` or any other add- or update- tool.
* Omit empty sections instead of printing empty tables.

**Validation:**

* If nothing is open, say that `{user-name}` has no open work and stop.