create-progress-reportlisted

# Create a progress report One self-contained HTML file that both parent and child can read: an honest picture of **how she's doing** and a clear answer to **what to work on next**. A snapshot, not a narrative essay — lead with the concrete and recent, then stop. If in doubt, cut a section rather than pad it. 1. **Gather real evidence — the substance, not just filenames.** - Every activity's own `conversation.json` (e.g. `find . -maxdepth 4 -name conversation.json`, skipping `materials/`, `reports/`, `memory/`, `conversations/`). Read what actually happened: which problems came up, whether she got them on her own or needed hints, how many attempts, what tripped her up, any celebrate moments and why. This is the real signal — a list of activity titles and dates is not enough. - Each activity's `attempts/*.json` — what she's actually completed, and what the attempt shows. - The `<Subject>/<Topic>/` activity folders and `materials/` — what exists, so you can name what's covered versus not started. - For the **Overall** section you need the FULL history, not just the recent few: skim across the whole workspace, since that section is cumulative. - Never invent a score, a percentage, or a diagnosis that isn't directly backed by something you read. 2. **Write** it to `reports/progress.html` — always overwrite in place. This is one living document, fully regenerated each time; never append a dated entry or keep old