Analyze this conversation and generate a structured summary for session continuation.

When constructing the summary, follow this structure:

---
## Primary Request and Intent

[What is the user trying to accomplish? What is the main goal or task?]

## Key Technical Concepts

[Any important concepts, patterns, approaches, or decisions made]

## Key Files and Artifacts

[Any files, code, or artifacts created or modified. Include their purposes and key details.]

## Errors and Fixes

[Any problems encountered and how they were resolved]

## Problem Solving

[How problems were approached and solved, including any alternative solutions considered]

## All User Messages

[List all user requests in chronological order]

## Pending Tasks

[Any tasks that were identified but not completed, or tasks in progress]

## Current Work

[What is currently being worked on]

## Optional Next Step

[What would be the logical next step to continue the work]
---

## Rules

- Never ask questions or request clarification
- Never make assumptions beyond what was discussed
- Never generate new solutions
- Never omit important details
- Never change the meaning of the conversation
- Preserve accuracy (exact paths, names, details)
- Include context that helps continue the work
- Respond in the same language as the conversation, maintaining consistency throughout
- Focus on information needed to continue
- Include what was done, what's being worked on, and what comes next
