Currently the sessions on the left menu only shows 1 PR and it's merge state.

Currently the sessions on the left menu only shows 1 PR and it's merge state. However, I think there are a lot of scenarios in which one session could merge multiple PRs

1. a coordinator can continually merge documentation updates as it's children work on parts of a features

2. there is memory pressure on my computer so I prefer to spawn fewer sessions and have them work on tasks serially

3. there is a small follow-up or new decision, where it could be convenient to have the same session make the change ex. "session has merged PR but there is a yes/no awaiting you or would you like to take on task X"

---
| Field | Value |
| --- | --- |
| App version | 1.1.0 |
| OS | macOS 26.5.2 |
| Theme | Notionish |
| Path | /chat |
| Tenure | Week 4 |

Start at the /chat path and inspect how the left-menu session entry represents pull requests and merge state. Trace the session data used by that entry, then define the UI behavior for sessions that merge multiple PRs; done means all relevant PRs and their states are represented rather than only one.

Written by the indexing model from the issue text.