Read the relevant conversation outputs and produced artifacts before drafting.
Build the recap around a clear narrative:
- starting request
- key turns and decisions
- evidence gathered
- final outputs and why they matter
Keep the output offline-first:
- one HTML file
- no CDN
- no remote fonts
- no runtime fetches
Prefer a presentation page, not a raw transcript dump.
Use the bundled references and template:
- Read references/workflow.md for the required structure and content rules.
- Reuse assets/offline_recap_template.html as the starting shape when it fits.

Required Output Rules

Default output path: place the recap near the produced artifacts unless the user specifies another location.
Include a top summary, a conversation/process timeline, key insights, and final artifact cards.
When documents or reports were produced during the session, embed summaries and optionally expandable full text.
Make the page visually intentional and presentation-ready for desktop and mobile.
Preserve accuracy: do not invent decisions, files, or outputs that did not happen.

Content Selection

Compress noisy tool logs into evidence cards or short proof snippets.
Keep the sequencing faithful to the session.
Emphasize pivots:
- when the problem changed
- when a conclusion was reached
- when reusable assets were produced
Prefer direct filenames and concrete outcomes over vague summary language.

Use semantic HTML, inline CSS, and minimal inline JS only when needed.
Favor light backgrounds and editorial/project-workbench aesthetics unless the repo already establishes another style.
Keep the HTML easy to hand-edit after generation.
If the session produced Markdown artifacts, either:
- embed concise summaries plus expandable full text, or
- embed the most relevant excerpts when full text would be too large.