creating-iteration-report

Automate iteration report generation by collecting iteration_plan-{N}.md, release_plan.md, git logs, and test outputs to compute planned vs actual story points, velocity tables, and burn-down charts into a single markdown report.

Track velocity and story points by aggregating iteration plans and release plan data to compute achievement rates, velocity tables, and burn-down charts, then write the metrics into docs/development/iteration_report-{N}.md.

You do not need mkdocs to generate the core iteration report, but the workflow refreshes mkdocs navigation and documentation indexes alongside updating release_plan.md progress entries when the report is written.

You need docs/development/release_plan.md and docs/development/iteration_plan-{N}.md in your repository, as the workflow aggregates these files with git history and test results to produce the formal iteration completion report.

Generate a reproducible iteration report by running backend, frontend, and E2E tests to capture results, computing story point metrics, and updating release_plan.md and documentation indexes for release planning and retrospectives.

Iteration report capture fails when the repository lacks the required iteration_plan-{N}.md or release_plan.md files, preventing the workflow from aggregating git logs and running backend, frontend, and E2E tests for the report.