Work your Bloomerang task queue with donor context in hand

**Objective:** Produce the working queue of outstanding tasks due within the next `{days-ahead}` days (default 14), with enough donor context on each one to act without further lookups.

**Step 1: Pull the tasks**

Call `bloomerang-get-task` with `due-date.to` set to the end of the window and `status` set to the value that means not completed. Run it a second time with `due-date.to` set to today to catch anything already overdue.

If `{assigned-to}` was supplied, keep only tasks whose user-id matches it and say whose queue this is. Otherwise cover everyone and group by user-id.

**Step 2: Put names to the tasks**

For each distinct account-id on the tasks, call `bloomerang-get-constituent` filtered by id, and keep full name, type, status, primary email and primary phone.

**Step 3: Add the context that decides priority**

For each of those constituents:

* call `bloomerang-get-transaction` with their account-id over the last year, and keep total given and most recent gift date
* call `bloomerang-get-interaction` with their account-id and keep the most recent one, so nobody is contacted twice about the same thing

**Step 4: Report**

Two tables.

First, overdue: days overdue, due date, subject, channel, purpose, constituent name, giving in the last year, last interaction date, owner.

Second, due within the window: the same columns, ordered by due date.

Then three to five lines saying what to do first and why, weighing both how overdue a task is and what the constituent gives.

**Rules and Guidelines:**

* Read only. Do not call `bloomerang-update-task`, `bloomerang-add-task`, `bloomerang-add-interaction`, or any other tool whose name starts with bloomerang-add- or bloomerang-update-. Never mark a task complete from this prompt.
* A task with no account-id is a general task rather than a donor task. Keep it in the queue and leave the donor columns blank instead of guessing.
* Do not order purely by giving. An overdue task on a small donor still outranks a task due next week on a large one.

**Validation:**

* If the status filter returns tasks that are plainly finished, report the status values you saw and ask which one means open, rather than quietly filtering on the completed date instead.
* If the queue is empty, say so and report the next task due beyond the window.