ijfw-milestone-summary

Produce an onboarding doc for someone joining mid-stream. Output: `.planning/<milestone>/SUMMARY.md`. Domain-agnostic: "what shipped" means chapters drafted for a book, launches that landed for a campaign, features released for software, episodes recorded for a podcast. Adapt the noun to the project type. ## Step 1 -- Resolve milestone Argument is the milestone slug (e.g. `1.5.0`, `q2-launch`, `book-draft-2`). If absent: 1. Read `.ijfw/state/workflow.json` -- use the current milestone field. 2. Else read `.planning/ROADMAP.md` -- pick the active milestone. 3. Else list directories under `.planning/` and ask which one. Set `MS="<resolved-slug>"`. Set `OUT=".planning/${MS}/SUMMARY.md"`. ## Step 2 -- Inventory artifacts Read whatever exists, skip whatever doesn't. Missing files are normal -- the doc adapts. - `.planning/ROADMAP.md` -- scope, dates, status of each item. - `.planning/${MS}/SUMMARY.md` -- prior version (overwrite guard, see Step 6). - `.planning/${MS}/**/SUMMARY.md` -- per-item outcomes. - `.planning/${MS}/**/LEARNINGS.md` -- per-item decisions (written by ijfw-extract-learnings / C06). - `.planning/${MS}/**/VERIFICATION.md` -- gaps, deferred items. - `CHANGELOG.md` -- the `${MS}` entry if present. - Git log for the milestone tag range: - If `v${MS}` tag exists: `git log --oneline v${MS}` and `git log v${MS}~1..v${MS} --stat`. - Else: `git log --since="<earliest .planning/${MS}/ commit date>" --oneline`. - Else: skip git stats. ## Step 3 -- Synthesize...