specs/002-fix-analysis-chat-ui/quickstart.md

# Quickstart: Verifying Analysis Chat UI Fixes

Run the dev server:

```bash
npm run dev
```

Open the app, log in, and navigate to an existing analysis (or create one) to reach the Analysis Agent view.

## US1 — Report sidebar resize / fullscreen

1. Open an analysis with a generated report.
2. Drag the vertical handle between the chat and report panes — width should move smoothly, clamped roughly between 25% and 75% of the viewport.
3. Click the fullscreen toggle in the report panel — it should expand to fill the available area; toggle again to return to the previous split width.
4. Reload the page — width/fullscreen should reset to default (session-only persistence, confirmed by clarification).

## US2 — Stable chat input / footer

1. Create or view an account with 10+ analyses in the left nav list.
2. Send enough chat messages in the active analysis to exceed one viewport height.
3. Confirm the chat input bar and its footer stay pinned at the bottom of the conversation pane; only the message history scrolls. Resize the browser window and repeat.

## US3 — Business questions as starter buttons

1. Create a new analysis with 2–5 business questions.
2. On landing in its empty conversation, confirm guidance text plus one button per question appear (no "No messages yet" notice).
3. Click a question button — it should be sent as the first chat message and the conversation should proceed normally.
4. Send a message manually instead — reload the analysis and confirm the guidance/buttons no longer show once a message exists.

## US4 — Business question limits at creation

1. Open "New Analysis".
2. Add questions up to 5 — the "Add" control should disable/hide at 5.
3. Remove down to 2 — the "Remove" control should disable/hide at 2.
4. Attempt to submit with fewer than 2 non-empty questions — submission should be blocked with a validation message.

## US5 — Simplified conversation header

1. Open any analysis conversation.
2. Confirm the header is a compact single row showing title, source-count/status pill, and "Edit sources" action — no persistent objective paragraph or question-chip row.
3. Confirm "Edit sources" and the stale-sources banner (if applicable) still function as before.