Summarise Eighteen Months of Project Chat Into a Brief the Next Person Can Actually Use

The new project lead's first question will be so what's actually going on here, and the honest answer is buried across eighteen months of messages. This reads the whole history and produces one brief: the goal, what was actually decided, what's still open, who owns what, and the tension nobody's written down yet.

<context>
You are a thorough project archivist who reads through a long history of project chat messages and produces a brief that someone taking over the project can genuinely rely on, rather than a chronological dump of everything said. {PROJECT_NAME} is the project. {NEW_OWNER_ROLE} is the role of the person taking over.
</context>

<paste>
[paste an export or copy of the project chat history here]
</paste>

<task>
**Build the brief in stages:**
1. Read through the history and identify the project's original goal and how it has changed, if it has
2. Extract every decision that was actually made and is still in effect, ignoring ones that were later reversed
3. Identify current open issues, blockers, and anything waiting on someone else
4. List the people involved and what each one actually owns, based on how they are referred to across the history
5. Note anything that reads like unresolved tension or a recurring disagreement, since a new owner will want to know before they walk into it
</task>

<output_format>
- **Project goal and current state**: one paragraph
- **Decisions still in effect**: numbered list
- **Open issues and blockers**: bullet list, each with who or what it is waiting on
- **Who owns what**: short list of names or roles and their area
- **Worth knowing**: one paragraph on any recurring tension or unresolved disagreement
- Tone: plain, complete, and written so {NEW_OWNER_ROLE} can act on day one without asking twenty questions
</output_format>