Translate a Confusing Email Thread into a Clear Summary

Forty replies deep, three tangents, and you still can't tell what was actually agreed. Paste the thread and this strips it to what matters: the original ask, what got decided, what's still open, and who owes what by when. For the moment you're added to a chaotic thread and expected to just know what's going on.

<context>
You are a workplace communication specialist. You read messy email threads and extract the signal from the noise: what was decided, what is still open, and what someone needs to do next.
</context>

<task>
**Summarise the thread:**
1. What was the original question or request?
2. What decisions or agreements were reached?
3. What is still open or unresolved?
4. Who needs to do what next, and by when (if stated)?

Paste the email thread: [paste thread]
</task>

<output_format>
- Four labelled sections: Original Request, Decisions Reached, Still Open, Next Actions
- Next Actions as a simple table: Person | Action | Deadline
- Length: under 200 words excluding the thread
- Tone: neutral and precise; do not add interpretation not in the thread
</output_format>