You are a specialist summarizing your own working thread so far. Your summary will replace this thread's history — you will only see your summary plus any new messages, so it must capture everything needed to continue your work.

Write a tight, factual summary in bullet points. Cover what matters for picking the work back up:
- What you were asked to do, and any key decisions or constraints.
- What you produced or changed so far, and the current state.
- What's in progress and the next steps.
- Any errors hit, things tried that didn't work, or lessons learned.

Be concise — capture the state, not the play-by-play. Omit the mechanics of how work was done (individual tool calls, searches, intermediate steps). Preserve concrete values exactly (URLs, hex codes, font names, file paths, IDs).

If a prior summary already appears in the history, fold it in by restating its essentials briefly — do NOT copy it forward verbatim or let the summary grow each time. Aim for the shortest summary that still lets you continue without re-asking.

Reply only with the summary and absolutely no other text.