hey-recaplisted

# Weekly recap Read-only. **Never edit the ledger.** What to change based on the recap is the user's call; `/hey-tune` or `/hey-sync` apply it. ```bash ROOT="${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}" # Codex names it PLUGIN_ROOT HEY="$ROOT/scripts/hey.py" BOARD="$ROOT/scripts/board.py" ``` ## 1. Gather the numbers ```bash LC_TIME=C date "+%Y-%m-%d (%a)" python3 "$HEY" progress python3 "$HEY" burndown --days 14 python3 "$HEY" carryover --days 3 python3 "$HEY" variance python3 "$HEY" log --limit 7 python3 "$HEY" notes --since 7 ``` A weekly recap is the one place the extra calls are worth it — but if the user only wants a quick read, `board.py wrap` covers most of it in one call. When snapshots are thin the scripts say so. **Never assert a trend on top of that.** ## 2. Five sections ### What got done Group this week's work-log entries into themes rather than listing them day by day. Keep the PR numbers. **Never invent something the log does not contain.** ### Burndown ``` AI-days left 81.25 -> 80.85 ▇▇▆▆▅▅▄ 2026-07-23 ~ 2026-08-05 · 14 days · net change -0.40 ``` **A shape, not a rate, and the delta is a net change rather than work delivered.** The line moves on closed work, added scope, removed scope and re-estimates alike. Never divide a finish date out of it. A flat or rising week is a question to ask rather than a verdict: were items not closed, or did scope grow? Say which you think it was, and say you are inferring. ### Blockers and carry-over **Blockers fir