progress-reportlisted

Turn the run's ledger into a document the user can read in two minutes. ## 1. Find the source and the watermark 1. **Reports folder:** the one the user named, else the repo's `skilleddocs/reports/` (create it). All reports and the watermark live there, committed with the repo, so they survive across sessions and machines. 2. **Ledger:** `skilleddocs/orchestrator/ledger.md` (older runs: `ledger.md` in the reports folder), written by the `meta-orchestrator` skill (numbered `### NNN · timestamp · kind` entries). If there is no ledger, reconstruct one now from `git log`, `gh pr list --state merged`, `gh issue list --state all`, and your own conversation — and say in the report that it was reconstructed. 3. **Watermark:** `.last-reported` in the folder holds the number of the last ledger entry already documented (and the filename of that report). No file means this is report #1 and it covers everything. **The non-overlap rule:** the new report covers ledger entries `watermark + 1 … latest`, nothing earlier. If report 1 covered entries 1–5 and the user asks again at entry 22, report 2 covers 6–22, not 1–22. The one exception: if something *already reported* was later changed (a merged PR reverted, a decision reversed, a "done" that turned out broken), include it under **Revisions to earlier reports**, citing the earlier report's number. Do not re-describe it otherwise. If the user says `full`, ignore the watermark, cover everything, and title it "Full rep