Write Asana status updates that match the real work

**Objective:** Draft a status update for the Asana project `{project-name}` covering the last `{lookback-days}` days (default 7), show it to the user, and post it only after they approve.

**Step 1: Identify the project**

Call `asana-get-project` with `name` set to `{project-name}`. If none or more than one project matches, list what you found and stop. Record the `project-id` and due date.

**Step 2: Gather the evidence**

* Call `asana-get-status-updates` with `parent-id` set to the project id and read the most recent update, so the new one follows on from it.
* Call `asana-get-tasks` with `projects` set to the exact project name, `completed` set to true and `completed-at.from` set to `{lookback-days}` days ago: this is what got done.
* Call `asana-get-tasks` with `projects` set to the project name and `completed` set to false: from this take what is overdue and what is due in the next 14 days.

**Step 3: Draft**

Choose a status of on_track, at_risk or off_track (on_hold only if the user says the project is paused). Use off_track when the project due date has passed or several key tasks are badly overdue, at_risk when anything is overdue. Write:

* **Title:** a short headline for the period
* **Text** in plain text with three short sections: Done (the completed tasks that matter, not every one), Next (what is due in the next two weeks), Risks and blockers (overdue tasks with owner and days late)

Show the user the status, title and text, and the evidence counts behind the status choice. Then ask: post this as it stands, edit it, or cancel.

**Step 4: Post, only on approval**

When, and only when, the user explicitly approves, call `asana-create-status-for-project` once with `project-id`, `status`, `title` and `text`. Report the returned id and status. If the user edits the draft, show the revised draft and ask again.

**Rules & Guidelines:**

* `asana-create-status-for-project` is the only write tool this prompt may call, and only once, after explicit approval. Do not call `asana-create-status-update`, `asana-create-status-for-portfolio`, `asana-update-project`, `asana-update-task` or any other write tool.
* Never post a draft the user has not seen. Silence or an ambiguous reply is not approval.
* Do not invent progress: every item under Done must be a task returned in Step 2.

**Validation:**

* If nothing was completed in the period, say so in the draft rather than padding it.
* If the post fails, show the error and the draft so the user can post it by hand.