Walk into your next account meeting knowing the whole history

**Objective:** Produce a briefing on the account `{account-name}` from the conversations and emails Chorus has captured in the last `{lookback-days}` days (default 90), so the reader can walk into the next meeting knowing where things stand.

**Step 1: Establish the account**

Call `chorus-get-engagements` with `account-name.contains` set to `{account-name}` and `date.from` set to the start of the lookback window. Read the `account-name` values that come back. If they resolve to more than one distinct account, list the distinct names and stop, asking which one is meant. If nothing comes back, widen to the full history by omitting `date.from` once, and if that is still empty say so and stop.

**Step 2: Read the conversations**

From the engagements, note for each one the `date`, `conversation-type`, `subject`, `duration`, `user-name` (who from our side ran it), `number-of-participants` and `meeting-summary`. Order them oldest to newest so the story reads forward.

**Step 3: Establish who is involved**

For the three most recent conversations, call `chorus-get-conversation-participants` with `conversation-id` set to that conversation's `conversation-id`. Build a single list of the people on the customer side: name, title and company. Mark anyone who appears in only the earliest or only the latest conversations, since a changed cast is a signal in itself.

**Step 4: Read the email traffic**

Call `chorus-get-emails` with `account-name.contains` set to `{account-name}` and `sent-time.from` set to the start of the window. Use the `subject`, `initiator-name` and `sent-time` to see what has happened between meetings, and read the `body` only of the most recent three.

**Step 5: Report**

Produce:

* **Where things stand** - three to five sentences of plain narrative.
* **Timeline** - a table of date, type, subject, our owner, duration.
* **Who is in the room** - a table of name, title, company, and whether they are new.
* **Open threads** - what was raised and has not visibly been answered, each with the conversation or email it came from.
* **Questions to ask next** - three concrete ones, each tied to something above.

**Rules & Guidelines:**

* This is read only. Do not call `chorus-add-moment`, `chorus-add-playlist-moment`, `chorus-create-playlist`, `chorus-update-playlist`, `chorus-update-playlist-moment`, `chorus-update-moment`, `chorus-export-recordings` or `chorus-export-scorecards`.
* Quote `meeting-summary` and email text as evidence rather than paraphrasing a commitment into existence.
* Say when something is absent. A gap of six weeks with no contact belongs in the briefing.

**Validation:**

* If `{account-name}` matches nothing, report that and suggest checking the spelling against Chorus.
* If conversations exist but all have an empty `meeting-summary`, say the recordings were not summarised and base the briefing on subjects, participants and emails only.