story-kit: start 168_bug_agent_message_queue_limited_to_one_line

.story_kit/work/2_current/167_bug_thinking_trace_height_constraint_not_working_in_web_ui.md

@@ -0,0 +1,35 @@
+---
+type: bug
+title: Thinking trace height constraint not working in web UI
+---
+
+# Bug 167: Thinking trace height constraint not working in web UI
+
+## Description
+
+Story 160 added a `ThinkingBlock` component with a 96px max-height to constrain thinking traces in the agent stream UI. However, thinking traces still flood the UI with no visible height constraint. The thinking text appears to render without the max-height container, or the component is not being used in the right place.
+
+## How to Reproduce
+
+1. Open the web UI and watch an agent stream
+2. Observe thinking traces — they expand unbounded, flooding the view
+
+## Actual Result
+
+Thinking traces take up the full height of the output, pushing real content out of view.
+
+## Expected Result
+
+Thinking traces should be constrained to a fixed height (96px) with overflow scrolling, as implemented in the `ThinkingBlock` component from story 160.
+
+## Key files
+
+- `frontend/src/components/AgentPanel.tsx` — `ThinkingBlock` component and where thinking state is rendered
+- Check whether `ThinkingBlock` is actually rendered in the agent output stream, or if thinking text is still going through the regular log output path
+
+## Acceptance Criteria
+
+- [ ] Thinking traces are visually constrained to a max height in the agent stream UI
+- [ ] Overflow scrolls within the constrained block
+- [ ] Regular output is not affected
+- [ ] All tests pass

.story_kit/work/2_current/168_bug_agent_message_queue_limited_to_one_line.md

@@ -0,0 +1,33 @@
+---
+type: bug
+title: Agent message queue limited to one line
+---
+
+# Bug 168: Agent message queue limited to one line
+
+## Description
+
+Story 155 added the ability to queue messages while an agent is busy. However, the queue appears to be limited to a single line — if you type multiple messages while the agent is working, only the last one is retained. Users need to be able to queue multiple messages.
+
+## How to Reproduce
+
+1. Open the web UI and start a conversation with a busy agent
+2. Type and send a message while the agent is processing
+3. Type and send a second message
+4. Observe that only the most recent queued message is shown/retained
+
+## Expected Result
+
+Multiple queued messages should be retained and delivered to the agent in order when it becomes available.
+
+## Key files
+
+- `frontend/src/components/` — chat/agent interaction components where message queuing is implemented
+- `server/src/` — if server-side queuing is involved
+
+## Acceptance Criteria
+
+- [ ] Users can queue multiple messages while an agent is busy
+- [ ] Queued messages are delivered in order
+- [ ] UI shows all queued messages, not just the latest
+- [ ] All tests pass