docs-create-status-reportlisted

<task overview="Generate a project status report by analysing the current state of the codebase, roadmaps, and recent work." destination="docs/dev-log/status-reports/" > <filename format="{PROJECT-REPORT-NUMBER}_{YY-MM-DD-HHMM}_{RECENT}.md" example="003_26-01-13-1545_xml-validation-added.md" > | Component | Description | Example | |-----------------------|--------------------------------------------------|---------| | PROJECT-REPORT-NUMBER | 3-digit incrementing number across all reports | `001`, `002`, `015` | | YY-MM-DD-HHMM | Date and time (24hr) | `26-01-13-1430` | | RECENT | Most significant change, max 3 words, kebab-case | `csv-parser-complete` | To determine PROJECT-REPORT-NUMBER, check existing reports in the output directory. </filename> <instructions> 1. **Read the roadmap** — `python3 "$HOME"/.claude/library/scripts/roadmap.py stats` when a rich roadmap exists (check with `roadmap.py detect`), otherwise the newest file in `docs/roadmaps/` 2. **Check recent work records** in `docs/dev-log/work-records/` for recent activity 3. **Review git history** in one command: `"$HOME"/.claude/library/scripts/git-doc-history.sh {previous-report-path} .` — commits, file changes and diff stat since the last report; accurate numbers, not estimates 4. **Identify blockers** from any TODO comments, failing tests, or documented issues 5. **Read the previous status report** in `docs